bmercier

In the menu, click "Home". You will see the gear icon on the right.

Does anyone has missing statuses fairly consistently? I'm referring to status either in the Nodes page, or when using the Admin Console to port 80 or 443 (eisy-ui)

The next eisy-ui release will show scenes & folders in the Nodes page. Programs with a scene will show the scene name as one would expect. The ability to edit or view the content of a scene will be implemented later though.

Does everything work in the Admin Console? I'm thinking that maybe the plugin has been removed or is not running? If everything works in AC, please open a ticket so we can investigate further with you.

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.