7 hours ago, Javi said:

See known issues: https://forum.universal-devices.com/topic/46914-os-144-release-is-now-available/#findComment-406192

Thanks, Javi. Is I the fix for this coming relatively soon? Not rushing.

30 minutes ago, hart2hart said:

Thanks, Javi. Is I the fix for this coming relatively soon? Not rushing.

The logs are informational only, no fix required.

iOS app has been updated to ignore this log. Pushed an update to app store, however Apple's approval can be a few days.

6 hours ago, Javi said:

In Notification > Email, Wake On Lan names. We should have beta release with these bug fixed by end of day.

OK, did the update and programs populated!

On another note, Still cannot find 'notifications > email......' in admin console, Looked all over. Just interested now. Thanks!

John

1 hour ago, JSchumann said:

OK, did the update and programs populated!

On another note, Still cannot find 'notifications > email......' in admin console, Looked all over. Just interested now. Thanks!

John

Customizations > Emails/Notifications

My UD Mobile and AC are both reporting a new version as of this morning (8/22). I upgraded a few days ago.

@Javi Is this for the fixes you mentioned above?

~jim

I cannot get rid of this notification

I have clicked the upgrade packages multiple times and it says successful and then the next time I log in this warning comes up again.

4 minutes ago, epete said:

I cannot get rid of this notification

I have clicked the upgrade packages multiple times and it says successful and then the next time I log in this warning comes up again.

That's what I saw, but I didn't hit the go button...

15 hours ago, Michel Kohanim said:

Please do

sudo repo.util and switch to staging.

With kind regards,

Michel

3 minutes ago, epete said:

I cannot get rid of this notification

I have clicked the upgrade packages multiple times and it says successful and then the next time I log in this warning comes up again.

Did you reboot as prompted?

3 hours ago, JimTurner said:

My UD Mobile and AC are both reporting a new version as of this morning (8/22). I upgraded a few days ago.

@Javi Is this for the fixes you mentioned above?

~jim

Yes. Also upgrades can (and should) be done from eisy-ui > Menu > System > System Upgrade. This shows available version and current versions + what is being upgraded (e.g. eisy-ui only)

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 successful

2026-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?

Edited Saturday at 09:01 PM3 days by Guy Lavoie

7 hours ago, Guy Lavoie said:

Did you reboot as prompted?

Guy - I think this may have been related to my bad USB to RJ45 eISY to PLM cable from my other thread that you also posted in. After swapping PLMs to USB PLM this had gone away.

8 hours ago, Guy Lavoie said:

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?

@Guy Lavoie , if it's a local only plugin, you need to reinstall it. The migration process upgrades the certificates for production plugins installed in /var/polyglot/pg3 but it does nothing for local ones.

With kind regards,
Michel

, if it's a local only plugin, you need to reinstall it.

@Michel Kohanim ,

Just to be clear, local only, with no beta or production with same id, or all local?

Thx

@sjenkins

Local means that it's neither in beta nor production.

With kind regards,

Michel

15 hours ago, Michel Kohanim said:

@Guy Lavoie , if it's a local only plugin, you need to reinstall it. The migration process upgrades the certificates for production plugins installed in /var/polyglot/pg3 but it does nothing for local ones.

With kind regards,
Michel

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?

7 hours ago, Guy Lavoie said:

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?

You can only do this by deleting the old plugin first then the slot opens to re-install. I won't bet my life on this next statement, but, I am pretty sure that if you delete a plugin and then re-install the same plugin in the same slot, any programs that reference any of those nodes will re-populate. When you install the plugin back in, all of the nodes should get the exact same id's and all the programs should put them back in. What won't re-populate is any customization you did on the main page of the admin console. In other words, any folders you put stuff in or any re-naming you did.

I would confirm with @Michel Kohanim on this.

EDIT: You might also look at the new eisy-ui beta plugin section. It might make things a bit more stream lined for you.

Edited Monday at 03:08 AM2 days by apostolakisl

10 hours ago, apostolakisl said:

I won't bet my life on this next statement, but, I am pretty sure that if you delete a plugin and then re-install the same plugin in the same slot, any programs that reference any of those nodes will re-populate.

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.

My upgrades went well. On one eISY I had to reinstall all my plugins, the other one was fine (they are the same plugins). Noticed on one eISY (the one I did not have to reinstall the plugins on) is showing the wrong time zone (2 hours ahead) in program last run/next run and variable last updated views. The PG Log (which I am using because I can see it in real time on the site) is showing local time in the one working properly but 2 hours BEHIND in the one with the TZ issues. However on both machines in the AC the time and time zone is correct.

Hello everyone,

You should not have to uninstall and reinstall "local" plugins. What you need to do is to remove the cert and key files so that they can be regenerated at install time.

With kind regarsds,
Michel

21 minutes ago, Michel Kohanim said:

Hello everyone,

You should not have to uninstall and reinstall "local" plugins. What you need to do is to remove the cert and key files so that they can be regenerated at install time.

With kind regarsds,
Michel

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

2 minutes ago, Guy Lavoie said:

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

Yes, because you local plugins are "developer" made/deployed, so I am assuming you already know how to ssh and do things on the command line.

With kind regards,
Michel

27 minutes ago, Michel Kohanim said:

Yes, because you local plugins are "developer" made/deployed, so I am assuming you already know how to ssh and do things on the command line.

With kind regards,
Michel

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

I was particularly nervous about this upgrade as I've made a lot of changes under the covers that I was afraid might get lost.

I am running on an nvme drive per a blog post from long ago. I am also running Home Assistant in a bhyve VM. I'm running netbird in the HA VM as well as on FreeBSD.

I'm pleased to say the only glitch I've seen so far was the EISY binding to eisy-2.local instead of eisy.local. This broke my HA integration until I reset it. Things look fine now.

I'm glad to finally see the web UI gain access to programs and better access to devices/scenes. I do have some trouble reading the screen due to recent eye surgery. I can magnify but many of the colors are too dim on my display to be read easily.

Usually as soon as I hear of an upgrade and I jump in without reading the forums or making a backup,,,,, That has caused "issues" in the past.

This time I decided to wait a while before upgrading AND read through this thread. I created back ups and then started the upgrade.

I never received definitive feedback that the upgrade completed, however I did get prompted for my user name & password several times during the process. Eventually the Admin console went through the startup process but got stuck at "Creating Widgets". I left it alone but after 40 minutes, I decided it was stuck. I couldn't cancel out and I couldn't close Admin console. I disconnected the power cord from the Eisy and let it be for a few minutes. I had to kill Admin Console via Task Manager.

Power up and boot seemed to take longer the first time, but once loaded, all my devices showed up and worked properly. No issues with plug-ins and my programs are functioning.

I have a first gen EISY with Zmatter dongle, and Insteon PLM. I run Insteon, Zwave, Zigbee and matter devices. I have Wemo & Kasa plugins with associated devices.

The only other sort of issue after the upgrade was Apple Home could no longer communicate with the Eisy. I removed the Eisy from Home and tried to re-add. Initially, Home would not re-add the Eisy. I waited about 30 minutes and tried again. Home accepted Eisy with no further issues and is working properly.

Kudos to the UD developers and everyone else involved!

One other oddity I have noticed is trying to view the error log from the AC. It seemingly hangs and never returns (log file too big??).

I can download the error log from the eisy.local and it has nearly 200k lines in it. I am assuming this is the same log????

(Trying to chase down an issue unrelated to this thread, but the error log not loading started with this upgrade...)

~jim