Topics created by Mihai

I did not work too much with github and still find it somehow a little bit annoying for me, but I was trying to do this. I also have updated the new inserted constant as you advice. The new definition should be moved to the MyConfig.h , but now it was easier to modify only one file. My tests were done on MQTT Gateway made by Arduino Uno (clone) + Ethernet shield 5100 and it works very nice.

In HomeAssistant, if you use MQTT switch for example, with state and command topic, the command is send to the gateway when requested from the interface, but the switch on the interface change itself when it receive back the status from the gateway. If the message doesn't reach the destination and comes back with the new status, the interface doesn't change the switch state. I encounter this situation a lot of times. After many tests, my findings show that the messages are lost between the nodes and the gateway, but I never miss a message between the gateway and the controller. So, while it will be nice and useful to have an end-to-end implementation with ACK and automatically retries, the real problem can be solved if such mechanism will be available between nodes and gateway.

Thank you.

I read other times that relays can cause some power fluctuations that can cause problems.

Until the problem will be solved, the solution is to use other range numbers for gateway relays, I go for single numbers in nodes (1, 2 ...) and high range for the gateway (101, 102...). I also have updated my examples on GitHub and use this approach to my project very close to final stage.

Yes, it works fine now, thank you!

@mihai Thanks Mihai, I have been struggling with getting my first basic Home Assistant + MySensors via MQTT working. Your examples got it all going for me. Thanks again for taking the effort to post.

Thank you, I know, I already do this, but I am thinking for other users too. I was building a node with 4 Relays, temperature sensor, PIR, smoke sensor, IR sensor so I use a lot of Arduino inputs.

Ok, thank you.

This wasn't clear to me either, I was expecting to see setup() & loop(). Perhaps a note or some documentation why this is empty would be useful.