Guy Lavoie

That's a good question. I'll probably be redoing some of my tests with 6.1.1

What version did you upgrade from?

Dying batteries in motion sensors can also be a cause of unexplained events.

Have you verified that the file is actually missing? You would need to access your controller with ssh and look for the file. The full path is /var/isy/FILES/CONF/2B9FCE.REC. If it's missing, you might try and see if an older backup has it, and restore just that file. IoX backups are compressed folders, that you can just browse through on a windows PC. Find the backup you want to check (they're helpfully named by date), click on the folder, and follow the path. First you'll see a folder with your UUID, then FILES, then CONF, and look for the specific file. Look for the most recent backup that has that file. Then try and extract it and copying it back to the eisy. Several steps are involved: create a temporary folder on your pc and extract the backup to it. For example, create a folder such as c:\tmp2 and then from the file browser that you're using to view through the compressed backup, click on "extract all" at the top and restore to c:\tmp2. Now you'll be able open a DOS command prompt and browse to the folder where the file is. use the scp command to copy the file to the eisy. To avoid permission issues, first restore it to admin's home directory (/home/admin), like this: scp c:\tmp2\FILES\CONF\2B9FCE.REC admin@eisy.local:/home/admin/2B9FCE.REC You'll be prompted for the admin password. ssh into your eisy and verify that the file is there. Then use: sudo cp 2B9FCE.REC /var/isy/FILES/CONF/2B9FCE.REC to copy it to the needed directory. See if that fixes your missing config file issue. If you're confident that the version of that device is up to date in the restored file, try restoring the device.

In fact that's what I also did, get Yolink temperature sensors.

Once every 20 years isn't so bad 😃 If you haven't modified your programs recently, then it can be just a freak occurrence. There are programming tips you can use to minimize the possibility of this happening, such as avoid issuing any new commands right after sending a scene command.

I'm not sure what it's called in Alexa. Maybe it's a routine. But I'd create an Alexa routine that would trigger on a variable being equal to each value. So if variable = 75 then say "the temperature is 75 degrees". One routine per temperature.

I looked for a way of doing this a while back and making an announcement for each temperature was the only workaround I had found. I did ask the author of the Virtual plugin to see if he could add a virtual temperature device (for Alexa), but that doesn't look like it might happen.

Yes, though a lot of the plugin developer information went missing a while back. I'll poke around.

How do we do that? Command line? And what is "install time"...when the upgrade is performed? Learning and taking notes here 🙂

Well that's it, I didn't want to bet my life either! Lol. I figured the node names would be the same since the slot number is part of the name, but the recreated names might end up at a different pointer in a device table. So I played it safe and replaced the plugin like an insteon device, by creating the new one and using find/replace.

Ok thanks, I just did that, which solved the problem. But...I could only reinstall it as a new plugin, in a new slot. I didn't find a way to update the existing one. This means that I lost the existing references in programs. So I installed it in a new slot, leaving the old non-working plugin in place until I could find and replace the program references to the nodes. Then I deleted the old one. That's not cool...there has to be a better way?

Very likely. I updated 3 Polisys this way and didn't need to set the repository on any of them. Not sure why it happens for some cases.

That might be normal, I saw something similar during the command line update, probably because the Polisy cannot be fully upgraded to freebsd 14.4. I'd reboot it and then check out that everything is ok.

I am running into an issue with a plugin after the 6.1.1 update. This is a simple plugin of my own creation (doesn't connect to anything outside). It gives me timers that increment once per second, referenced like variables in programs. It is run in developer mode. Now it shows as disconnected, and it keeps giving the following error: interface:_disconnect: MQTT: Reconnect successful2026-08-22 15:43:32.937 Interface udi_interface.interface INFO interface:_disconnect: MQTT Unexpected disconnection. Reason code: Unspecified error. Sent by server: False. Retry in 10 seconds. It's been running fine since I created it over a year ago, even after updates to 6.0.5. But 6.1.1 is giving me this. Restarting the plugin doesn't work. Any hints? Edit: my other development plugin is giving the same error. Looks like something need to be refreshed. Ideas?

You power cycled the eisy after plugging in the new PLM, right?

Until you get the new cable, try finding a position for the old one that works, and don't sneeze on it! 😆

I'm not sure how that email was structured but reflashing the eisy is not part of the upgrade process. It could be a last resort if your freebsd version is too old or crashed. Normally you just do the required backups and then click on "Update Packages" as indicated in the release announcement.

You can't easily swap the PLM without all the implications of a full PLM restore and following the procedure. I'd start by just putting things physically back in place, try the reboot, and test things, first looking out for that memory error.

I'd start with a reboot, that includes disconnecting the power for 30 seconds.

Did you reboot as prompted?

That's up to you. If your whole setup is stable and you're not looking to expand it, you might be fine as-is. Upgrades generally introduce new features, fixes, etc. Support for the Polisy is officially ended, but for the time being is still updatable to the current iox versions, which could come in handy should you need to replace it with a eisy.

Yes, heed the warning about the freebsd version. This upgrade method was suggested by Michel at UDI. I've personally upgraded all three of my Polisys successfully this way. Page 4 on the following thread has discussion, including instructions on enabling the repositories if needed.

That's for the Polisy only.

Have you just done a version upgrade by any chance? It might need a reboot, with a good 30 seconds with the power removed.