@lolodomo
OK, I understand and respect that you don’t want to spend more time to this plugin.
Could you then indicate which LUUP file(s) I have to adapt to make this work. Then I will dig deeper into it.
Thanks in advance.
L_RfxTrx.lua
hello everyone, i read this thread and saw that the byron sx was being used in vera, but upon purchasing the byron sx220 i can’t get it to create any devices despite the Byron SX protocol enabled in the plugin and the plugin registering Last received message : 07 16 00 0B 00 9D 06 70 every time i push the bell i can’t see how it works.
Am i missing something fundamental ?
Hi deejc,
The Byron sx is supported by the RFXtrx433 but there is NO support for this protocol in the Vera Plugin so it will not work in Vera unless YOU add support for this protocol yourself.
If you read the thread you should already know this.
i did read the thread, as i noted. but its a bit confusing, i thought the plugin creator was advising one of the posters about creating a particular device for it.
but now you have made it clearer.
its a shame, i would really like to add it as a device but I’m not a coder so its above me.
does anyone know a work around to get it to trigger a scene ?
could PLEG be used, Could it pick up the code and use that as a trigger ?
i have a byron SX doorbell and feel sad it is supported by the RFXcomE, but not the plugin. hopefully it is, since the last posting?
well anyways…my doorbell isnt working too great anyway, so could anyone just mention a few doorbells that are both supported by the plugin and the RFXomE itself? i guess i will just buy any of those then.
Kaku (coco) doorbell is working ok here (Vera3 on UI5 and RFXcom both old and e-version)
Which one exactly?
ACDB-7000BC. This is a wireless doorbell that you can simply plug in a 220V outlet plus a sender
wow, looks like I have the same one but it is called LML-710 from Nexa. Works grate anyhow.
i’ll be needing a totally new doorbell. I guess the ACDB-7000AC will be compatible with the vera and RFXcomE plugin as well?
Yes
While the Byron SX doorbell is not officially supported in the plugin (as an option) I know @lolodomo provides a variable called “LastReceivedMsg”. Has anyone checked the codes being sent by their doorbell and see if it appears in there ?
If it does, it should be possible to create something in the Lua start up that always looks to that specific variable for the door bell’s signal.
Here’s some ‘luup.variable_watch’ code that I found on this forum which is looking for their radiator valve to wake up, in order to call a specific function. For those with the skills this could potentially be reworked to do what you need, e.g run a scene when the door bell has been pushed (and the signal received by the plugin).
function stellaNotify(lul_device, lul_service, lul_variable, lul_value_old, lul_value_new)
luup.log("Sending a thermostat wakeup alert")
local status, result = luup.inet.wget("http://xxx.xxx.x.x:xxx/?stellaZWakeUp", 5)
luup.log(status)
end
luup.variable_watch("stellaNotify","urn:upnp-org:serviceId:ZWaveDevice1","LastWakeup", 141)
Caveat, I do not have a Byron SX door bell, and I’m not a programmer either - so the above is just a thought/suggestion 
Hi yes, good thought. I’ve taken that idea and used it in PLEG with a =~ operator - works a treat as a BYRON signal.
Example.
Last message received from RFXTRX = 07 16 00 61 00 60 05 70
Note the 61 is a rolling code so you can’t do a direct compare with == as you would do elsewhere, but as PLEG doesn’t have a LEFT, RIGHT string compare function the =~ operator works okay instead for this purpose
PLEG Condition
Lastmsg =~ "07 16 00" and Lastmsg =~ "00 60 05 70" (ie. doing a compare but missing out the rolling code ID)
btw the penaltimate pair (05 in the example above) is the code for the different ring tones of the unit so you can do some fancy logic with that if you need.
Also note that the =~ operator is not available if you use the PLEG condition editor from the UI - just type it in from the main condition window.