johnnyt

zwave restore bug was fixed in an unadvertised update (6.0.4) a few days ago. After the upgrade I was able to replace my dongle following the steps outlined in my original post without needing steps 7 and 8.

Got some hands-on UD support yesterday and there's a problem with zwave restore in latest IoX version - perhaps a bug in a recent update to the zwave libraries. Surprised no one else reported it but then again restoring a backup usually only happens after some sort of failure that requires it. I guess this is why it's important to test your backup/restore process every now and again before you really need it. Hopefully this gets fixed soon because if my (and/or others') current zMatter dongle fails we'll be dead in the water.

I was an early adopter of eISY (also of Polisy). I remember being advised to replace the power supply for the Polisy and I did that. Is it really an issue with the eISY too? With respect to both the power supply and USB port, I have to wonder why one dongle would fine but not another. Would different dongles bought at different times have different power consumption? One thing I thought of doing was swapping out the complete set (eISY and dongle) but that's a big pain / last resort as I believe different eISY h/w comes with different portal and plug-in licenses. I would need to get all that stuff transferred over and (I think) do a fair amount of configuring, although I've never done it so I'm not sure.

I opened a ticket about a week ago and included several logs from my initial attempts. The lack of a reply lead me to post here. I just added explanation I posted here around my second session of trying to replace it. Hopefully I do hear from someone.

So I started the process over making sure antennas were connected inside and in the right place (Red = Zigbee // Yellow = Z-Wave.) I also made sure Zwave was ON in the config tab and even tested both dongles after doing a factory reset using my spare eISY and a spare Zwave device. The test included verifying that things worked consistently including at a fair distance on the other side of the house two floors away while both my test and prod eISYs were running right next to each other. One of my dongles, although recognized enough for the Zwave menu to appear in the AC, stopped communicating during my testing and I could not get it to work so it's been relegated to my e-waste box. Using the now proven fully working 2nd spare dongle, I went through the restore process in my original post (after doing factory reset while it was on my test eISY) and the same exact problem occurred. The new, restored (spare) dongle refused to connect with any of my prod devices. It reports them all as 'not awake' and there's no status being reported to the Admin Console. This after a "Restart IoX" then, when that didn't work, a reboot, Also this is with "Query at Restart" enabled in config tab, and I followed it with a manual Query All a good 5 mins after system stopped being busy due to restart. (I also had disabled 95% of my programs to minimize resource contention.) I can see from the event viewer and by using Xray function that the restore worked and the dongle has all my prod devices in its memory. I really don't know what to think. Did I miss anything? How likely is it that my spare dongle is defective even though it's working fine using my spare eISY?

I checked them and they're correctly connected, i.e. Red = Zigbee // Yellow = Z-Wave.

you can still login the old way by adding "https://<your.eISY.IP.address>:8443/desc" to the launcher list and electing it instead of the entry without the 8433 port number.

Has anyone had problems replacing their zMatter dongle? My current zMatter stops working after a few weeks and I power cycle eISY to get it working again. It's happened about 3 times now so I decided to replace it. I've tried with two spares I have that were working last time I checked them and in both cases they were not able to communicate with any of my devices. I either get a message that device is "not awake" (most of them) or err=1 (a few). Most of my devices are AC powered and therefore always awake. Not a single one works. Here's the process I followed: 1. backup zwave 2. backup IoX 3. power off eISY 4. swap out zMatter dongle 5. power on eISY 6. restore zwave 7. restart IoX 8. power cycle eISY (after restarting IoX didn't result in things working) I tried this with 2 different spare zMatter dongles. I also tried doing a factory reset on the 'new' dongle before step 6 (restore zwave). This deleted all zwave devices in IoX so I did a restore IoX then restore zwave again. Same outcome. I do see in Event Viewer that the zwave restore was successful. I also tried letting things settle after startup with new dongle and after the restore to make sure it wasn't just a question of time or resource contention. I can put the old one back in and everything works fine. I worry I'm living on borrowed time with the old one and would like to be able to replace it. Am I missing a step? Is the restore zwave function broken? Any help would be appreciated.

This plug-in worked for me intermittently after I upgraded for eisy-ui 0.7.2 about a month ago but it's broken for a little while now such that neither a plug-in restart or an eISY restart fixes it. <snip> UPDATE: Today's problem was a unusual issue related to something else. Ignore this (I don't see how to delete it)

@bmercier I've submitted a ticket, as requested. I'm glad to hear the call to the mothership is encrypted even if the rest of the local traffic is not. On that note, why can't we use https with rest locally?

So I can't do eisy.local. It doesn't resolve because I have eISY on a separate IoT subnet (VLAN), which protects devices on my main subnet from all my Internet of (Insecure) Things devices. I tried http with IP address and, while it didn't chew through RAM and responded quite quickly, it still gave me 404 error Problem with using http (I thought) is that I'm sending my portal userid and password in the clear and I don't really want to do that.

using https://192.168.100.249/

Am on 0.7.2 (had this problem on previous versions too) When I open home page (or select "Nodes"), Chrome works for a while and either gives me error 404 or crashes. I can see my RAM going up to 95% (mostly Chrome climbing above 6 GB ) in Task Manager before the crash. Firefox doesn't doesn't chew up RAM as bad (maybe 2GB) but it keeps loading and loading and loading for minutes then returns 404 With the Programs tab, it shows them almost immediately but keeps loading and Chrome soaks up all the RAM again. Firefox also shows programs but keeps loading until 404 without soaking RAM the way Chrome does. I do have lots of nodes and programs but I don't see this kind of RAM consumption with Java AC. It peaks at ~1.5 GB

I upgraded my eisy recently and noticed this morning that PG3 system log entries are timestamped 2 hours behind. The OS time is correct (checking through SSH), as is the Admin Console time. Am running IoX 6.0.0 and PG3x 3.3.23.

Has anyone found solution to this? After upgrading yesterday and now at 0.7.1 of eisy-ui, I also am getting the 404 error message when I try to add a tile. Have done 2 reboots and 3 Re-install All Plug-ins. No joy.