Replies: 3 comments
-
I did more testing using MQTT Explorer: publish raw value of 30.0 to ebusd/22420/room/temperature/set, result in ebusd.log:
to compare result publish same value to same topic with ebusctl (ebusctl write -c 22420 room/temperature/set 30.0) result in ebusdlog:
here the definition in 15.22420.HW0102.SW0502.csv:
I attach my *.csv files. Can anybody explain what is wrong publishing with MQTT Explorer? Werner |
Beta Was this translation helpful? Give feedback.
-
you shouldn't use slashes in message and/or circuit names as this will break things at various locations. |
Beta Was this translation helpful? Give feedback.
-
I want to write a value (room temperature) via mosquitto MQTT from openhab to ebusd and further to my Ochner OTE.
I am successfull using ebusctl:
ebusctl write -c 22420 room/temperature/set 24.0
I can see immediately in MQTT explorer the result
and after a short time also on the OTE display.
But I am not successfull writing the value from openhab via mosquitto MQTT.
Here my openhab mqtt.things:
Bridge mqtt:broker:mosquitto "Mosquitto MQTT Broker" @ "MQTT" [ host="localhost", secure=false, port=1883 ] { Thing topic ebusd { Type number : temperature_room [ stateTopic="ebusd/22420/room/temperature", commandTopic="ebusd/22420/room/temperature/set", transformationPattern="JS:|(input).split(';')[6]"] } }
I can see the new value in MQTT explorer write topic set (changed from 24.0 to 24.5)
`- ebusd
but not on the read topic temperature and OTE display.
Maybe a wrong value type used by openhab?
I do not have any idea how to solve this problem, any help is welcome!
Thanks in advance
Werner
Beta Was this translation helpful? Give feedback.
All reactions