Support for Temperature and Humidity in gl200 protocol for GL300A device
This is one of the messages sent by the device (extracted from Traccar logs) in case it helps:
HEX: 2b524553503a47544652492c3439303330312c3836303539393030353237373439362c2c33302c302c342c322c302e302c3233312c36302e342c31342e3433353032322c33352e3930363039302c32303230303132323132333735382c303237382c303032312c303044362c433939432c2c322c302e302c3233312c36302e342c31342e3433353032322c33352e3930363039302c32303230303132323132333830312c303237382c303032312c303044362c433939432c2c322c302e302c3233312c36302e342c31342e3433353032322c33352e3930363039302c32303230303132323132333830372c303237382c303032312c303044362c433939432c2c322c302e302c3233312c36302e342c31342e3433353032322c33352e3930363039302c32303230303132323132333831332c303237382c303032312c303044362c433939432c2c39332c32342e352c34392e302c3739352c302c32303230303132323132333831362c3232374424
After decoding the above hex message, it is sending the +RESP:GTFRI (coma delimited) with Battery Percentage, Temperature (optional), Humidity (optional), Ambient Light (Optional), Device Removal Light (Optional) at the end before the send time, count number and tail character $.
These were included:
93,24.5,49.0,795,0,
Traccar is showing the battery level (which is not optional), but not the other 4 attributes.
Is there any way to enable them?
Hi,
Does traccar parse sensor readings such as temperature and humidity sent over the gl200 protocol (Queclink etc.)?
I tried to test a GL300A device and it connects fine to Traccar, but I only see position information.
According to the documentation (GL300A @ Track Air Interface Protocol) it sends temperature, humidity etc. too.
http://www.queclink.com/sites/default/files/GL300A_Develop_Suit_A03V08_Eng_%28Doc_and_Tool%29_BQ5W.zip
The device was configured to send all of these but when I looked in the traccar database I only saw the following:
hdop, type, distance,totalDistance,motion
radioType, considerIp, cellTowers
Is this something supported by Traccar that needs to be enabled? or is it just not there in the protocol parsing yet?
thanks