Small messages are for not powerful platform to save energy and cpu, for example for gateway itself. Thank you for more formats, will test.hvxl wrote:The type of the value is always the same for a particular parameter, so it's a waste of bandwidth to transmit that information every time (I understand MQTT was designed to keep the messages small). But obviously JSON isn't the most appropriate format if bandwidth is a consideration. So I've added two more JSON formats to otmonitor 4.1b1.
Currently it's not actual for me, but we can expand the standard a bit, prefix can be empty .hvxl wrote:Re: Prefix for the topic: I'm not sure that's allowed. The DomoMQTT specification says "The events topic has the following format: events/device_type/device_id/property".
I just want to get messages in the following form:hvxl wrote:I don't understand what you are trying to say regarding the unprocessed messages and using http interface for command. If you want me to change something there, please explain a bit more.
T00110000
BC0110000
T9014A73B
R80190000
B40191B00
T80001300
otmonitor is processing messages very well, but other applications can use messages from gateway for additional processing, for ex. if chsetpoint is overwritten. That topic should be not persistent.
About http command interface, I just use it and I don't need mqtt interface for it. With "http get" request I have got report in transactional way in time of request.
Thank you very much, I can't expect such high level of support.