3.1.0

[marcus-j-davies]

Hi @georgeinva2004

Any ill health to report with 3.1.0? - I'm tempted to release the new version this weekend (maybe even this evening), if 3.1.0 is working ok. it didn't need to address many issues, more of a tightening up exercise.

[georgeinva2004]

Sorry for the late response. I thought I had hit send on my email. No issues.
Thanks for the great work!!!!

[georgeinva2004]

Just installed the prod version of 3.1.0. Did anything get changed on ValueNotification events between the alpha and the prod version? They seem to have stopped working. The driver appears to be getting the events from the device, but I'm not seeing the ValueNotification event firing. I'm forcing the download of the new PSI. Other events appear to be working.

----------------------------------------Driver log-------------------------------------------------------------
2022-06-14T16:57:04.116Z SERIAL « 0x010d00040024055b03488001cc008a (15 bytes)
2022-06-14T16:57:04.117Z SERIAL » [ACK] (0x06)
2022-06-14T16:57:04.119Z DRIVER « [Node 036] [REQ] [ApplicationCommand]
└─[CentralSceneCCNotification]
sequence number: 72
key attribute: KeyPressed
scene number: 1
2022-06-14T16:57:04.121Z CNTRLR [Node 036] [!] [Central Scene] scene[001]: 0
2022-06-14T16:57:04.121Z CNTRLR « [Node 036] received CentralScene notification {
"nodeId": 36,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0x488001"

[georgeinva2004]

PollValue did the trick. Now I just need to reliably correlate the Indicator propertyName to the Central Scene propertyKeyName and I'll be in business. Thanks for the tip!

[marcus-j-davies]

Nice!

The difference between Get and Poll value, is that Get fetches the value from the drivers cache (which is usually kept up to date, as and when things change)

The cache also survives restarts - it writes it to disk.

Poll on the other hand, forces a refetch of that value from the device.

Poll can be used, where you have had some downtime maybe, where the cached values may not be current.

[AlCalzone]

Indicator class doesn't have an event mechanism right? But local values should reflect on the successful set?

Correct. There is no value notification for the Indicator CC, only value added/updated events.

And a Central Scene notification does not influence Indicator values, because there is nothing in the specs that says it should. If the device changes its indicator values in tandem and does not send a corresponding report, "manually" refreshing them is necessary.

[georgeinva2004]

You ever have one of those days where you are overthinking a problem? Well, that was me yesterday. After reading @AlCalzone 's response it occurred to me that using the Indicator command class to determine Scene state was a bad assumption, and would have required more work than was required. Following the KISS principle, I'm simply going to force the Indicator (if the command class exists) to sync with what my controlling app has defined as the scene state. Thanks for the help folks!!!!

[marcus-j-davies]

Everyday!

[georgeinva2004]

No issues. Very stable. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Marcus Davies ***@***.***> Sent: Friday, June 10, 2022 9:41:45 AM To: zwave-js/ZWaveJS.NET ***@***.***> Cc: John M. George ***@***.***>; Mention ***@***.***> Subject: [zwave-js/ZWaveJS.NET] 3.1.0 (Discussion #23) @georgeinva2004<https://github.com/georgeinva2004> Any ill health to report with 3.1.0? - I'm tempted to release the new version this weekend (maybe even this evening), if 3.1.0 is working ok. it didn't need to address many issues, more of a tightening up exercise. — Reply to this email directly, view it on GitHub<#23>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABJAZ4PQH5YZSC5S2XLZLWDVONAZTANCNFSM5YNXEQUQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>