giomania

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

I mentioned this could be an issue earlier, but in case it was missed, let me ask a direct question: Is there any reason why a reserved IP address that is outside the DHCP range will not connect? Like because there is probably no DNS defined because it is outside the DHCP range set in the router? Thanks. Mark

Yeah, the clients still won't connect.

Yes, the external IP address is 10.10.2.20. I just had that in there earlier, and the result was the same. I will add it again, and restart PG3x, but I don't think that will fix the issue.

Here is the MQTT config: