Local python service MQTT vs REST communication

restapi
python
mqtt
Tags: #<Tag:0x00007f1e51b0c158> #<Tag:0x00007f1e51b13ef8> #<Tag:0x00007f1e51b13db8>
(Daniel Dakhno) #21

you are absolutely right. TCP and MQTT and so on are for sure way more future-proof than domain sockets.

TCP just forced me to shift some of my logic to my service, because that logic is really timing-critical and does not allow for any delays caused by MQTT.

0 Likes

(Daniel Dakhno) #22

I finally tried homie, and i am slighty confused.
If i have, for instance, a ringer, which is configured as a contact in openhab,
how does homies “true/false” for a switch work together with openhabs “ON/OFF/OPEN/CLOSED” for switches/contacts?

0 Likes

(David Graeff) #23

That’s the reason why there is a binding :wink: It performs all those mappings transparently for you.

0 Likes

(Daniel Dakhno) #24

thanks for the answer.
What binding do you mean? The MQTT binding? I am somehow unable to find a binding that transforms those values by itself…

0 Likes

(David Graeff) #25

The MQTT binding exactly. It consists of 3 bundles that are all installed at once, and one is the Homie MQTT part. It works for auto-discovered things only, of course. That’s the entire purpose of Homie.

0 Likes