Replies: 1 comment
-
This comment from john30/ebusd-configuration#86
Seems to confirm that both get and set require fields to be published separately but I still don't understand how this would be handled at the ebus level. Surely the bai is only able to react to the single message concatenating all the relevant parameters? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm getting on just fine with reading and writing with ebusd from the command line and over Telnet, however, while I'm successfully polling the info I want to read back via MQTT I can't seem to write (set) mulitple parameters in my payloads. From the MQTT section of the wiki:
So how should a multi-parameter write command such as
ebusctl w -c bai SetModeOverride '0;65;-;-;-;0;0;0;-;0;0;0'
be sent as an MQTT message? If I use MQTT spy to enter the topic
ebusd/bai/SetModeOverride/set
and enter0;65;-;-;-;0;0;0;-;0;0;0
for the payload it doesn't set the boiler (as it does from the command line) and the log shows that ebusd received an unmatchable topic:But then the log goes on to say it sent update-write bai SetMode (why?) then write bai SetModeOverride with the same parameters I'm trying to set. MQTT spy shows thtat the command got broken into separate topics for each parameters:
This is sort of understandable because I have configured ebusd with
--mqtttopic=ebusd/%circuit/%name/%field
for more elegant decoding however I don't think this looks to be compatible with multi-parameter payloads being written. Is this true?Beta Was this translation helpful? Give feedback.
All reactions