forum

I have not had this problem re-occur in a very long time (since the 3.1.0 upgrade I think) so it is probably fixed!

I don't know how to get the logs. I can only tell you I just restarted my z-way-server 3 times. 1st time device 38-86-132 marked as failed 2nd time device 12-186- 211 3rd time device 38 I took the Uzb stick and turned on silabs PC controller: No device marked as failed. Put the Uzb back and turned o...

No need, my data already proves that the serial API does not return the device as failed given that no other controller shows these devices to have fail using the uzb and not even the z-way server since the failed devices change every time.

I am 100% sure that the chip is not responding that the device is dead. I can plug it into the silabs pc controller and show you that none of the devices ever is tagged as failed. At every single z-way-server start 1 to 3 of my devices show up as failed on z-way and they are never the same one. I ca...

Can you check if is failed field is true or false for such device in EUI? Because in smart home UI there is additional logic on top of EUI They show up as isFailed = true and it is actually the command I use through the JS API to make isFailed = false. I can see from the command queue during the z-...

It appears to restart where it previously stopped and therefore has the tendency to run out of space. I really don't know how to get around it. I just retried until it took.

It isn't a CRC problem. It is an issue with the tool starting to write the firmware code from the wrong place it seems. I had to go through 50+ retries to finally get it to take. Same problem on the razberry as with the uzb. No need to shutdown and power-on. it makes no difference.

Seems to be some translation problem with the previous post but... I tend to agree. Upon reboot of the server (not of the zwave chip which has remained on with no reboot for the past 6 months), I can still see randomly devices coming up as "dead". Because the devices changes all the time a...

It seems like you are confusing things. The 3 node limit is only on z-way and is indeed a license needed to use the z-way software on the uzb. It is different from the problem you have with inclusion which is more likely a device/openzwave problem.

After a lot of pain, I finally was able to upgrade the uzb with the ZME tool and booted the z-way-server. So far no false IsFailed report.