bmercier

Both the eisy and/or Java app can use wifi or be wired as long as they are on the same network.

Yes, you still need the Java app to manage OpenADR.

You might have rebooted too early. The upgrade to 6.x takes a LOT of time. If the system, is still responsive, try to run upgrade packages, one more time, and give it 2+ hours (unless it tells you it's completed and you can reboot).

Thanks for the feedback & suggestions. I would see this as something separate from backup. Something like "Export configuration". The backup is meant to be restored, either on the same unit or a different unit. It is not meant to be opened for tinkering or troubleshoothing. The export on the other hand could be a text reference to a few things like you suggested when everything goes south and you can't or don't want to restore.

As others have pointed out, a scene or program is the way to go. If you want a button in eisy-ui, you can install the Virtual node plugin that will create a node that is mapped to a variable, and you can have that variable trigger your scene or program. Then in eisy-ui, you can create a tile and expose a button to turn off that node. The missing piece of the equation is that you need to ensure that the variable is set to the "on" state whenever an All on is detected.

I'm not sure the suggested file name would be popular. I believe it is better as it is. It identifies what the file is about, and has a date in a format that allows sorting by date.

Hi Geddy, Yes, the Upgrade To would have been updated eventually. The Upgrade To shows the equivalent of "pkg search". Let me share some of the internals: When you updated manually, you would do a sudo pkg update, then sudo pkg upgrade. The "update" part refreshes a local database of pkg available. The "Upgrade To" shows that. It won't do a "pkg update" by itselk. This is done on schedule, I believe daily. So you would have seen it eventually. The reboot error you saw has been corrected in 0.9.0. So on the next update, it should not show and an error anymore. After the reboot, the browser showed a 404 because the UI url for the upgrade has changed. The upgrade used to be under Settings, and it is now under system. That should not happen anymore. Benoit

It's best to update from eisy-ui if you are upgrading from a recent enough version.

eisy-ui 0.9.0 is now available. The main feature is related to backup and recovery. The backup includes IoX, ZWave, PG3x and eisy-ui settings. The restore allows to restore everything in one shot, or do a selective restore. For those migrating, you can restore an IoX and/or a PG3x backup. It will detect and restore accordingly.

Re-authorizing is exactly the same thing as Authorizing. It may take a few seconds to redirect to the Ring Authorization page, so be patient when you click. You may want to check the PG3 log for errors when you click. The error you see in the plugin log is not related. It just means that the node exists in IoX but not in PG3. IoX is querying the node, but the plugin does not know about it. I'm not sure what led to the need to re-authorize, but that may recreate that node.

Try it on my.isy.io. They are the same.

The reboot API has changed named between version. So it looks like the eisy-ui server got updated, and the UI was out of sync. A refresh of the page would have fixed it. The black screen issue following login will be fixed in the next release.

There are no cases where updates would be done automatically. Whay may have happened is an upgrade packages being done, either using the Admin Console, UD Mobile or eisy-ui, with no reboot. In that case, only at the next reboot would version updates. That may look as an auto-update. @Geddy, The solution to your struggles is eisy-ui. If an update is available, you get a notification at the top right that tells you an update is available. You can look at the releases notes BEFORE upgrading within eisy-ui, on the upgrade packages page. The upgrade itself is more convenient as it clearly tells you what's happening during the upgrade.

The Alexa smart home skill API is the same for Alexa vs Alexa+. Amazon has not published anything that is specific to Alexa+ as far as skills are concerned. The skill should be working with both. If the issue is only with scenes, then I would suggest to not use scenes. If you have ISY scenes, you can make them appear on Alexa as lights instead.

One thing for sure is that you will need a backup. So if you don't have a recent backup, you will need to login to the Admin Console to take one. If the unit is functional, I'm pretty sure we can help you get the Admin Console to work again. To migrate the spokens, that can be done on my.isy.io.