Closed apb2019 closed 5 years ago
Please can you clarify: do you get the status = Alarm
message for both switch on and switch off operations? Are there separate on & off buttons, or just one button (that switches the light on & off alternately)?
I'm currently making changes to the rfx-detector-in
node to fix issue #64, which may have already fixed this problem, if it's what I think it is from your description!
If I understand #64 correctly it’s a similar situation as there is no difference between successive messages sent by the switch (and no heartbeat). The switch has one button which always sends the same signal each time it’s activated. When the paired receiver receives the signal, it toggles the connected light to the opposite state ie from Off to On or vice versa. Consequently other than the time stamp, the output from rfxcom is always the same ie “status = alarm” for every message received. Hope that helps
From: Max Hadley [mailto:notifications@github.com] Sent: 04 February 2019 19:14 To: maxwellhadley/node-red-contrib-rfxcom Cc: apb2019; Author Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] rfx-detector node (#72)
Please can you clarify: do you get the status = Alarm message for both switch on and switch off operations? Are there separate on & off buttons, or just one button (that switches the light on & off alternately)?
I'm currently making changes to the rfx-detector-in node to fix issue #64 https://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/64 , which may have already fixed this problem, if it's what I think it is from your description!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/72#issuecomment-460373868 , or mute the thread https://github.com/notifications/unsubscribe-auth/AsYKiX_SajjNdM6UJbODDE98hcYsfnB5ks5vKIZ4gaJpZM4ahNLM .Image removed by sender.
In that case the next release should fix it: I will use the message details you posted to make a simulation for test purposes. Hopefully any day now, if I can find a spare couple of hours...
Tx, I look forward to it. Happy to test beforehand if it helps
Should be working now
Hi, update downloaded and working well. Tx for the quick fix
From: Max Hadley [mailto:notifications@github.com] Sent: 05 February 2019 21:34 To: maxwellhadley/node-red-contrib-rfxcom Cc: apb2019; Author Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] rfx-detector node (#72)
Should be working now
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/72#issuecomment-460812540 , or mute the thread https://github.com/notifications/unsubscribe-auth/AsYKiTTz6AFkKXeA8KjQQlVhhP7FcfcSks5vKfjNgaJpZM4ahNLM .Image removed by sender.
I have some RF light switches (PCB says CreaJian-X21) which I would like to use. Though light switches, RFXmngr identifies the transmissions as being X10 Security1 packet types so I have used the rfx-detector node to feed into my flow. Unfortunately the detector node only picks up the first transmission (topic: "X10_DOOR/device id", payload: "Alarm") and ignores any further transmissions from the switch - is this correct? The following is the rfxmgr output
Packettype = Security1 subtype = X10 security Sequence nbr = 0 id1-3 = 52F300 decimal:5436160 status = Alarm battery level = OK Signal level = 7 -64dBm