Techman

When you get it resolved can you post the fix

Probably best to submit a suppport ticket. It could be a hardware or a firmware issue. https://www.universal-devices.com/my-tickets

It's possible the the power surge may have damaged the Zwave board Try HEALING NETWORK If you have a recent zwave backup you can try doing a Zwave restore Do you have a spare Zwave device you can install to see if the board is still working?

Try removing power from the EISY for about 30 seconds Make sure that Zwave support is set to on under the configuration tab

You can't have an IF statement in the THEN or ELSE statement You can split it up into two programs

You're setting the variable after you send your message. Move the variable line up before sending the notification. What are the contents of "Z-wave T Hot". You should be sending the "$i.Greenhouse_T" which is your temperature

The EISY/POLISY can only send email notifications. The carriers no longer support email to text notifications Post a copy of your program

Try rebooting your controller. 16.3 works flawlessly on Android. Also try clearing the cache on UDM

I use the Zooz ZAC38 which also has a built-in battery. The EISY and the EISY-UI doesn't not show "AC Mains Reconnected", but the work around is if your program doesn't show the AC Mains Disconnnected then assume you have a power restored.

You can view the EISY config file from here: https://eisy.local:8443/WEB/sysconfig.txt click on ADVANCED, CONTINUE to eisy.local (unsafe)

To add local login to the admin console click on ADD, then add the following URL https://eisy.local:8443/desc and then click on SAVE.

I'm not aware of a way to view the CPU or processes. To view running programs click on PROGRAMS | SUMMARY and look at the ACTIVITY column I would first clean the SD ard

The SD cards have a tendency to fail after time, howerver you can try removing power from the ISY, then remove the SD card and clean its contacts with a soft eraser. The contacts are prone to oxidation and cleaning them restores connectivity. Also look for programs that may be running in a loop

@johnstonf What type of devices are in Motion3 and Vacuum program with the out of memory? Can you post a copy of that program. You should correct all the errors in the 994 before migrating

I'm a Windows user, in windows you can hold down the control key when closing the window to set the size, not sure about the MAC As @Geddy suggested you should try to locate the .STATE files and delete them. The will rebuild the next time you open the launcher

Are you on Windows or MAC

It's best to open a support ticket My Tickets - Universal Devices - The Most Powerful Automation, Energy Management, and IoT Platform

Under the configuration tab, is the zwave box set to ON

It's best to send an email with your question to: sales@universal-devices.com

Even though the Zwave/Matter board is Zwave LR certified it appears that the current software doesn't support LR. I have an open ticket and should know more next week and will post the results

It's possible that your Insteon mesh network is marginal, or that you have noise on your powerline that's interfering with the Insteon signals . How many dual band devices do you have in your system. If everything was working prior to moving over to the eisy try doing a restore device on the insteon devices that aren't working properly.

If the PLM was linked to another Hub then you will might have to factory reset it as the PLM contains the link tables of the previous hub and may not be compatible with the eisy Do you currently have a working, and populated eisy? The replace PLM instructions are attached. Replace PLM Procedure (EISY or POLISY).pdf

@NewB Scenes reside in the PLM and the devices. You could disconnect the ISY and the scenes will still work. It's possible that when you initially restored the new PLM the scene's links got corrupted. Take a scene that isn't working and do a restore device for each device in that scene. If that corrects the problem then you'll have to do it for each scene that isn't working correctly. If that doesn't correct the problem then you'll have to rebuild the scene

@NewB Assuming you have the ISY994, here is the replace PLM procedure Replace PLM (ISY994).pdf

@Javi Just updated to UDM to 1.5.10 on android. I'm now getting the following error every time I synchronize. This wasn't the case with the previous version>