DennisC

I think responded to your other post. Try rebooting one more time. After shutdown pull the plug for a bit and then power up. Wait 10 - 15 minutes before trying to login. Also confirm you are being asked to login to the portal and you are using the correct credentials for both logins. PG3x uses the admin console login, which might not be the same as the portal login.

One node server or PG3? If PG3, try power cycling the system one more time. After shutdown pull the plug for a minute.

I would suggest opening a ticket with UD spelling out exactly what you did. Not sure I understand the "reinstall of PG3" and the reason for doing so.

I'm getting it also, sometimes frequently. I had reported this to UD on v5.5.6 and now it is happening on v5.5.7. I owe UD a report on .y testing of a bunch of issues on 5.5.7, so I will pass this on to them.

Glad you got it working.

The login should be the same as you use for eisy, have you not changed user from the default (something you should do)? However, you should have received a portal login before you could enter login for PG3x, did you login in to the portal? If you didn't receive that login page, I would suggest you reboot eisy.

Not sure, maybe try it both ways. I looked at the Sun node server looking for instructions, but the link doesn't work. I copied this from TimeData: Configuration Enter latitude in the form 12.3456, negative is south Enter longitude in the form 123.4567, negative is west

I believe he is speaking about 10 concurrent subscriptions, not number of node servers.

I rebooted a few times and all of the node servers loaded. They take a little time, about 7 minutes, but they all loaded with a query.

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.