mmb

Well AI engines have pretty much sucked up all knowledge on the internet, so my goto when I have a question as you suggested is just head to Gemini or AGY. For me what will be nice is eISY’s plug-in to dig into logs and coding, and suggest/make changes.

Very interesting Michel, can the eISY AI do a review of all my Programs to determine if there are any problems that need to be addressed? Like AGY AI?

I gave up on them about 15 yrs ago. Battery devices are too flakey. Almost 20 yrs - I had a good run.

@lilyoyo @Guy Lavoie Thanks they are older but motion sensors. No program modifications. Also interesting, the logs shows scene IDs instead of scene names around the time of the event. I checked the logs again later this morning and they're gone. Hard rebooting everything.

I experienced a first time ever event in the almost 20 yrs of ISY/Polisy/EISY ownership All my Insteon lights randomly turned on at 3:00 am this morning. The only program scheduled to run is the usual query to devices at 3:00 am. The query confirmed lights were on in the logs. I'm on the latest up to date EISY firmware, my PLM is relatively new and line noise has never been an issue. Anyone else experience this weirdness? Edit: My wife says she had to get up at 11:30pm and turn off all the light.There is a possibility that the lights were randomly turned on earlier and the query just reported the fact the lights were on.

Thanks!

Hi @Javi , I see these errors on sync after installing the major update today. They don’t seem to be causing any functionality issues. Can you help me understand what they are? Thanks!

Upgrade went well, no issues.

Did you upgrade via the admin console or from the EISYUI? My EISYUI says I'm up to date for some reason. Thanks!

It's been a while, is there an update? Not showing it's available on my EISY UI.

The only thing I would consider unusual is my use of REST. I retrieve temp data from an external website and set variables to trigger programs (switches). I also trigger lights based on motion on BlueIris NVR. These were never a problem on the ISY.

I experienced a lockup as well, first time ever since migrating away from my ISY. It was such an unusual event that I felt Michel should have a look. My programs are pretty straight forward as well. I have mostly Insteon switches and a few of zigbee devices which were added since the migration. Anyway Michel blamed it on a loop as well.

I use EISY for all my Insteon lighting, nothing comes close for functionality. I have a couple of Zooz switches on the EISY as well. However, I use HA for all my utility needs like zigbee sensors and smart plugs. I find EISY support very limited and/or clunky compared to HA for these devices.

Same?

Not sure about Apple devices but UDI has said in the past the target for the webui is end of year 2026. So maybe they had this in mind with their timeline. I actually mentioned to Michel a couple of years ago that they should develop a webui to gain better adoption of their devices and plus java always seems to be a problem area for new users. I was told, UDI is a small company etc.

Good plan, thanks!

Good idea, I'll watch it. Currently I'm at 135. Thanks!

Thanks, I'm still not sure, it seems like OS/IOX doesn't have an open socket to take the admin console requests for a Program Save, for example. Makes sense to me why would a reboot clear up the problem for another month. I don't have a huge number of Programs but I do have external programs that use REST to do regular update on variables in the EISY. And PG3 has an DSC Alarm node that updates the EISY. Nothing crazy in my mind. Maybe I'm missing something.

Thanks, it happens on a Save function like creating a Program. I saw the thread. I seem to remember setting the -Xmx512m to 1024 previously years ago but the setting is missing. I'll try that again. Firmware is up to date. 6.05. I'll see how it goes and submit a ticket if it happens again.

Does anyone know how to get rid of these socket timeouts? I do know what a socket is but not sure how to address them on the eisy. They popup about once a month and total bork a program save and other functions. Thanks!

Curious @Michel Kohanim what is causing the ISY Default smtp failures on the ISY? Even when firmware is updated. It seems so straight forward.

My experience as well, EISY and Polisy work fine with Gmail but the ISY doesn't work at all. The ISY Default smtp setting does work fine for me, first try actually.

Very smooth for me, surprisingly given everything that was touched.

My ISY has been on Gmail since 2012/2013, likewise never a problem,. Back in the days of LeeG etc.

Nothing changes for your Gmail account. The change affects use of their smtp servers that you use to move email. It's well known that certain people abuse smtp to send spam and other garbage. Stronger authentication tries to ensure that the right people are using their smtp servers. ISY supports Basic authentication for their smtp servers, Google no longer supports Basic authentication for reason describe above. They say you have to use their procedure to generate an approved strong password (16 character) if you want to continue to use Basic authentication.. BI now supports Oauth which allows you to use your usual Google username and password for authentication to their smtp servers.