Michel Kohanim

@gschoffstall, 1. You can return the ZMatter USB dongle within 30 days, so you are not stuck with it. 2. You can install plugins/node servers (Hue) and they show up as nodes just like INSTEON devices. Here are the instructions: - Go to PG3 Dashboard (Admin Console | Node Servers | PG3 Dashboard) - Follow the instructions here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#NodeServer_Store_Menu. In short, go to the store, find the Hue plugin, click on the Install button, and the follow the instructions on the screen to link it to your Hue Hub. I am assuming that you already know how 994 programming works. But, in case you don't and want to start from scratch, you need to start from our Wiki. Or you can read the Cookbook. We would be delighted to answer specific questions via Tickets, alas we do not have the resources for soup-to-nuts education. Apologies. With kind regards, Michel

Which? With kind regards, Michel

@PGannon, As I mentioned in the ticket, the first thing you should try is to move the PLM to a different outlet. With kind regards, Michel

@gschoffstall, Perhaps this will help: https://docs.isy.io | click on Some Definitions. With kind regards, Michel

@larryllix, The reason the links goes nowhere is because you are on a firmware from more than a 1 year ago. Most probably, you are still on PG3 (or PG2) neither of which are maintained. We are on PG3x with major improvements. Regarding NRs, the whole purpose of plugins/node servers is to make NRs less relevant. What exactly do you use these NRs for? If you wish, I can do a remote session and see whether it's possible to upgrade your OS and everything else. But, I definitely don't want to force you to do anything you don't want to. With kind regards, Michel

@larryllix, Do you know what version OS you have (https://polisy.local:8443/desc). There are many bug fixes and enhancements especially for Z-Wave/Zigbee and node server communications + stability. With kind regards, Michel

Hello everyone, In most cases, the issue is that eisy cannot get out to the Internet. If you are on the latest 5.7.0_5, then there's a 99.9% chance that the issue is on the router/ISP side of things mostly DNS name resolution. Please check your error log. And as always, we'd be happy to take a look and give you recommendations via tickets. With kind regards, Michel

Hello everyone, 5.7.0_5 was released yesterday, and thanks to all those who helped us with debugging, it definitely does fix the disabled programs issue. With kind regards, Michel

All, the site works including tickets. What does not work is the Account page which we are trying to fix. With kind regards, Michel

@brians, Apparently the fix didn't fix all the issues regarding disabled programs. This said, we added a lot of debugging, so if you have this issue, please submit a ticket with your error log. @oskrypuch, Did you submit a ticket? With kind regards, Michel

@gwk, are you certain you are on the right website? With kind regards, Michel

@Hoosier Daddy, Apologies, 3.2.9 had nothing to do with disabled programs. 5.7.0_4 was released just a few minutes ago. It should fix the disabled program issue and, if not, it would provide us enough debugging info to figure out why it was not fixed. With kind regards, Michel

I use my eisy for development including the compilation of the whole OS, run eclipse, and chrome, and vscode ... although hot, it never reaches the point of not being able to touch it. As long as the top is ventilated, I wouldn't worry about it. With kind regards, Michel

@hart2hart, the SSDP Client issue is on the client side of UPnP discovery (Admin Console). If you are on Linux of FreeBSD, it's normal. If you are on Windows, then something else is using that port. In short, it has nothing to do with eisy. @kzboray, so very sorry for the trouble. This is fixed in our next release (today). This said, simply restarting IoX from the Admin Console will fix this issue so that you don't have to re-enable all programs manually. With kind regards, Michel

Hi Sparks, Almost uncomfortable might be normal depending on what the processes are doing. When it becomes really uncomfortable, then you do need to worry. With kind regards, Michel

As @Geddy mentioned, this is normal. The output of the URL is correct. So, this is definitely Java installation issue. Please submit a ticket. With kind regards, Michel

@Envirogreen, seems to be your computer/networking and/or Java related. Please try: https://polisy.local:8443/desc and let me know what you get. With kind regards, Michel

@Envirogreen, What error are you getting when you click on Admin Console | Cloud? With kind regards, Michel

@oskrypuch, Please submit a ticket. We'll figure it out. With kind regards, Michel

@jpoje, Perhaps this will help: https://www.universal-devices.com/eisyir-flirc/. With kind regards, Michel

All, I think we may have found the issue and will have a fix by no later than Monday. With kind regards, Michel

No, it's $39 for two years. @CBPetrovic, If you don't use ISY Portal for remote access, then you don't need it. Local programming will continue to work. With kind regards, Michel

Hi all, Disabled programs are most probably due to the bug in 5.7.0_0. We have not been able to reproduce but @brians might be right that it's related to the upgrade process because it has changed: - Previously, when we upgraded IoX (isy service), the service was restarted immediately. This basically meant that we could not send status updates back to the Admin Console. - In the current process, when IoX (isy service) is upgraded, isy service continues running the previous version till the next reboot. The current hypothesis is that the file that governs enable/disable for programs somehow gets corrupted during the upgrade of IoX (isy service). This issue is the highest priority task on our list. Apologies for the inconvenience. With kind regards, Michel

@Lore, You need to install Dev Packages for Vue. Admin Console | Configuration tab | Install Dev Packages button. With kind regards, Michel

@CoolToys, It's our job! With kind regards, Michel