Closed jaakla closed 5 years ago
As temporary workaround I changed in _Userconfig.h:
#define simplePublishing true //comment if you don't want to use simple publishing (one topic for one parameter)
This fixes the Pilight messages. Still it is not a final fix, as this way I'm making many other messages hard/impossible to process. For example now I have following set of BTLE messages (from 3 devides I believe) which are very difficult/impossible to make usable, as messages from different devices are messed up:
home/home_presence/OpenMQTTGateway/id 5e:0b:62:21:6d:5f
home/home_presence/OpenMQTTGateway/manufacturerdata L
home/home_presence/OpenMQTTGateway/rssi -58
home/home_presence/OpenMQTTGateway/distance 0.8
home/home_presence/OpenMQTTGateway/id 70:19:e5:38:60:e9
home/home_presence/OpenMQTTGateway/manufacturerdata L
home/home_presence/OpenMQTTGateway/rssi -75
home/home_presence/OpenMQTTGateway/distance 5.8
home/home_presence/OpenMQTTGateway/id a0:99:9b:1d:05:ae
home/home_presence/OpenMQTTGateway/manufacturerdata L
home/home_presence/OpenMQTTGateway/rssi -58
home/home_presence/OpenMQTTGateway/distance 0.8
I get the same with pilight, had to run it thru nodered to convert it to Json....
Should be better now, with v0.9.2beta
Describe the bug PilighttoMQTT message format is not recognized by json parsers, e.g. home-assistant. The
message
field JSON, but not for some reason escaped as json string. It is quite hard to even notice this issue, I spent literally hours troubleshooting why home-assistant does not read the data properly.Notice that message contents is not really json object here, but just a string value of "message" top level element.
To Reproduce Listen messages over Pilight connection. See also #355 .
Expected behavior Proper JSON format, with sample above
Environment (please complete the following information):