auger66

I assume this topic is for eISY and ver 3.1.25. Upgrade went fine, except the restart after upgrade didn't work. I couldn't open the Polyglot page. I tried three restarts and then repowered the eISY. That worked. I haven't had to repower in the past few updates, just restart.

Making Hue scenes, rather than programs, work well for me.

Definitely. I never understood why Smarthome treated UDI like they did many years ago, especially since UDI was the reason many of us used Insteon at all.

Mea culpa. I missed that part. Good to know Insteon is more helpful than in the past. And to answer your question, no. I would rather support come out as it is able to like it is now; even though, I have no near-time use for i3 products. I'm just glad UD support for Insteon is continuing. Especially considering past UDI comments saying they would never go through that again with Insteon. Clearly now, I see things have changed for the better.

I'm glad to see UD working on this, too. But Insteon--meet the new boss, same as the old boss. What is initial support? Although support is almost complete, but due to lack of documentation, the following is not yet working:

After a rough start, eisy is mostly functioning normally so I tackled a program running on the ISY that did a smooth fade to off in around three seconds. Not very elegant, but it worked perfectly. However, eisy executes the original program so fast it's like hitting a stop button. Here it is below. Sonos volume fade off - [ID 0018][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'ST-Sonos / Bathroom' Group Volume 27% Set 'ST-Sonos / Bathroom' Group Volume 24% Set 'ST-Sonos / Bathroom' Group Volume 21% Set 'ST-Sonos / Bathroom' Group Volume 18% Set 'ST-Sonos / Bathroom' Group Volume 15% Set 'ST-Sonos / Bathroom' Group Volume 12% Set 'ST-Sonos / Bathroom' Group Volume 9% Set 'ST-Sonos / Bathroom' Group Volume 6% Set 'ST-Sonos / Bathroom' Group Volume 3% Set 'ST-Sonos' Pause All Set 'ST-Sonos / Bathroom' Group Volume 30% I've tried: Wait one second between steps Way too slow Wait zero seconds As expected, not a noticeable change Repeat 2 wait zero seconds Unexpectedly very slow I put repeat 1 before each of the volume steps so only the wait would repeat twice Two wait or more zero seconds steps instead of repeat 2 Too fast again Repeat 1 wait zero seconds Same as wait zero seconds Setting 1% volume increments Appears to hammer the node server too much and too fast so the volume settings are all over the place after the program runs I tried 2%. 3% steps in succession seems to be the maximum the node server can handle. This is what I have now after all the experimentation. It's too step-y and too slow but the best so far on eisy. If I take the repeat 2s out, way too fast. Sonos volume fade off - [ID 0018][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 2 times Set 'ST-Sonos / Bathroom' Group Volume 25% Repeat 2 times Set 'ST-Sonos / Bathroom' Group Volume 20% Repeat 2 times Set 'ST-Sonos / Bathroom' Group Volume 15% Repeat 2 times Set 'ST-Sonos / Bathroom' Group Volume 10% Repeat 1 times Set 'ST-Sonos' Pause All Wait 1 second Set 'ST-Sonos / Bathroom' Group Volume 30% Wait 1 second Set 'ST-Sonos / Office' Player Volume 15% Else - No Actions - (To add one, press 'Action') I've also noticed some other programs and Insteon device status' aren't as reliable as they were on the ISY. Programs running too fast to be reliable? Don't know. I've made a lot of recent changes redoing my network closet so the problem could be related to that. Although I've used UD devices for many, many years now, my programming tends to be pretty basic. Anyone have a suggestion here? @Michel Kohanim, any chance of an IoX wait enhancement to fractions of a second or some other way to slow a program down? Thanks

I didn't even have to do that this time. A first.

Oddly, this is the first IoX version on eisy that started right back up for me after the upgrade. All previous versions required a restart, repower, or something. Weird.

IoX 5.5.6 on eisy has, thankfully, fixed the Hue node server. Previously on 5.5.5, Hue would not survive any sort of restart or upgrade.

I don't know. The various node servers seem to have their own particular issues on eisy. The ST-Sonos server was completely non-functional in PG3x until recently. Hue was OK until IoX 5.5.5. One version of PG3x required a Hue reinstall, then it was fine. This is the first problem I've had when just a restart breaks something. The Hue server is the one I use the most.

Per our posts in the Hue section, the Hue node server with eisy IoX 5.5.5 quits after every restart. Even though Hue says it's connected, it doesn't work. You have to delete and set up again.

Same. IoX 5.5.5 broke the Hue node server. Reinstall didn't work. Had to: Delete Hue node server Reinstall Hue Add the bridges custom parameter I had to add this step one or two IoX versions ago. Press the Hue hub button and restart the node server. It should prompt you for this. Go into the admin panel to add Hue devices back to scenes. Hue steps in programs had to be selected, updated, and saved. Any sort of restart of eisy requires a complete redo of the above steps. I haven't tried a restore yet. I'll try that the next time I have to unplug everything. That will probably be tomorrow since I'm reorganizing my network cabinet.

Up and running with PG3x. The Hue node server was "disconnected." Tried several restarts. Ended up deleting and installing again. Had to add the "bridges" custom parameter. It works but doesn't survive any sort of restart. I have to do everything Hue related again. A reinstallation doesn't work. Only delete and install. Edit: Also, managed to delete Hue out of all my scenes. Makes sense, but I haven't had this happen before. Hue in programs just had to be clicked on, updated, and saved.

Same PG3x problem on eisy. I've had this pretty much every time after an IoX update. Usually an eisy systems settings reboot gets it back. Not this time. Repowering didn't work, either.

Yes, it did. The dashboard and store are still showing 1.0.7, btw. But it's clearly a new version since it works now. My exit-music-fade-to-off-pause-and-reset-volume program executes so rapidly on eisy compared to the ISY, it's really like hitting the pause button. I'll have to play with it. I've run into other eisy's-too-fast issues after switching over. Some steps in other old ISY programs I had to add repeats to make them more reliable. All Insteon fwiw. Thanks!

I've been using the eISY for over a month now. This node server has never worked on eISY. I've tried every version of IoX and PG3x since late Dec. Multiple installs, restarts, etc. All Sonos S2, and a wired connection to the eISY and half of my Sonos devices. Dashboard shows connected with one ST-Sonos controller node. No device nodes. Today, I noticed 1.0.7 of ST-Sonos. Changelog says "update to work with eisy," along with a 50% price cut. Still doesn't work. Same as before, "connected" with one node. I attached my 1.0.7 debug log if anyone wants to take a peek. ST-Sonos_1-31-2023_64452-PM.zip

eISY .20 I get this popup about every 30 seconds. This didn't happen repeatedly with previous versions. Also, my ST-Sonos shows connected with one node for the first time ever on eisy. It still doesn't work, though.

Updated to 3.1.18 and reinstalled ST-Sonos node server on eisy. Still disconnected. Logs are the same as the OP.

Agreeing with UD tech support on this. You're basically describing a near Faraday cage location. While I agree a USB extension cable would be preferred, I think the difference from an antenna extension would be negligible.

Did you try reboot on the admin console?

same same. And "Current Status: Disconnected" on the ISY Dashboard page. It was disconnected on 3.1.16 also, but I never had any logs on 16.

I had the same. It fixed itself eventually and didn't seem to make a difference.

Good point and understood. My experience is a little different. I had one ISY-99 a long time ago, and until a few days ago, six ISY-994s running. I finally stopped concurrently running my personal 994 and switched it completely over to Polisy last week. Never had a failure. My eisy will be here soon. I've also never had a PLM failure. Lucky, I guess.

Wouldn't you still have a single point of failure?

Unfortunately, I have this happen every two weeks or so. A restart of the Sonos node server always gets it going again for me.