For those who are part of the 0.25.x beta test, we are releasing new firmware: Version 0.25.20 Hub Targets Samsung SmartThings Hub (Hub V2) Samsung SmartThings Hub (Hub V3) (2018) Release Date 2/27/2019 Release Notes Enable Z-Wave Network Wide Inclusion by default when entering inclusion …

Wholeheartedly agree. You mentioned to me that the hub missing the NIF might be due to excessive traffic on my network. While it may be obvious to your trained eye when looking at the logs, it may not be for the average user. Is there any way for the platform to rate the traffic level so the user ca…

Wow, that is a really good idea. I will make an internal ticket about your suggestion and perhaps find a way to expose that info to the user.

On a related note. If the DTH does request a NIF from the device, if that information wasn’t available while pairing you said it fills the info with 0000. If the NIF comes in later does the platform update the information? I’m thinking about FLiRS devices and listening devices. I have seen this happ…

This should be a simple thing to do. A small bit of logic added to the refresh() method that calls sendCommand(zwave.manufacturerSpecificV2.manufacturerSpecificGet()) anytime the MSR is all zero’s. (or possibly manufacturerSpecificV1 depending of the device)

That’s easy and many DTH’s do that already however he does not update the zwInfo field which still shows 0000. So I was asking what command response would cause the zwInfo field to be updated? Many DTH’s including the stock ST DTh’s use zwInfo to decide how to take actions for a range of things fr…

Having a “refresh” button under the device Data or Raw Description to force update of the data in the node frame would be great, aside from failed inclusions, it would also be helpful for replaces of similar devices, or out of band firmware updates.

Is it feasible to detect during inclusion that the NIF was missed (or corrupted) and send a request for it again before setting up the device?

With a sleepy device it may go to sleep before the request can be completed. I was suggesting that if a NIF is not received leave the configuration open to updates. At the next wake up send a NIF request or got active devices request it right away and the update zwInfo and the configuration once the…

[image] RBoy: and also preserve the current logic of sealing the database What is the logic behind “sealing” the DB? How should firmware updates be handled that change the NIF or device replaces where a switch might be replaced by another switch, but from a different vendor?

Hub Firmware Beta 0.25.20

Developer Programs Hub Firmware Beta

Kianoosh_Karami (Kianoosh Karami) March 1, 2019, 3:47pm 34

We currently do not support the ability to update the zwInfo field after the device has been created.

Topic		Replies	Views
Hub Firmware Beta 0.25.19 Hub Firmware Beta	32	1823	February 27, 2019
Hub Firmware Beta 0.34.x Hub Firmware Beta	75	6876	May 11, 2022
Hub Firmware Release Notes - 25.26 Announcements hub_firmware_update	473	39743	May 28, 2019
Hub Firmware Beta 25.26 Hub Firmware Beta	111	6312	April 9, 2019
Hub Firmware Beta 0.25.32 Hub Firmware Beta beta	46	2465	May 14, 2019

Hub Firmware Beta 0.25.20

Related topics