giomania

Is it possible to install eisy-ui on an NVME SSD while maintaining the Home Assistant VM I created on the NVME SSD? I was going to migrate IoX to the NVME SSD in early 2024, but users were having issues with implementing the scripts to move the OS, so I never took action. Now I remembered about this, and am wondering if the scripts are now built into the latest version of IoX or in eisy-ui? I am looking for the most stable path to upgrade to eisy-ui, because everything is working now, but would not mind the extra performance from moving the OS to the NVME SSD. Thank you. Mark

Where are the instructions that mention any actions to take post-upgrade. Here is the official upgrade post I saw. Instructions: Backup your Z-Wave if any (Z-Wave | Backup) Backup your IoX (File | Backup IoX) Backup your PG3 Click on Upgrade Packages in Admin Console | Configuration tab. Do NOT use ssh as it will brick your system.

I wasn’t going to upgrade, as I had posted my reservations earlier, but when I came home from work on Friday, my wife had upgraded. So far everything‘s working, but I mostly have Insteon devices controlling lights and a few smart plugs from Amazon and Athom (MQTT via PG3). Mark Sent from my iPhone using Tapatalk Pro

Interesting. I was thinking about upgrading but might not be worth it due to slower response times. While this response time might improve I was also thinking they will probably charge for the service in the future, and reverting to the OG service could be an issue. If it ain’t broke… Mark Sent from my iPhone using Tapatalk Pro

Same here. Sent from my iPhone using Tapatalk Pro

Same for me. Alexa said the skill was not enabled. Sent from my iPhone using Tapatalk Pro

There are separate instructions for installing and initializing the SSD and for installing for HA in a VM, so it seems like it would be the same script to install HA, but we would need an expert to chime in. Mark

I saw this blog post about configuring the eisy to boot from an NVMe SSD, and it clearly states the process will wipe out any VMs installed. I just installed Home Assistant a few weeks ago on the NVMe SSD, and don't really want to lose it. That said, I would like to use the SSD for the extra performance benefits noted in the blog post. Will the migration without the loss of installed VMs be supported in the future? Thank you. https://developer.isy.io/blog/Supercharged

I am still stuck on 5.6.2 and unable to upgrade. Were we expecting this release to fix this type of issue?

I also cannot update to 5.6.3, nor PG3x v3.1.36 before that. I have been trying with PG3x v3.1.36 since it was released mid-july. Multiple package installations and reboots. Hopefully this is part of the issue Michel discovered. Mark

Update on what I learned from UDI support. MQTT is installed, however PG3 and PG3x make use of a private MQTT broker for internal communication between the various components, and that package is specifically configured to support PG3x. They advised I should just use another mqtt broker on another device on my network, so I used a broker on my Raspberry Pi that is for a different project, but is now serving two purposes. I hope this helps.

So the commands no longer work to install mosquitto I think they have locked down the eisy more. I am going to start a ticket.

Oh darn. I guess I forgot that I probably did that back in the day. Let me do this and report back. Thank you.

I use 1884 because I have another MQTT broker on my HTPC that only controls the fans in my theater for 4D Wind tracks added to movies. It is long story, lol

The MQTT node server is the broker. Those logs only show polling, unless I restart the node server. I restarted it and then downloaded the log, attached. I don't notice anything out of the ordinary. MQTT_4-6-2023_22820-PM.zip