DennisC

Based on @Steve L comment, try triggering motion and immediately wright changes to device.

It's good that you were able to add it. Make sure the device is awake (if battery powered), right click on it and select write updates. If that doesn't work, I would suggest opening a support ticket so UD is aware of the problem. Reporting it is the only way to make sure it gets fixed. Open UD Support Ticket

Glad you got it working.

I don't think it will resolve itself without intervention. The only further suggestion I have is to power down eisy and after it shuts down, remove the plug for a few minutes and then power it back up. If that doesn't work, then flag @bpwwer to look at you posts (3 & 6 post up) and see what he thinks. He maintains pg3x and offers assistance freely.

Not sure I understand your question. I use the Elk Node Server and I can assure you it is genuine and not fake.

Hmmm, used for years has me wondering if the 2 year period for your account license expired. You might want to sign directly in to UD portal via a web browser and check your expiration date license on the eisy in question. If you migrated the account from another device, it might not of had a lot of time left. If you used a trial license it might have ended.

Are you running any node servers and are they populating in the admin console? Is this a new portal account or have you been using it on the same machine for awhile?

Glad you got it to work.

Interesting, did you excluded both before trying to add them?

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.