bloodyd

I had a similar issue when I did my upgrade from 994i to EISY. Are you using a new PLM in your system? I used a new USB PLM in my scenario and physically flipping any switches or lights on the wall units would not update the IoX status in the admin console. My fix was creating a new scene and adding the troubled device as a controller to that scene. I then right click on the device on the admin console and restore the device. Once EISY finish writing to the device, I delete the scene. This restored functionality to the device. Repeat this for all your devices that are having issues. The steps listed above did not worked for the IOlinc garage controller though. I had to remove the device from the system and re-add it for it to work correctly.

Thanks apnar. I don't want to trouble you for that. My system is running fine now and I rather not mess with it for now. Appreciate the offer though!

My home assistant is running fine after restoring from a backup. I didn't encountered any issues at all. I haven't tried running the script again, not knowing what will happen. I'm hoping there is a way to put the OS back in the emmc. I don't want to be screwed if the NVMe ever fails.

If I run the script fl.ops setup.nvme.boot again after choosing the no mirror option, will it revert back to internal emmc?

That's a pretty good idea. I've never considered drilling a hole in the back cover and use a straight cable. Thanks!

Anybody know where I can get some 10 feet cables for the Motion Sensor II? The ones sold on Smarthome.com is only 6 feet and I can't for the life of me find anything longer that would work. I know there are extension cables out there, but I'd rather not use them (for aesthetic reasons).