Guy Lavoie

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.

The format is: http://<ipaddress>:8443/desc

No, you should be able to use the old isy username and password, as long as they're replicated in the new eisy. If you log into admin console using that name and password, does it work? This has to be the url in ISY Finder with port 8443 in it. It prompts you for the eisy password:

Well you can't uncheck the DHCP setting. You need to have it use DHCP.

Maybe try recreating the scene manually? If the new one works, then delete the old, corrupted one.

The "top" command gives a good overall portrait of system resource usage. As Michel hinted at, most of the memory is appropriated for possible use, but not necessarily active at any given moment. Here are two screens showing the output of the top command. The first one is my eisy, running dozens of programs, many plugins (notice the several "python3.11" processes). The second one is one is my least used test Polisys: Among the "Mem:" line is a value called "Laundry" (who said programmers don't have a sense of humor?). It's memory that's been used and freed up by a process, available for acquisition for a new task if needed. So the actual, unused "Free" value stays small, which is what what makes the percentage of memory "in use" seem high in eisy-ui.

One handy tool is the Find/Replace tool in programs (right click on "My Programs"). Look for the button name throughout programs, and assign the new one by clicking on the Replace button. There is no similar function in scenes, but if you click on the keypad button you want reassign in your device list, you'll see the scenes it is used in, under the Membership list on the far right. Then go to those scenes and make the changes.

Have a look here, on the 4th page of the thread. there is a command to do first:

Does it appear on your network? Can you ping it? You'll probably need to open a ticket.

Have you tried a full reboot (unplug the power)?

That's odd. Were you previously updated to 6.0.5? Try this: try the usual upgrade procedure first within Admin Console (Upgrade Packages), this might enable something. The upgrade itself should fail, as per the log file will show you. Then try the upgrade again with the command line method. Remember the release announcement warning: If your FreeBSD OS is below 13.2p11 (check via https://eisy.local:8443/WEB/sysconfig.txt), do not attempt this upgrade; it will brick your system.

Well those devices have only been listed as being supported by the new release 6.1.1 for less than 48 hours, so unless someone was able to quickly buy one at a corner store, I don't think anyone here will have experience with them yet. Since you want both zwave and zigbee, the dual protocol dongle sounds like the most attractive option. If you already have one of the Zooz dongles (700 or 800) then you might consider adding the Sonoff zigbee dongle. No instructions have been posted as to if it's possible to migrate existing devices from the Zooz or ZMatter dongles to one of the new ones.