Is this UZB1 stick damaged?

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
ekkzk5f
Posts: 18
Joined: 20 Feb 2016 00:41

Is this UZB1 stick damaged?

Post by ekkzk5f »

I have a Z-Wave.me UZB1 stick in use which is not working properly anymore with a Open-ZWave library based application. Other UZB1 sticks are working fine with the same software, so it is for sure no problem of the application.

This one stick receives after start of the application only 5x notifications of the Type_Notification for the node 255 (which was never included, probably it is invalid number).
No more notifications, no bootstrap of the network - silence!
When looking to the OZW_Log.txt:

Code: Select all

Error, mgr,     Manager::GetDriver failed - Home ID 0x00000000 is unknown
Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
So it looks like the Home ID is now 0x00000000, before it was 0xf2de4e64

I've already tried SoftReset, restart application, reboot system, remove or restore of the zwcfg*.xml file... nothing helps.

Is this a hardware problem of the UZB1 stick?
Last edited by ekkzk5f on 19 Mar 2017 03:10, edited 1 time in total.
User avatar
PoltoS
Posts: 7649
Joined: 26 Jan 2011 19:36

Re: Is this UZB1 stick damaged?

Post by PoltoS »

Please check it's home ID. Looks like a known issue (solution here: http://razberry.z-wave.me/index.php?id=29 - search for 5555555)
ekkzk5f
Posts: 18
Joined: 20 Feb 2016 00:41

Re: Is this UZB1 stick damaged?

Post by ekkzk5f »

Thanks for your feedback,
the software tries it with home ID 0x00000000 which is for sure invalid. Before It worked with 0xf2de4e64 on the same UZB1 (I've updated my fist posting with logfile details).
So it looks like none of the hints on the mentioned RaZberry support page helps for my UZB1 stick
User avatar
PoltoS
Posts: 7649
Joined: 26 Jan 2011 19:36

Re: Is this UZB1 stick damaged?

Post by PoltoS »

Well, you can try the one from 55555555, but it will erase all your data on the dongle (looks it is already lost). If it will not help, looks the EEPROM on the UZB1 is damaged. Usually this is due to ESD or a spike in powering voltage.
Post Reply