Hi,
I suppose you see this behaviour on HA isn’t it? Could you check what is happening on the mqtt broker side and post the results?
Yes, it’s on Home Assistant, and using this broker, which mainly just shows connections.
Logbook also doesn’t show the code, just a blank space.
Do now have serial monitor so when pressing the doorbell button:
Creating SRFB buffer
isAdupl?
Adv data SRFBtoMQTT
Pub json into:
home/OpenMQTTGateway_SRFB/SRFBtoMQTT
{"raw":"147800B40208374D05","delay":5240,"val_Tlow":180,"val_Thigh":520,"value":3624197}
Pub data per topic
raw
147800B40208374D05
delay
5240
val_Tlow
180
val_Thigh
520
value
3624197
Store val
Min ind:
0
store code :
3624197/43895
Col: val/timestamp
0:3624197/43895
1:0/0
2:0/0
3:0/0
4:0/0
5:0/0
6:0/0
7:0/0
8:0/0
9:0/0
10:0/0
11:0/0
[RFBRIDGE] Sending ACK
MQTTlens for button as well.
{
"raw": "145000BE0208374D05",
"delay": 5200,
"val_Tlow": 190,
"val_Thigh": 520,
"value": 3624197
}
And then serial monitor when I activate the switch to send same signal as received above.
Hey I got a callback
MQTTtoSRFB prts
[RFBRIDGE] Sending MESSAGE '%s' %d time(s)
⸮⸮%@⸮7MU
And MQTTlens for switch too.
Could you indicate the receiving device type/model?
Doorbell is a “local” SA brand. Ellies. Not a super lot of info.
RGB Controller is one of these
If I can receive the codes, I should be able to send them as well, or is there something regarding RF I’m missing?
For the sonoff rf bridge the speed has to be set to 19200
This is working now, thanks!
I’ll keep an eye on the false readings issue. Hasn’t happened again today.
Does any of this help narrow down the issue with sending? From the serial monitor log is does seem like something’s going wrong.
Thanks again!