Closed darkbasic closed 3 years ago
The request does sound plausible, but I'm not sure if it is feasibly to do this automagically. At least I couldn't find anything in the specs I've read that these two CCs should be mapped to each other.
Did this work with the OZW backend? A quick search didn't show any code where that could be happening.
I'm a bit hesitant to do this, because I can already anticipate that there's at least one device out there where Binary Switch and Multilevel Switch do different things.
@robertsLando what do you think?
Could be something configurable using the device config file? Maybe a special option
I think this should be a matter of setting the right association groups or something similar. Regarding OZW if I recall correctly it used to work with OZW 1.4 but it doesn't work anymore with 1.6. If I include the device with OZW 1.6 it doesn't even update the power (W) value when I turn on/off the light, while if I include it with zwave-js it does update the power (W). So I guess it's something which gets set during inclusion. Something similar happened to me with the Qubino Flush Shutter in venetian mode, which didn't report the tilt value whenever you changed it using the physical push button with OZW 1.4. The following procedure fixed it: https://community.home-assistant.io/t/integration-of-qubino-zmnhdd1-flush-dimmer/129487/13 With OZW 1.6 it works out of the box, so I guess it's setting those associations automatically.
Could it be something similar for the Flush Dimmer?
This is the manual: https://qubino.com/manuals/Flush_Dimmer.pdf
The following procedure fixed it: https://community.home-assistant.io/t/integration-of-qubino-zmnhdd1-flush-dimmer/129487/13
Both OZW and this driver automatically configure lifeline associations during the device interview. Missing reports are almost always related to misconfigured associations.
zwave-js
automatically uses Multi Channel Assocations (with a target endpoint) if possible, otherwise "normal" node assocations.
For some devices I had to force node associations, because I was getting reports that the reports wouldn't work otherwise. This includes ZMNHDD
!
I'm not sure if the dashboard already allows you to configure associations - if it does, you could try to change group 1 (should include the controller) from a node association (node 1, NO endpoint) to a multi channel association (node 1, endpoint 0)
I see you opened a similar issue in the OZW repo, I'll watch this to see if the maintainers have any more information about the correct behavior.
I'm not sure if the dashboard already allows you to configure associations
@robertsLando does it?
Yes, you can
Control Panel > Groups Tab > Select a Node Then the goups and the target node / endpoint and press add association
While you're at it, try if adding the controller to group 4 changes anything. This might at least give you multilevel switch updates when turning it on with binary switch.
try to change group 1 (should include the controller) from a node association (node 1, NO endpoint) to a multi channel association (node 1, endpoint 0)
Those are my associations for node 2, group 1. Unfortunately I cannot manage to remove the existing one, neither with "Remove" nor "Remove all".
z2m:App Zwave api call: removeAssociations [ 2, 1, [ { nodeId: 1, endpoint: 0 } ] ] +3m
z2m:Zwave Assocaitions: Removing associations from Node 2 Group 1: [object Object] +8m
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +350ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 1 => 1 +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 => +0ms
z2m:Zwave Success zwave api call removeAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +650ms
z2m:App Zwave api call: removeAllAssociations [ 2 ] +1m
z2m:Zwave Assocaitions: Removing all associations from Node 2 +1m
z2m:Zwave Success zwave api call removeAllAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +1s
Any clue?
This should be a node association:
Success zwave api call getAssociations [ { nodeId: 1 } ]
but the remove call tries to remove an endpoint association { nodeId: 1, endpoint: 0 }
(which does not exist)
@robertsLando
I know but shouldn't the removeAllAssociations remove it?
Probably, yeah. I'd need to see the logfile 😅
Here it is: zwave-359840.log
In the log I tried to remove it with "Remove" first, then "RemoveAll".
Strange, there's only the first remove visible in the log. @robertsLando I'm inclined to believe this is a bug in zwavejs2mqtt. The interview and the log from above
z2m:App Zwave api call: removeAssociations [ 2, 1, [ { nodeId: 1, endpoint: 0 } ] ] +3m
z2m:Zwave Assocaitions: Removing associations from Node 2 Group 1: [object Object] +8m
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +350ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 1 => 1 +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 => +0ms
z2m:Zwave Success zwave api call removeAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +650ms
shows that there is only a node association (last line), but zwavejs2mqtt tries to remove an endpoint association (first line).
shows that there is only a node association (last line), but zwavejs2mqtt tries to remove an endpoint association (first line).
Yes, you right. Actually when I call removeAssociations
I let the user specify the association to remove 'manually' (he doesn't select it from the associations list) and as it is multiChannel I also add the endpoint. I will try to improve this in the ui, anyway like I said, shouldn't the removeAllAssociations remove it?
@darkbasic Try to pull last commit https://github.com/zwave-js/zwavejs2mqtt/commit/3def708f8c86c638333ddcd0069a77d93951cb56
removeAllAssociations
That is not part of zwave-js https://zwave-js.github.io/node-zwave-js/#/api/controller?id=managing-associations
That is not part of zwave-js
:rofl: :rofl: Let me go take my :coffee:
Is removeNodeFromAllAssocations
the same?
No no wait I'm calling the right api: https://github.com/zwave-js/zwavejs2mqtt/blob/master/lib/ZwaveClient.js#L1164
I have just changed the name :)
Or maybe it means to remove the node from the other associations, not to remove associations of that node. Tricky :confounded:
Yep, that has an entirely different meaning :) When a node is removed from a network, it should be removed from all associations. This is what this method is for.
You could just call removeAssociations
with getAssociations(nodeId).get(groupId)
to clear a group.
@AlCalzone z2m:Zwave Error while adding associations to 2: Node 2, group 1 does not support multi channel associations! +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +12s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +37s
z2m:App Zwave api call: removeAssociations [ 2, 1, [ { nodeId: 1 } ] ] +11s
z2m:Zwave Assocaitions: Removing associations from Node 2 Group 1: [object Object] +11s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +389ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 1 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 => +1ms
z2m:Zwave Success zwave api call removeAssociations +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +75ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 => +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [] +535ms
z2m:App Zwave api call: addAssociations [ 2, 1, [ { nodeId: 1, endpoint: 0 } ] ] +1m
z2m:Zwave Assocaitions: Adding Node 1 to Group 1 of Node 2 +1m
z2m:Zwave Error while adding associations to 2: Node 2, group 1 does not support multi channel associations! +1ms
z2m:Zwave Success zwave api call addAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [] +1s
@robertsLando z2m:Zwave Assocaitions: Removing associations from Node 2 Group 1: [object Object] +11s
typo is Associations plus json needs to be serialized
@robertsLando I also don't like the fact that once you've changed the placeholder channel ID you can't select the empty one anymore
@AlCalzone I also can't add the controller to group 4
z2m:App Zwave api call: getAssociations [ 2, 4 ] +2m
z2m:Zwave Success zwave api call getAssociations [] +2m
z2m:App Zwave api call: addAssociations [ 2, 4, [ { nodeId: 1 } ] ] +5s
z2m:Zwave Assocaitions: Adding Node 1 to Group 4 of Node 2 +5s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +387ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 => 1 +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => +1ms
z2m:Zwave Success zwave api call addAssociations +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +61ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 1 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => +0ms
z2m:App Zwave api call: getAssociations [ 2, 4 ] +1s
z2m:Zwave Success zwave api call getAssociations [] +550ms
I also don't like the fact that once you've changed the placeholder channel ID you can't select the empty one anymore
What?
z2m:Zwave Error while adding associations to 2: Node 2, group 1 does not support multi channel associations! +1ms
That's really strange as it is has multiChannel flag to true
What?
Nevermind, I saw the slider and I didn't notice you can actually delete the content of the channel ID field.
Anyway, wouldn't it be better to have a "Delete" button near each "Current associations" item instead of the current way of doing this?
Anyway, wouldn't it be better to have a "Delete" button near each "Current associations" item instead of the current way?
Yes it would be more user friendly, I'm just lazy :rofl:
Anyway I've just tried to add a multichannel node association to group 4 and now both the node association and the multichannel one appeared:
z2m:App Zwave api call: getAssociations [ 2, 4 ] +8m
z2m:Zwave Success zwave api call getAssociations [] +8m
z2m:App Zwave api call: addAssociations [ 2, 4, [ { nodeId: 1, endpoint: 0 } ] ] +16s
z2m:Zwave Assocaitions: Adding Node 1 to Group 4 of Node 2 +16s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +319ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 => 1 +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => [object Object] +0ms
z2m:Zwave Success zwave api call addAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 4 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 }, { nodeId: 1, endpoint: 0 } ] +684ms
Something strange is going on here...
@darkbasic I have submitted an ui improvment for associations that you will like :) pull
Something strange is going on here...
Zwave is good, zwave devices are strange :rofl:
z2m:App Zwave api call: addAssociations [ 2, 4, [ { nodeId: 1 } ] ] +5s z2m:Zwave Assocaitions: Adding Node 1 to Group 4 of Node 2 +5s z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +387ms z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 => 1 +0ms z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => +1ms z2m:Zwave Success zwave api call addAssociations +1ms z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +61ms z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 1 => +1ms z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => +0ms z2m:App Zwave api call: getAssociations [ 2, 4 ] +1s
Looks like the device did not accept this change. addAssociations
performs an add command and then requests the updated list. Wonder why the node association showed up on the next attempt though, maybe the device needed time to update?
Zwave is good, zwave devices are strange 🤣
yeah and Z-Wave associations are a f*cking mess.
That's really strange as it is has multiChannel flag to true
If the config file forbids multi channel associations then the driver respects that. @darkbasic You could try and change your config file locally:
In node_modules/@zwave-js/config/config/devices/0x0159/zmnhdd.json
comment out the lines with noEndpoint: true
, then restart.
Just be warned that this could cause the unsolicited updates to stop working.
I have submitted an ui improvment for associations that you will like :) pull
Unfortunately the backend is doing something fishy, because I had both a node association and a group association and after deleting one of them it deleted both...
z2m:App Zwave api call: getAssociations [ 2, 4 ] +10s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 }, { nodeId: 1, endpoint: 0 } ] +13s
z2m:App Zwave api call: removeAssociations [ 2, 4, [ { nodeId: 1 } ] ] +1h
z2m:Zwave Assocaitions: Removing associations from Node 2 Group 4: [{"nodeId":1}] +1h
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +388ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 1 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 [object Object] => [object Object] +1ms
z2m:Zwave Success zwave api call removeAssociations +0ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +16ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 [object Object] => +1ms
z2m:App Zwave api call: getAssociations [ 2, 4 ] +1s
z2m:Zwave Success zwave api call getAssociations [] +594ms
Wonder why the node association showed up on the next attempt though, maybe the device needed time to update?
I don't think so:
z2m:App Zwave api call: addAssociations [ 2, 4, [ { nodeId: 1 } ] ] +2m
z2m:Zwave Assocaitions: Adding Node 1 to Group 4 of Node 2 +2m
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +389ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 => 1 +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => [object Object] +1ms
z2m:Zwave Success zwave api call addAssociations +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +45ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 1 => +2ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 [object Object] => +1ms
z2m:App Zwave api call: getAssociations [ 2, 4 ] +1s
z2m:Zwave Success zwave api call getAssociations [] +561ms
z2m:App User disconnected ndt4_zcnbK4pPDA0AAAC +10s
(waited some time)
z2m:App Zwave api call: getAssociations [ 2, 4 ] +12s
z2m:Zwave Success zwave api call getAssociations [] +23s
In node_modules/@zwave-js/config/config/devices/0x0159/zmnhdd.json comment out the lines with noEndpoint: true
It looks like despite the error it already created the group association, because after commeting them out it shows both:
z2m:App Zwave api call: getAssociations [ 2, 4 ] +7s
z2m:Zwave Success zwave api call getAssociations [] +12s
z2m:App Zwave api call: getAssociations [ 2, 1 ] +2s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 }, { nodeId: 1, endpoint: 0 } ] +2s
@robertsLando I tried the new "Remove all", but it doesn't remove all the associations:
z2m:App Zwave api call: removeAllAssociations [ 2 ] +25s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +26s
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 [object Object] => +2ms
z2m:Zwave Assocaitions: Removed 2 associations from Node 2 group 1 +4ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-2 16 => 16 +337ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-2 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-2 => +0ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 2 +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +252ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-3 16 => 16 +93ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-3 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-3 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 3 +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-4 16 => 16 +337ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-4 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-4 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 4 +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-5 16 => 16 +326ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-5 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-5 => +0ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 5 +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-6 16 => 16 +344ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-6 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-6 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 6 +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-7 16 => 16 +336ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-7 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-7 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 7 +0ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-8 16 => 16 +352ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-8 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-8 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 8 +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-9 16 => 16 +364ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-9 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-9 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 9 +2ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-10 16 => 16 +344ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-10 => +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-10 => +1ms
z2m:Zwave Assocaitions: Removed 0 associations from Node 2 group 10 +1ms
z2m:Zwave Node 2: value updated: 142-0-maxNodes-11 16 => 16 +321ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-11 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-11 [object Object] => +0ms
z2m:Zwave Assocaitions: Removed 1 associations from Node 2 group 11 +1ms
z2m:Zwave Success zwave api call removeAllAssociations +0ms
EDIT: even removing it with removeAssociation (instead of removeAll) doesn't work:
z2m:App Zwave api call: getAssociations [ 2, 1 ] +5s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +2m
z2m:App Zwave api call: removeAssociations [ 2, 1, [ { nodeId: 1 } ] ] +23s
z2m:Zwave Assocaitions: Removing associations from Node 2 Group 1: [{"nodeId":1}] +23s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +403ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 => +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 => +0ms
z2m:Zwave Success zwave api call removeAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +601ms
Hmm that does indeed look very fishy.
z2m:App Zwave api call: removeAllAssociations [ 2 ] +25s z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +26s z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 => +1ms z2m:Zwave Node 2: value updated: 142-0-endpoints-1 [object Object] => +2ms z2m:Zwave Assocaitions: Removed 2 associations from Node 2 group 1 +4ms
This looks like an endpoint association was removed (2nd to last line)
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +252ms
And this is really weird. @robertsLando does z2m cache these results somehow? If not, this does seem like we have a node association created by the Association CC
and nothing for Multi Channel Association CC
. Removing that only uses Multi Channel Association CC
, so the Association CC
association is probably unaffected. 🤔
does z2m cache these results somehow?
I only cache groups, associations are fetched on every request when the user selects a group
@darkbasic Please use dev
branch, I will add edits there
Ok, then I'll have to investigate
@AlCalzone Add investigating
flag :rofl:
@darkbasic could you share your cache file (something.values.jsonl
) please? If @robertsLando didn't change the location, it should be in node_modules/zwave-js/cache
It's in "store" folder now
It's in "store" folder now
Yes, it's in store:
zwavejs2mqtt]$ git status --ignored
Sul branch master
Il tuo branch è aggiornato rispetto a 'origin/master'.
File ignorati:
(usa "git add -f <file>..." per includere l'elemento fra quelli di cui verrà eseguito il commit)
bin/zwave-10331.log
bin/zwave-16501.log
bin/zwave-3679.log
dist/
node_modules/
store/d743ed1a.json
store/d743ed1a.metadata.jsonl
store/d743ed1a.values.jsonl
store/settings.json
@AlCalzone here it is, I also attached latest log
Yup, that confirms my suspicion in https://github.com/zwave-js/node-zwave-js/issues/1090#issuecomment-721699693
I'll probably have some time for a fix later tonight. Will let you know.
@darkbasic https://github.com/zwave-js/node-zwave-js/pull/1094 should enable the controller to remove both the "normal" and the multi channel association. Can you test this from github or should I create an alpha release for you?
Testing from github should work as follows:
npx lerna bootstrap
npm run build
npx lerna exec -- npm link
npm link zwave-js
I'm using zwavejs2mqtt from the dev
branch and node-zwave-js from the association-delete-all
branch.
I added a node association and then tried to add a multi-channel association, but it doesn't show up: is it normal?
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [] +676ms
z2m:App Zwave api call: addAssociations [ 2, 1, [ { nodeId: 1 } ] ] +8s
z2m:Zwave Assocaitions: Adding Node 1 to Group 1 of Node 2 +8s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +320ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 [] => [ 1 ] +1ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 [] => [] +0ms
z2m:Zwave Success zwave api call addAssociations +2ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +678ms
z2m:App Zwave api call: addAssociations [ 2, 1, [ { nodeId: 1, endpoint: 0 } ] ] +4s
z2m:Zwave Assocaitions: Adding Node 1 to Group 1 of Node 2 +4s
z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +284ms
z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 [ 1 ] => [ 1 ] +0ms
z2m:Zwave Node 2: value updated: 142-0-endpoints-1 [] => [] +1ms
z2m:Zwave Success zwave api call addAssociations +1ms
z2m:App Zwave api call: getAssociations [ 2, 1 ] +1s
z2m:Zwave Success zwave api call getAssociations [ { nodeId: 1 } ] +719ms
By the way, did you consider using yarn workspaces?
z2m:App Zwave api call: addAssociations [ 2, 1, [ { nodeId: 1, endpoint: 0 } ] ] +4s z2m:Zwave Assocaitions: Adding Node 1 to Group 1 of Node 2 +4s z2m:Zwave Node 2: value updated: 142-0-maxNodes-1 1 => 1 +284ms z2m:Zwave Node 2: value updated: 142-0-nodeIds-1 [ 1 ] => [ 1 ] +0ms z2m:Zwave Node 2: value updated: 142-0-endpoints-1 [] => [] +1ms
The multi channel association is added as a node association. Not sure if this is due to the config file forcing a node association or if z2m is mixing this up? @robertsLando
By the way, did you consider using yarn workspaces?
I have never worked with yarn. npm@7
is also getting a workspace feature, but I'm not sure yet what this changes exactly.
Btw, can I interpret the above log as confirmation that the association-delete-all
does what it is supposed to?
Btw, can I interpret the above log as confirmation that the association-delete-all does what it is supposed to?
I've been able to remove a node association or a multi channel association, but I couldn't try to delete them when they where both present at the same time, because I can only have a node or a multi channel now (not both).
@robertsLando I've found a new bug: if you edit the channel id field (for example because you added a multi channel association) and then you clear it up, you won't be able to create new associations until you refresh the page:
z2m:App Zwave api call: addAssociations [ 2, 1, [ { nodeId: 1, endpoint: '' } ] ] +14s
It basically targets the "empty string" endpoint.
I've been able to remove a node association or a multi channel association
That is enough for me. At least it seems like your phantom association is gone.
When I turn on the light using the switch command class I expect it to update the level of the dimmer command class accordingly and viceversa. Unfortunately that doesn't happen.
Turning the light on with the switch command class (2-37-0-targetValue) Before:
After:
As you can see the switch on 2-37-0 has been updated to true but the level (2-38-0) hasn't been updated to 99 accordingly.
Turning the light on with the dimmer command class (setting the 2-38-0-targetValue level to 99) Before:
After:
As you can see the level on 2-38-0 has been updated to 99 but the switch (2-37-0) hasn't been updated to true accordingly.
zwave-284642.log