You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi All,
I have several kaku wall switches which I use to control several devices in the house. Currently I'm using an USB RFXCom to receive the signals and trigger the associated functions via MQTT/Node-Red/Home Assistant . This is working fine, except for some wall switches which are out of range of the RFXCom.
So I bought some RFBridges to be installed near the problematic wall switches.
I flashed Tasmota and Portisch like described in the documentation. I convert B1 to B0 using the node red implementation of bitconverter. Raw sniffing works well, and I'm able to reproduce the wall switch signal using the bridge.
Now I would like the RFBridge also to recognise the wall switch pressed. But the RAW codes are never the same. So my question is how to solve that. Is it possible to set a range for every switch, or am I overlooking something.
PPee
The text was updated successfully, but these errors were encountered:
Hi All,
I have several kaku wall switches which I use to control several devices in the house. Currently I'm using an USB RFXCom to receive the signals and trigger the associated functions via MQTT/Node-Red/Home Assistant . This is working fine, except for some wall switches which are out of range of the RFXCom.
So I bought some RFBridges to be installed near the problematic wall switches.
I flashed Tasmota and Portisch like described in the documentation. I convert B1 to B0 using the node red implementation of bitconverter. Raw sniffing works well, and I'm able to reproduce the wall switch signal using the bridge.
Now I would like the RFBridge also to recognise the wall switch pressed. But the RAW codes are never the same. So my question is how to solve that. Is it possible to set a range for every switch, or am I overlooking something.
PPee
The text was updated successfully, but these errors were encountered: