Hi,
Is it possible to do a hard rest with hassio for the zme_uzb1 stick? I only found the “soft reset” button…
If no, how can i set this stick to factory settings?
Thanks!
Stefan
Hi,
Is it possible to do a hard rest with hassio for the zme_uzb1 stick? I only found the “soft reset” button…
If no, how can i set this stick to factory settings?
Thanks!
Stefan
I have the same problem? Can anyone help? Or is there any other way to reset the stick without home assistant.
Same problem here, the documentation for this stick says NOTHING about hard resetting it, which is extremely important for a Z-Wave controller
Hi, sorry for the late answer.
What i did to reset my z-wave controller: I installed “Z-Way” on another SD-Card for my raspberry pi
https://z-wave.me/z-way/download-z-way/
With Z-Way you can hard reset your Controller.
Excellent, thanks!
Hi,
Just to mention another (simpler) way - run this command from SSH:
sudo -s echo -ne “\x01\x04\x00\x42\x01\xB8” > /dev/ttyACM0
and it will do the magic. Originally posted on the wave.me forums: https://forum.z-wave.me/viewtopic.php?f=3419&t=24217
just pay attention that it will not work with hass.io (you will need to connect the UZB to any other rasp* OS and run it)
That’s very interesting, and I assume that key is what is supposed to be used regardless of your network key, right?
Also, I think this could work well for manual installations of HASS.IO in Docker, I have an underlying Ubuntu VM which should not create the issues that HassOS would, so it could work on the same physical machine.
Hi johnflorin, sorry for the late reply, not sure how I missed your reply.
yes, I don’t think it is related to the network key (which is a key for the security communication of the zwave network).
I don’t think it’s related, but for the moment I fail to connect any of the modules, even one that I hard reset. Also tried to exclude them, to no avail. I’m still trying to figure out what is going on (I read somewhere that hard reset does not eliminate the association of the module with the controller, even though the controller as was defined before does not exist anymore). I guess I’ll post here once I’ll solve or on a new thread once give up
I’ve just added successfully a new module (out of the box). So we can discriminate any problem from the UZB controller after reset using the command above.
Seems that my problems are due inability to exclude installed modules prior to re-include them on the ‘post-reset’ controller.
Because hass.io is an OS of itself (or something of that sort) that does not allow you the same interaction as regular Linux OS. You need a Linux OS you can interact with.
I think