palacekeeper

I'll probably experiment with this just because I'm curious :-). by the way, I checked and Alexa routines do allow you to be more granular with regards to setting schedules, where you can do offsets, times of day, etc. Either way, the current way I have it set up with Alexa routine running an EISY scene first, and then running the Govee commands directly afterwards, is working well and seems to be a decent workaround. Sams Club has the Govee bulbs pretty cheap and they seem to be pretty reliable so far, and reasonably well made. I've had Govee temp/humidity sensors for quite a while and they are very reliable.

interesting idea. One advantage to doing it that way (although I'm not sure how it would be done) would be that I think setting schedules in Alexa routines is limited to dusk and dawn - unlike the flexibility in EISY, but I haven't messed with it yet so there may be other ways to tweak the timing in Alexa routines

Does anyone know if the GE Cync bulbs will work with EISY? I didn't see any nodes in the PG3 store for it but I may have overlooked it or it could be under another node name. Thanks

Thanks for the replies and suggestions. It did end up rediscovering the 5 devices after I sent this out, but the next morning they were dead in the water again. It's a shame because the Govee devices work really well within their own app and within Alexa. I may check out Hue or others, but in the meantime, I'm working around it with Alexa by using her Routines option to kick off Scenes in the EISY and then appending the Govee devices, which are supported in Alexa. I suppose I could try to contact the devs in Github - not sure if anyone else has tried that...

I have a few Govee devices (wifi light bulbs and 2 floor lights) and had them working on my EISY for a day or two, but then they stopped working. I even had them working in Scenes. They still work fine using the native Govee app and when using voice commands with Alexa. However, the EISY admin console was no longer showing any values for the 5 devices listed under the controller as of last night - no idea why. 1. I tried rebooting the EISY and also the node for Govee, and the PG3 from the web console. I also did the option to upgrade all packages and rebooted. 2. I tried deleting the controller and devices from EISY, deleting the node from PG3, and adding it all back, including the API key. 3. Once the plugin was reinstalled in the PG3 dashboard, showed connected, and the api key was added back, it did add the Govee node back to EISY and it shows "true". However, none of the 5 devices were rediscovered. 4. I then tried the add all nodes option from the Plugins/Govee menu in the EISY admin console. From what I can tell the node is running fine and communicating with EISY. but the devices are not being detected or added. Initially, they added themselves immediately once I had entered the api key, but not this time. I don't think the api key expires because the Govee node was free to download and install. How can I get troubleshoot to get the 5 devices to show back up and reconfigure them again? Thanks! Jim

Okay so I had some time to try next steps today, but still no luck and I get the same errors. Both the PC and ISY are on the same physical switch and hardwired. I reseated both connections also. Java had lost its memory setting I had previously set, but I was not aware of the -Xms option, so I tried that, assuming that once it allocates the specified amount of memory at startup, it should retain it. I experimented with the amounts, and it seems like above 1200 and it doesn't load properly. It's not a memory limitation on the PC, though, because it has 64GB of memory installed. So, I left it at 1200 with the -Xms option. I backed up the Zwave and ISY again, and retried but got the exact same errors. I checked the error log and debug options but the only debug option is for the subscription and there are no errors logged since 3am this morning. 1. Is there a way to enable debugging or additional error logging that might provide more info about why it is failing to upgrade? 2. The backup (zipped), including zwave, is only 47KB. Does that sound correct? Seems quite small... Thanks!

I finally got some time today to move forward with the ISY994 upgrade from 5.3.0 to 5.3.4. I backed up the Zwave config and ISY config and exported My Programs as suggested. However, when I attempt to do the actual upgrade, I'm running into two errors, shown in the attachments. I re-downloaded the zip file just to make sure that it wasn't damaged in transit but it failed with the same error. Any ideas? Thanks!

Excellent! Thanks for the thorough information. Very helpful and appreciated!

Thanks Geddy! Great point and I definitely overlooked the other release notes. A few quick questions: 1. Can I update directly from 5.3.0 to 5.3.4? 2. Will a full backup restore the 5.3.0 firmware if I need to revert for some reason, or just the configuration? If not, is it possible to downgrade the firmware if needed, although unlikely? thanks!

Thanks for this information, Dennis. My devices are all Z-wave so it looks like it would be about a $450 investment plus some manual tweaking. I'll considerate the EISY for a future project and watch for discounts and sales. Unless this has changed, I've been holding off on upgrading the firmware because from the notes it doesn't look like there would be much of a benefit, and might require a lot of intervention, which is why I was thinking of holding off until I"m ready to mess with the EISY. From the notes on 5.3.4: "This build is just a small update. It contains a fix for unit conversion in program conditions." "Notes - Upgrading to this version may require a lot of manual intervention including verifying scenes, programs and program settings are correct. In some cases it will be easier to rebuild your network."

Hi Dennis, My ISY is on firmware version 5.3.0 and I've attached the About info from the admin console. I'm open to upgrading etc. but I haven't looked into it in a while - just haven't had the time, and the last time I looked it up it sounded like something I didn't want to dive into because I didn't have time for disruption. 99% of the time it's solid. If it wasn't for Java always trying to update and break everything it would be rock solid. I was also considering maybe checking out the EISY and setting that up from scratch. The problem, though, I'm assuming, is that I'd have to remove devices from the ISY and add them gradually into the EISY. Might be worth doing but I haven't researched the benefits I'd get from upgrading. The ISY does pretty much everything I need at the moment, and the Mobile Lync app works fine as well.

Thanks Techman. I was in the process of grabbing some screenshots and it started working again. Earlier the finder wouldn't find the ISY no matter what I tried - even with the latest version of the finder and all of the things I listed in my original post. Just now it worked using the full URL/desc. Odd because that definitely did not work at all earlier! I appreciate the reply, regardless.

My admin console has stopped working again, and this time nothing seems to be bringing it back. I've reviewed similar threads on this forum, tried the troubleshooting steps in the wiki, etc. but none of the suggested steps are working. So far I've tried: 1. Rebooted the PC I'm accessing from. 2. Rebooted the ISY. 3. Verified in the portal the IP address and mac address. Everything works fine in the portal and the mobile app. 4. Power cycled the ISY. 5. Downloaded the newest IoX Finder. 6. Entered the IP address in the finder as http://192.168.0.4/desc 7. Cleared Java cache (all 3 boxes). 8. Added exceptions to Java for the IP address in both http and https, as well as for https://isy.universal-devices.com/, reset security prompts, etc. per the wiki. 9. Tried adding it by using the full console url with /desc, copied from the portal. 10. I am not running Norton or any VPN software. 11. Both my PC and the ISY are definitely on the same network and both have an IP address from the same DHCP server (disabled on the FIOS router, as I'm running DHCP in a Windows Server VM). Any other suggestions on how to regain access to the admin console? Thanks!

never mind. seems to have been related to an outage for the ISY portal. working now.

I am used to Java updates breaking my configuration regularly, but this one appears to be a new issue - at least for me. I'm getting an XML Parse error when attempting to start up the admin console from the shortcut I always use. I have not made any changes. Java hasn't been updated since November and Temurin since about 3 weeks ago. I can't get into the ISY portal either. I saw in other threads where maybe my subscription lapsed, but I can't even log in to the portal to check the status. I tried downloading a new start file and pasting the full URL including the desc at the end, but it just says "not found". I tried power cycling the ISY and still get the same results. Any suggestions on what steps I can run through to regain access? Thanks!