tazman

Isy portal is needed if you're running the occupany items in the portal.

Try shuting down the eisy with 6 clicks of the multifunction button and unplugging the unit when the light turns red wait 10 seconds and give it a while to start then try accessing it. Sometimes eisy gets hung up and needs a complete power down to return everything to it's proper state.

I believe they can be deleted in ISY where you took this screen shot from. Click on each individual node server and I think there is a delete button in there.

Have you checked the link tables in the motion sensors? Maybe have the event viewer open on level 3 while you trigger the motion sensors?

Have you shutdown and unplugged your "ISY" device? That seems to be a step that can cure some "issues"

This happened to me a couple of times in the past and the only way I know to fix it was to submit a ticket with UDI and they would do something on their end to correct the issue.

As far as I know you have to use a control device/program/variable from Eisy exposed to Alexa with a Routine in Alexa or multiple Routines depending on how much control you want over the device in Alexa. The Virtual node server is the actual name of it. https://github.com/UniversalDevicesInc-PG3/Virtual/blob/master/README.md

You can have some control of Allexa devices from Eisy. You can expose a variable to Alexa as a motion sensor and there is the Virtual node server that you can create virtual switches to use in Alexa. You can also create Routine in Alexa where anything exposed to Alexa from Eisy can control Alexa devices.

I use the regular Ocupancy in the portal so I don't know if this applies but did you setup the configuration in the portal and upload the node definitions? I know when that needed to be done for me it would show the light bulb and I have had updates that required me to upload the node definitions again.

It was a different device but it sounds similar that you might want to try their solution

@CoolToysyour front door needs to be a control item not a status so when the door is opened it activates the program to run as long as the rest of the conditions are met.

Try pressing the button 6 times to power the unit down and when the light turns red pull the plug to remove power for a little then plug it back in to see if that helps.

As was stated above you wire the white from the three wire going to the right box in with the rest of the white wires (neutrals) in the left box.

It looks like the 2 blacks tied together in your left box are the hots which will need to power both switches. You show all of the whites tied together which can not be the case at this time but does need to happen to send the neutral to the right switch and both switches need the white neutral to work. Then the single black wire going up in the left switch I would assume is your switch leg which will tie to the red wire on the left switch. The red wire that goes between the boxes can be capped off on both sides as well as the red wire from the KPL in the right box. To add this is my best guess from your diagram and all wires need to be verified with a meter.

Does your firmware and UI match in Help About? It sounds like you need to clear your Java cache.

I believe the portal one is if you are using the occupancy node server but I don't know if it is used by UD Mobile also. For the Invetory one you will have to delete from IoX using the AC.

OK let's try this again https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x

When you uncheck the Z-Wave support you have to click the save button before you restart IoX or else it does not hold the setting.

On the Configuration/System tab you need to check the box to enable Zigbee Support then press the Save button followed by the Restart Iox button.

The install went good for me I still get the PG3x restart needed but refreshing the browser now gets rid of it without having to shutdown eisy. Node server re-install: Restart node servers after re-installation if it was running Node server re-install: At the end, display a confirmation message The re-install worked with a green box confirmation afterwards. In node server nodes, property variable can be copied using copy icon This is a nice feature!

It was most likely triggered by the query program if you have it. I would disable the program so the only way it will run is when you run it directly from Alexa.

I ran the update on my eisy and everything seems to be working fine. After the commands and a restart of PG3x it still showed PG3x needed to be restarted so I performed the 6 button press shutdown and pulled the plug on eisy after the light turned red then after pugging it back in when it booted the restart PG3x was gone. I have made the 6 button press shutdown and removing power a standard step after an upgrade.

The update went fine for me and I'm able to log into PG3x where I see this image and I even performed the power down 6 button press and unplugged the unit. Everything seems to be working.

I was just upgrading PG3x from 3.1.29 to 3.1.32

I received a reply from Michel and they have the upgrade working now. I was able to to perform the upgrade and it was a success this time.