Basic dashboard switch wiring #188
Replies: 4 comments 49 replies
-
|
The module does have a sample flow - but it's more to demo how the nodes work (menu -> import -> examples). On the other hand - see below a flow (and subflow) to import to gain some idea. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @fabnavigator However, have had a look - few things I would change.
Also - this is not strict enough - you need to filter to the value you are interested in
Example for battery level if (msg.payload.object !== undefined && msg.payload.event === 'VALUE_DB') {
for (var i = 1; i < msg.payload.object.length; i++) {
// Filter Here
let Value = msg.payload.object[i].values.filter((V) => V.valueId.commandClass === 128 && V.valueId.property === 'level' )[0]
node.send([{
topic: "init",
nodeId: msg.payload.object[i].nodeId,
payload: Value.currentValue
}]);
}
}Lastly Good work! |
Beta Was this translation helpful? Give feedback.
-
|
@marcus-j-davies Thank you for looking this over. Those are some good pointers. I have a long way to go to duplicate the functionality I had with Home Assistant. Who knows how this is all going to end up, if it ever does. I'm a continous improvement type. |
Beta Was this translation helpful? Give feedback.
-
|
@marcus-j-davies Making great progress! My switches (including the dual outlet) are working as well as my three types of remote controls. I've named my nodes with my HA entity id names (i.e., "switch.bedroom_plugin_outlet", so I can use all of my existing infrastructure. For the dual outlet I named the node "switch.primary_bedroom_tablet_device_charger_plugin_outlet,switch.primary_bedroom_phone_device_charger_plugin_outlet" (two entity id's, comma separated). Then I can address each outlet separately, by it's unique entity id. I haven't run into any issues with your code. Everything is working as expected, and seems very well though out. Great job. I should be able to migrate from HA very soon. |
Beta Was this translation helpful? Give feedback.
-
|
That's great news! - and thanks for the feedback 👍 I originally created the module for my (very small 5+) network. zwave-js is getting close to releasing V9 of the driver, I will follow this up with v6.6.0 of the module, which will see a tidy up of the UI. |
Beta Was this translation helpful? Give feedback.
-
|
I have long node names that use underscores. I wonder if you might want to line break at underscores in addition to spaces? No big deal if you don't want to. |
Beta Was this translation helpful? Give feedback.
-
|
All events / messages being sent into your flow will have the following shape. {
"payload": {
"node": 10,
"event": "SOME_EVENT",
"object": {},
"timestamp": 1637014660258,
}
}See here for all events and the full wiki. |
Beta Was this translation helpful? Give feedback.
-
|
First of all my compliments, this is a great project, very impressive! I am now preparing to migrate all my devices from my old Veralite after trying Homeassistant, this works way better. My quertion: just like @fabnavigator I am using the node-red dashboard and I am looking for the best way to make my dimmers and switches reflect the actual state of the devices which are also controlled manually. With Veralite / Node-Red I used an event listener (node-red-contrib-mios) that produced event messages when a device was controlled also when using the physical switch or dimmer. These messages were passed through to the dashboard buttons and sliders. I would like to do the same with zwave-js. However, when I connect a debug node to the zwave-js controller node and set the logging to verbose (or silly) I don't see any event messages when I use a physical dimmer or switch that is connected to zwave-js. So, can I only use polling to achieve this? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @henkbb36org, And welcome. Setting debugging options won't (normally) output to the debug panel (unless using Pin 2 Debugging - but that requires that you format the debug messages). As for not receiving events when changing the device manually, there is no need to poll. Providing the device broadcasts changes to the USB controller - your Node RED flow will receive it. The first thing to check is Associations.
You may have 1 or more endpoints here. Each of them will have a Lifeline or similar named group. if it does not - add it. Expand Configuration and look for settings that may hint at producing events or sending updates. |
Beta Was this translation helpful? Give feedback.
-
|
Yes wow, that was it! Thanks a lot! :-) |
Beta Was this translation helpful? Give feedback.
-
|
Sure. It is this device: https://devices.zwave-js.io/?jumpTo=0x0064:0x0001:0x0000:0.0 |
Beta Was this translation helpful? Give feedback.
-
|
Mmm... it has nothing to configure (no settings) Although, I did find another thread about the same issue (with another zwave implementation) If you would like to dig deeper.
If the device is sending us an update, we should see it in the logs. Attach the log file here (as a file). oh and disable logging after - it fills up quickly 😅 |
Beta Was this translation helpful? Give feedback.
-
|
OK, I set logging to debug and used the dim paddle twice and disabled logging again. The node ID of the dimmer is 13 but I don't see anything appearing in the log, perhaps I am overlooking it... Seems to be the same problem as in the thread you mentioned |
Beta Was this translation helpful? Give feedback.
-
I would have to agree, looking at other material on this device - its reporting is extremely basic, and the manual seems to favour its own ecosystem with a 'Wireless Switching Server' or something to that affect. You maybe able to poll the device, say every hour - BUT if its battery operated, you don't have a lot of options sadly. Some devices, need little hacks to their config file, so it maybe something like that, again will let you know, but given this device is not sending anything, I could be missing something that the zwave-js dev may spot. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, really appreciate that! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @marcus-j-davies
I would like to do something fundemental. I have a z-wave plugin outlet and a node-red dashboard switch. If you turn the switch on/off I want the outlet to turn on/off. If I go to the outlet and manually turn it on/off, I want the dashboard switch to reflect it's state (on or off).
I think there's a way to do this without an endless loop. I can probably figure it out (eventually), but I feel I would be reinventing the wheel. Do you have a sample flow that does this?
Beta Was this translation helpful? Give feedback.
All reactions