via the mqtt.publish. I can see it it sent out, but the light doesn’t react on it.
I guess it could because of the #, but if I don’t enter that it sends out something completely different.
So what am I doing wrong here?
It looks like I can store the codes in the ‘preprogrammed’ slots in bridge, but not send them directly.
I have several buttons But yes, seperate buttons and codes for on and off (this is the light)
Using the stored keys in the rfbridge works very well, but it’s difficult to maintain, eg. if the rfbridge dies, so I would much rather have it all in one place.
The light is very stable in turning on and off etc. much better than the other one I tried.
I don’t see any of the codes being transmitted properly if I enter the # code.
I’ve tried building most of the buttons with stored keys, and it works, but again, it’s not optimal to not have it stored in HA instead.
I can also see that some of the buttons like ‘white’ takes quite a long press to be captured by the rfbridge, and that results in two codes being stored in one key. This makes it switch between the two white modes it has stored (one is ‘real’ white, and the other is RGB-white) and then switch back to the original white mode.
This is what I’ve built so far with stored keys.
@1technophile Yes I had that one at first, mine was sadly defective and didn’t give any red color, so I replaced it with the one I have now, that also produces real white
I would imagine you would use the OpenMQTTgateway
I think I’ll get a new Sonoff Bridge, and make it with ESPHome, as it seems to be faster.
It is just an arduino UNO with an ethernet shield and OpenMQTTGateway:
The use of an ethernet compared to wifi added to the direct handling of the decoding by the uC (no use of an external uC to decode/encode signals) make a huge difference in term of processing time.
If I had to redo it now I would use an Arduino Mega, but it is working correctly since more than 3 years.