tazman

@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.

When I run upgrade packages on my eisy it runs the pkg program but the system does not seem to update. IoX is on 5.6.2 and PG3X is 3.1.29. I submitted a ticket to see what is happening.

For variables you would have to use them with programs.

The virtual node server can be used to create a switch. I never tried it but you might be able to change a variable from Alexa.

Awesome Panda88 you got it! The node created in the AC is now called EV1 instead of the car name which does not matter to me and everything looks good to me initially. Thank you for your quick response!

I did have the log on debug and I don't notice anything else but I can PM you the log later today to see if anything else looks wrong to your trained eye. Thanks for the quick reply!

Is anybody else having issues with the node server working? I'm getting this error 2023-06-12 20:08:49,313 Thread-6 udi_interface ERROR TeslaEVController:createNodes: Exception Controller start: 'display_name' 2023-06-12 20:08:49,313 Thread-6 udi_interface INFO TeslaEVController:createNodes: Did not obtain data from EV I tried redoing the refresh token but it did not help and I'm wondering if there is an issue because Tesla changed something.

Have you tried pressing the multi function button 4 times to reset the network settings?

Also don't forget to check if the programs are in a folder that might have a condition that is preventing them from running.

Just to wrap this up I found a Z-Wave device that died and was not responding any more. I deleted the device from eisy and have not had any issues since.

Once you pick a lock from your devices it puts it in as a lock on it's own. If yours does not show as a lock in the portal I would open a ticket with UD because I would imagine the device is not being identified properly in IoX or you are picking the wrong node.