DennisC

and eisy doesn't have a speaker

Will do. I am going to experiment this afternoon with one or two reboots of eisy to check. Any advantage to setting node servers on debug before the reboot, or will that generate too much traffic?

Based on my experiences with Polisy updates, whenever UD says 4 beeps, I have always counted 4 + 1. I am on eisy now and when I updated that, I had to do two upgrade packages before things were normal. Maybe, the process is some items getting updated the first time and some the second time, I don't know. I am just glad things are returning to normal (stability).

You need to delete your Java Cache and reload start.jnlp.

A couple of silly questions..... Are you sure lon/lag is set correctly? Anything in the node server log (set to debug) or PG3x log?

I believe you would need to wake the device up before Querying. I think the button is part of the ZWave set up, I believe Polisy/eisy doesn't customize features depending on battery device or not(?).

For me, it took several minutes for ZWave device status to show up. For battery devices, you might need to wake them up before Querying.

Have you tried right clicking on the device and select write updates? What about trying synchronize with interview?

You could also try Compatibility Mode if adding it non-securely doesn't work.

Try updating to the latest version, 5.5.7 and see if that corrects your issue.

Not sure what UDAC is, but open PG3x to the node server log page and set the log to at least information or debug. Leave browser open to log page. Back in the admin console on the node page for that node server is there a Query button, if so press. If not, try right clicking on the node server name in the left side panel tree and see if Query is there. After clicking on Query, check the log in PG3x. Look for either confirmation info was sent or an error.

Use upgrade packages button in admin console on eisy, or 1 press of the multifunction button. I haven't tried upgrading from UD Mobile. So far so good on v5.5.7.

@jahn It took 2 upgrade packages for me and I had to manually restart PG3x to get node servers running. Also, after pressing the upgrade packages button on eisy, there is a warning popup that opens. For me, the box is empty, all I see is a white empty box.

@bpwwer I received a request from Michel to install v5.5.7. After taking my backup, I set the node server logs to debug and proceeded to upgrade packages on eisy. I had to do the upgrade packages twice to get the admin console to load with some status'. None of the node servers had data in the admin console after about 20 minutes. When I checked on PG3x, none of the node servers were running and attempts to start them failed. I restarted PG3x and all of the node servers started up. When I restarted the admin console, Insteon and Zwave had loaded. It took about 7 minutes for all of the node servers to populate the admin console, however, this is the first restart of eisy since upgrading to v5.5.6 that all of the node servers populated the admin console. I'm wondering if all my issues were related. Anyway, I will try a few more restarts of eisy tomorrow, as I don't want to push my luck further tonight.

I have been working with UD on random reboots running v5.5.6. They indicated this afternoon that they identified the problem and are close to issuing a fix.

Well, we never specifically spoke about it until he asked me what reboot meant. Wouldn't those items restart with an eisy reboot? Other than ssh in to eisy and issuing a UDX restart command, I wouldn't know how to restart those services. If there is something specific you want me to test, I can test it tomorrow morning. I'm out of the house now.

That might be tied to v5.5.4. There was an earlier version (prior to 5.5.5) that wasn't recognizing the dongle consistently, just don't remember the exact version number.

Reboot is a restart of eisy. And, yes, in my case the node servers are starting and running fine. I opened the ticket with UD because I thought it might have been rated to the eisy random reboots, which I am told there will be a fix out today, or the false upgrade packages available notice.

After I upgraded I received that message and it stopped after one or two reboots and several logins to admin console. Also received repeated notices about upgrading packages that UD spent time troubleshooting and determined it was a bug.

Bob, I'm on the releases you listed and experience the same issues. I opened a support ticket with UD yesterday thinking it was related to the random reboots I was experiencing. I have waited 15 minutes for node servers to populate the admin console. In my case, the node servers are running, but don't populate until queried. The node servers I experience this with is Weatherflow, Notification, Wireless Tags, and sometimes TimeData. Weatherflow doesn't have a query button associated with it on the node page, but you can right click on the name in the left hand tree and query from there.

You are on 5.5.4 and the latest firmware is 5.5.6 and a new one is expected before end of day. Earlier firmwares have some issues, you should consider upgrading, it may correct your issue. If not, this is the closest match I found in the wiki: Can't connect to ZMatter Z-Wave board / dongle Sometimes the USB ports need to be reset within Eisy / Polisy. The simplest way to do that is to restart Eisy / Polisy (not just IoX). This will likely solve the connection problem. If that doesn't solve it then the problem may be due to Z-Wave network traffic. Some Z-Wave networks with a high amount of constant network traffic can prevent IoX from detecting the port being used by the ZMatter Z-Wave+ board / dongle. The port it is using will likely be either cuaU0 or cuaU1 You can override port detection by doing the following: Do this from a browser (if you use Help | About in Admin Console it will show your IP address e.g. something like 192.168.0.51) http://<your_polisy>:8080/rest/zmatter/zwave/port/name/override/set/cuaU1 You should get this back (its important you see the 200) <RestResponse succeeded="true"><status>200</status></RestResponse> Restart IoX and it should connect to your ZMatter Z-Wave board / dongle If it does not connect, repeat the process but use a different port.

This is a bug that UD is working on correcting. I had some conversations on this with them yesterday. For now, on a restart, I have been manually querying the nodes.

eisy is currently running v5.5.6 and you mention 5.5.4, is that what you are currently running? If so, maybe an upgrade will correct your issue? If you decide to update, be sure to take a backup first, in case you need to restore it.

FYI, just in case you were not aware, you can add more than one ssid's, so wouldn't matter which one you connect with.

I understand about the desire for a quick, easy, and reliable app, but I never found one. When I first set location home/away with Tasker I had some issues, but after some tweaking, it has been very reliable. We have been using this set up for more than 5 years (?) and it has been solid for at least 4-5.