search

maxwellhadley / node-red-contrib-rfxcom

node-RED nodes to access an RFXtrx433 transceiver
BSD 2-Clause "Simplified" License
22 stars 13 forks source link

Livolo. Only "SCENE x" command is working. going from 1040 to 1043 on RFXCOM and 2.11.0. #98

Open MosesHill opened 3 years ago

MosesHill commented 3 years ago

let working commands:

msg.payload = 'Toggle' -- I have tried with 'Toggle 5' msg.topic = 'LIVOLO_APPLIANCE/1522/5'

This does also not work: msg.payload = 'Off' -- I have tried with 'Group Off' msg.topic = 'LIVOLO_APPLIANCE/1520/0'

Nothing works.

maxwellhadley commented 3 years ago

I don't think anything should have changed, but I will take a look - might take me a couple of days to get round to it though

MosesHill commented 3 years ago

Thank you. It has been working perfectly since we implementer and tested it last time :-)

Hilsen Marcel

Den 12. jul. 2020 kl. 16.01 skrev Max Hadley notifications@github.com:

 I don't think anything should have changed, but I will take a look - might take me a couple of days to get round to it though

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

maxwellhadley commented 3 years ago

Did you update the firmware & the node at the same time?

MosesHill commented 3 years ago

Yes I did

Hilsen Marcel

Den 13. jul. 2020 kl. 10.57 skrev Max Hadley notifications@github.com:

 Did you update the firmware & the node at the same time?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

maxwellhadley commented 3 years ago

OK, I can see why toggle isn't working: it's a change I introduced when I added the rfx-fan-out node in version 2.10.0 released on 14th February. Many fan types have associated lights which can generally only be toggled on & off. However, the group off command is not affected by the error, and works OK for me.

I notice in your original message the address is different in the group off command example, msg.topic = 'LIVOLO_APPLIANCE/1520/0' instead of msg.topic = 'LIVOLO_APPLIANCE/1522/0' to match the toggle command example. Can you please check you have the correct address? The correct way of sending a group command (any command, if the device supports it) is to replace the unit code - the number after the last '/' in the topic - with 0, and to leave the command unchanged.

MosesHill commented 3 years ago

Hi Maxwell

The address was just wrong in the mail.

The way I use the Livolo is:

Select one address to use for this switch only Set a switch into programming mode Send toggle for button 5 command to that address. Now the switch is connected to this address. Set the switch to programming mode again while it is turned on Send a scene 1 command to that address

Now the scene 1 command is a true “turn on” command and the group off is a true “turn off” command. So I can use these two when programming the nodes behind an Alexa node.

But when I click a lamp on a map of my house in a browser I use the toggle button 5 command as I cannot receive the on/off status from the Livolo switch as it has no send function.

Just as you said. Toggle is the one not working in the RFXCOM node. So using the browser click to toggle does not work anymore I cannot program any switch anymore.

Can this toggle be fixed?

Marcel

Den 17. jul. 2020 kl. 13.32 skrev Max Hadley notifications@github.com:

OK, I can see why toggle isn't working: it's a change I introduced when I added the rfx-fan-out node in version 2.10.0 released on 14th February. Many fan types have associated lights which can generally only be toggled on & off. However, the group off command is not affected by the error, and works OK for me.

I notice in your original message the address is different in the group off command example, msg.topic = 'LIVOLO_APPLIANCE/1520/0' instead of msg.topic = 'LIVOLO_APPLIANCE/1522/0' to match the toggle command example. Can you please check you have the correct address? The correct way of sending a group command (any command, if the device supports it) is to replace the unit code - the number after the last '/' in the topic - with 0, and to leave the command unchanged.

— 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/98#issuecomment-660057332, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIOERVJRVZ3MMLSBRXNMDYTR4AZGBANCNFSM4OXZCIIQ.

maxwellhadley commented 3 years ago

OK thanks for clearing that up - I found & fixed the toggle bug (I had forgotten to add an else clause) but I was worried in case I had missed another problem. I will merge the fix and publish an update later this evening. Off on a cycle ride first!

maxwellhadley commented 3 years ago

Fixed in 2.11.1

MosesHill commented 3 years ago

Hi

When installing the new version and restarting, node red says: RFXCOM Port and RFCCOM Lights out nodes are missing.

Den 18. jul. 2020 kl. 21.28 skrev Max Hadley notifications@github.com:

Closed #98 https://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/98.

— 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/98#event-3561527016, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIOERVNEOWX2TJHTRITSARLR4HZUPANCNFSM4OXZCIIQ.

maxwellhadley commented 3 years ago

I think this may be related to #99 - something in the installation seems to be breaking. Are you using Home Assistant and/or Docker?

MosesHill commented 3 years ago

I installed node red directly on a Raspberry pi with Linux (Jessie I think)

Hilsen Marcel

Den 19. jul. 2020 kl. 22.33 skrev Max Hadley notifications@github.com:

 I think this may be related to #99 - something in the installation seems to be breaking. Are you using Home Assistant and/or Docker?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.