Jetstream API
Device Types
Read Point
5min
about read points are powerful rfid sensors that can be mounted almost anywhere to track rfid tags passing through the sensors range the most common configurations include doorway mounted portals that track the movement of tags in and out of the room, and ceiling or wall mounted portals that track the sighting of tags in a particular location model ts090 commands name supported update firmware docid\ h9h679y t3yztcipn2gcz yes get all passes docid\ d7j1rxbgyehbv3bajwgsp no add or remove passes docid\ the3s6mtw3baeauul1a83 no get all rfid tags docid\ ci32mn8hwosbcmjmdu4tp no restart a device docid 9jcownfudipbznnnryfr0 yes lock a device docid\ wahzv ft98lwrpl3x2p0v no unlock a device's door docid\ qdtewzyti 4vmdsnli9qm no get a device's configuration parameters docid 94vzb6djztjxfyzb78uj yes set a device's configuration parameters docid\ llqub1kfyhmeomohn 1fc yes configparameters name description data type min max default name description data type min max default antennatxpower the db transmit power of all of the antennas int 15 32 23 antennarxsensitivity the db receive sensitivity of all of the antennas int 80 30 70 autoupdate firmware auto update enable bool 0 1 0 capturetime time in seconds before a tag that enters the field is reported int 1 120 5 commandpollinterval the number of minutes between polling for device commands in jetstream int 0 600 60 commsreboot number of minutes after the system loses communication that it will automatically reboot int 10 1440 230 commsreconnectinterval time in seconds to wait before attempting to communicate with jetstream if there were any communication problems int 1 300 10 commstimeout time in seconds to wait for a reply from jetstream after sending an event or command response int 1 300 60 heartbeateventinterval the number of minutes between sending a heartbeatevent a setting of 0 will disable heartbeatevents int 0 600 60 inactivityinterval time in seconds communications will wait before re establishing a connection if there is no activity int 0 3600 300 jetstreamdeviceurl the url to which the read point sends jetstream messages string http //us device tersosolutions com/ http //us device tersosolutions com/ jetstreamwebsocketappendpoint the jetstream resource used to connect for websocket communications using '#' will disable websocket communications string /dwsliveconnection ashx logentrylevel the verbosity of the logs sent by the reader off error warning information verbose string error logfilelevel the verbosity of the logs saved locally on the reader off error warning information verbose trace debug string debug numantennas number of antennas active for reader int 1 4 1 objecteventhour the hour to perform the daily system scan as well as other system checks a value of 1 disables this feature int 1 23 0 readerlogentryonfailure generate a logentryevent when communications to the internal rfid reader fails bool 0 1 0 removeevent sets whether an aggregate event "remove" is sent when a tag leaves the field of scanning bool 0 1 0 securesocket use secure communications over https for the read point bool 0 1 1 versionsfileurl location of file listing current versions of firmware used to configure auto firmware update string http //firmware tersosolutions com/versions json http //firmware tersosolutions com/versions json logentryevents the list below are some common, potential logentryevents a read point may send in however, not all possible logentryevents are listed in this table the logentrylevel in use determines which logentryevents are sent to jetstream name description lowflashmemory lowflashmemory occurs when the read point has less than 25% flash memory lowmemory lowmemory occurs when the read point has less than 25% memory this event will be sent every hour until the device reboots reboot occurs automatically if memory drops to 10% newfirmwaredownloaderror newfirmwaredownloaderror occurs when a request to upgrade firmware fails readexception readexception occurs when there is an issue performing an rfid scan startup startup occurs whenever the read point is started up sensorreadingevents the read point does not generate any sensorreadingevents