Discussion about setting things up and learning the ropes #50
-
|
Alright I am at a point where I am wanting to just ask "how do I do a thing" so I'm moving over to discussions. First question: Is the nodes list available as a JSON file? If so, where? I assume Basically wanting the JSON that makes this list: PS: please let me know if you prefer one discussion per question - or if you prefer keeping a running discussion for all my setup questions. I don't want to spam your repo... |
Beta Was this translation helpful? Give feedback.
Replies: 15 comments 85 replies
-
|
Hey! Discussions are perfect for long running things 👍 So,
There is a file that holds the nodes, but the list you see isn't the result of it (not directly anyway) This is the file created by the Z-Wave JS Driver, and is used for the Driver to store/manage the metadata of your nodes.
This will get you a very nice (and detailed) output - oh, and is the message used to generate this list let Message = {
payload: {
class: "Controller",
operation: "GetNodes",
}
}
return Message;Each node in the result has the following:
|
Beta Was this translation helpful? Give feedback.
-
|
Get nodes is awesome. Perfect. Next question: I have a couple of binary switches which use endpoint 1 instead of the more common (in my house) endpoint 0... For some reason, they aren't sending updates the same as endpoint 1 is sending through the controller node. When I send this message my light turns on (or off) as expected but there is no feedback from the controller node. I also checked on a node 12 device node and I get nothing. I would expect to get a "VALUE_UPDATED" message as I do when I'm controlling any of my endpoint 0 things... payload: {
"node": 12,
"class": "BinarySwitch",
"operation": "Set",
"endpoint": 1,
"params": [
true
]
}The device in question is this one |
Beta Was this translation helpful? Give feedback.
-
|
And since we are learning the "get nodes" command - here is the result of this (node 12) from get nodes: {
"nodeId": 12,
"name": "BackPorch",
"location": "SensorSwitch",
"status": "Alive",
"ready": true,
"interviewStage": "Complete",
"zwavePlusVersion": 1,
"zwavePlusNodeType": 0,
"zwavePlusRoleType": 5,
"isListening": true,
"isFrequentListening": false,
"canSleep": false,
"isRouting": true,
"supportedDataRates": [
40000,
100000
],
"maxDataRate": 100000,
"supportsSecurity": false,
"isSecure": false,
"protocolVersion": "4.5x / 6.0x",
"manufacturerId": 99,
"productId": 12338,
"productType": 18765,
"firmwareVersion": "5.39",
"neighbors": [
10,
11,
13,
14,
16,
17,
18,
19,
2,
20,
21,
22,
23,
24,
25,
26,
27,
28,
29,
3,
30,
32,
33,
34,
35,
36,
37,
38,
4,
40,
41,
42,
44,
45,
46,
47,
48,
49,
5,
50,
51,
52,
53,
6,
7,
8
],
"deviceConfig": {
"filename": "/home/pi/.node-red/node_modules/@zwave-js/config/config/devices/0x0063/26931_zw4006.json",
"manufacturer": "GE/Jasco",
"manufacturerId": 99,
"label": "26931 / ZW4006",
"description": "In-Wall Smart Motion Switch",
"devices": [
{
"productType": 18765,
"productId": 12338
}
],
"firmwareVersion": {
"min": "0.0",
"max": "255.255"
},
"associations": {},
"paramInformation": {
"_map": {}
},
"compat": {
"valueIdRegex": {},
"treatBasicSetAsEvent": true
},
"isEmbedded": true
},
"isControllerNode": false,
"supportsBeaming": true
}``` |
Beta Was this translation helpful? Give feedback.
-
|
I wonder if Association groups has something todo with it. available since 3.3.0 let Message = {
payload: {
class: "Associations",
operation: "GetAllAssociations",
params:[12]
}
}
return Message; |
Beta Was this translation helpful? Give feedback.
-
|
I'm running 3.3.0 - output from that looks like:
|
Beta Was this translation helpful? Give feedback.
-
|
Ok can you do Interestingly, I don't see anything for endpoint 1 - so this might be a clue |
Beta Was this translation helpful? Give feedback.
-
|
Just tested the device sending commands to endpoint 0 instead and it still controls the light - but still doesn't send updates "out" of the controller node. Doing GetAllAssociationGroups now |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
The only times I do get the expected message is if I hit the button on the switch or if I command it through the UI panel on NR
|
Beta Was this translation helpful? Give feedback.
-
|
Ok - and you get the result via a node message? |
Beta Was this translation helpful? Give feedback.
-
|
Correct. If I control it on the switch or the UI panel I get this type of message from the controller node: {
"node": 12,
"nodeName": "BackPorch",
"nodeLocation": "SensorSwitch",
"event": "VALUE_UPDATED",
"timestamp": "2021-05-01T05:36:08.107Z",
"object": {
"commandClassName": "Binary Switch",
"commandClass": 37,
"endpoint": 1,
"property": "currentValue",
"newValue": true,
"prevValue": false,
"propertyName": "currentValue"
}
}``` |
Beta Was this translation helpful? Give feedback.
-
|
Ok, can you fire up a browser debug window (network tab) - do the change, and see what is sent? |
Beta Was this translation helpful? Give feedback.
-
|
Whew asking the hard questions now. I think I found it: |
Beta Was this translation helpful? Give feedback.
-
|
Yup - thats the one. Just out of curiosity can you do let Source = {nodeId: 12,endpoint: 1}
let Group = 1
let Destination = {nodeId: 1}
let Message = {
payload: {
class: "Associations",
operation: "AddAssociations",
params: [Source, Group, [Destination]]
}
}
return Message; Then send a message to change the state (again on EP 1) The other API (which the UI uses) might cause a different update to happen. you can remove the association switching to |
Beta Was this translation helpful? Give feedback.
-
|
Edit: I figured there's not much reason to try sending the command again since the association didn't work... |
Beta Was this translation helpful? Give feedback.
-
|
Ok, At least we know, its not an association. Send the message for EP 1. |
Beta Was this translation helpful? Give feedback.
-
|
Log file time. Right after startup and "all nodes ready" I turned the switch off then back on using EP 1. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'm going to chat to the Z-Wave JS Driver dev on slack. Be back soon |
Beta Was this translation helpful? Give feedback.
-
|
So I've gone back through my on/off devices and I have a few which are acting like this. Could be helpful information for the drivers guy. All of my dimmers are fine. Working as expected. My GE on/off switches are good. Working fine: The switches with motion detectors (node 12) and my outlets are the weird ones. Not working: I haven't yet worked on setting up my other devices in nodered yet so I'm not sure what their status is. I never noticed this issue with zwavejs2mqtt (been running that since late last year) |
Beta Was this translation helpful? Give feedback.
-
|
Node 12 is absolutely silent. Node 37 (dimmer which is behaving nicely) has a lot to say - I'll spare you the log, I copied it to a text edit document, it's like 19 pages printed. |
Beta Was this translation helpful? Give feedback.
-
|
ok. sounds like setting values for multi channel devices via the CC API - doesn't produce an update (but does using the ValueAPI) This is a driver thing. just for reference. remove the metadata updated event listener I'll raise an issue with the driver (for CC API it seems) |
Beta Was this translation helpful? Give feedback.
-
|
If you don't mind, post a link to your issue so I can watch the progress. Anyway, awesome progress today. I've now moved all my homekit lights and dimmers from mqtt over to 100% nodered. I like taking away extra layers. |
Beta Was this translation helpful? Give feedback.
-
|
Yup. I'll talk to him first on slack, and see what happens, will link to the issue when raised. Many Many thanks 👍 Please holla for anything else. |
Beta Was this translation helpful? Give feedback.
-
|
I have an update (a good update) Device's should send an Update, as per specification (regardless of how it was updated) Now then, However, the CC API does not do this check, and for the times you do get a value updated event, is because the device did follow spec and send the update. Seems to be devices with > 1 endpoint have trouble sending updates after the value was updated by a command, but this compliance issue is hidden by how the Value API internally gets the updated value. In fact - the log does show we don't get a The fix: I'll poll the updated value when using the CC API, I'll get this in for 3.3.1 See: #51 |
Beta Was this translation helpful? Give feedback.
-
|
Alright so I’m trying these value ID things - and I’m getting the list without any trouble. But if I send a value, nothing happens. I believe my ValueID is 24: But I’m sending a message with this function where msg.payload is true, false, 1, or 0 - and nothing happens at all… let Message = {
payload: {
node: 21,
class: "Unmanaged",
operation: "SetValue",
params: [24, msg.payload]
}
}
return Message; |
Beta Was this translation helpful? Give feedback.
-
|
Well yeah that works better! I was expecting some cryptic number for “ValueID” not just an object. Now I’m sending just as you showed and I am getting the proper feedback! I think I like this way, I can simplify my functions a bit. I’m using global context to store a little object about each switch so I’ll just add the important ValueID to that and should be all set. |
Beta Was this translation helpful? Give feedback.
-
|
Yup, its a pretty instant API the Value one, just a bit cumbersome to start with, and work out |
Beta Was this translation helpful? Give feedback.
-
|
I may switch to using it one day - By I use some complex values which won't work for the ValueID API (as it only supports one value) and it must be primitive |
Beta Was this translation helpful? Give feedback.
-
|
Right, I already noticed that I can't send transition time to my dimmers with the unmanaged option. I'll probably leave dimmers how they are (all working great on value api) but switch my on/off things to unmanaged. |
Beta Was this translation helpful? Give feedback.
-
|
this is why I bridged both APIs - best of both worlds |
Beta Was this translation helpful? Give feedback.
-
|
Also a little hint, |
Beta Was this translation helpful? Give feedback.
-
|
So - next question... any way to make it spit out all the values it knows about a node? or even all nodes? Looking for a good way to have all the right values sent around nodered on startup. |
Beta Was this translation helpful? Give feedback.
-
|
I'm the same! I love groups. I try to keep anything "finished" in a box.
|
Beta Was this translation helpful? Give feedback.
-
|
I'm abusing the group functionality right now! |
Beta Was this translation helpful? Give feedback.
-
|
OK - I like Groups - Simples!
|
Beta Was this translation helpful? Give feedback.
-
|
Glad I could contribute something to your setup! PS: you don't use any of the messages coming from the controller? |
Beta Was this translation helpful? Give feedback.
-
|
Since the introduction of the status text update, most things are covered. Good observation though 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Been digging. GetValue (Z-Wave JS -> getValue) actually returns the last know value (in 99.99999% of cases is current). And upon the driver starting up, it restores these values. The values later, are of course updated when the Driver receives updates. The UI therefore is using the same cache - which again is 99.99999% current. I could look to add methods to return this cache in a future version, but getValue is asynchronous, so I will need to do some work, to incorporate some waiting before returning the cached values package. |
Beta Was this translation helpful? Give feedback.
-
|
I'll put this in for 3.4.0 -> #53 |
Beta Was this translation helpful? Give feedback.
-
|
Oh very nice! Sounds like a great option. |
Beta Was this translation helpful? Give feedback.
-
|
Just a quick update - the code changes are done (have been for the last few days), to allow grabbing the cache DB. How is your network?, is the Node Red Z-Wave driver running well for you? |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Good to know. I'm looking to UI-fy Association management at some point - but that's further down the road. 3.4.0 is looking like this (documented in my dev branch)
|
Beta Was this translation helpful? Give feedback.
-
|
Sounds like a great release! What's "UI-fy Association management" mean? One of the best parts of moving from mqtt to nr is having all the Zwave config right next to me while I'm creating flows. It's a great upgrade from using 2 separate interfaces. |
Beta Was this translation helpful? Give feedback.
-
|
To manage Z-Wave associations, it can only be done with messages currently. UIfy is a term I made up about 30 minutes ago 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I understand now. UIfy is apparently the name of a UI building company... I was a little worried you might have plans to change the awesome Zwave UI panel I got confused I think the zw mqtt project uses vuetify for their UI Too many things to keep track of! Don't mind me, carry on |
Beta Was this translation helpful? Give feedback.
-
|
haha no, |
Beta Was this translation helpful? Give feedback.
-
@hufftheweevil, if we ever add association management to the UI (which will be nice in the future) |
Beta Was this translation helpful? Give feedback.
-
|
Hey! @crxporter Just a courtesy call to check your newly 700 series network is working well with the z-wave node-red plugin? |
Beta Was this translation helpful? Give feedback.
-
|
Much Like X10. it was very (and may still be regarded as) the most reliable system (compared to the now wireless standards) Plus the fact, its device types were limited (no motion sensors or anything like that) |
Beta Was this translation helpful? Give feedback.
-
|
Oh the device communication was excellent. My house was built in 1999 and the wiring is just fine. I'm still convinced they've got some of the best hardware on the market. But decent software is nowhere to be found. |
Beta Was this translation helpful? Give feedback.
-
|
ps - if you're on discord we really should just shoot the breeze. I feel like you've got a lot of interesting things to say. Find me there at |
Beta Was this translation helpful? Give feedback.
-
|
I'm all over slack (Node-Red's workspace and Z-Wave JS'es), but could do with a stretch 😄 |
Beta Was this translation helpful? Give feedback.
-
|
The @NRCHKB crew hangs out on discord... I made a slack account for a couple questions I had for the zwavejs2mqtt guy a while ago, but I haven't been back since... |
Beta Was this translation helpful? Give feedback.
@crxporter,
Been digging.
GetValue (Z-Wave JS -> getValue) actually returns the last know value (in 99.99999% of cases is current).
These values are actually stored in
{Home ID}.values.jsonl- A Line-By-Line JSON FormatAnd upon the driver starting up, it restores these values. The values later, are of course updated when the Driver receives updates.
With this in mind, you could actually grab the values, without fear it is causing a Huge network spike.
The UI therefore is using the same cache - which again is 99.99999% current.
I could look to add methods to return this cache in a future version, but getValue is asynchronous, so I will need to do some work, to incorporate some waiting bef…