MrBill

Open Each of the referenced scenes, the scene attributes need to be set for the root level and each controller link. example: First click the root level "Attic Fan" and set the attributes on the right side window. Then click each of the RED Controller node (Controllers are Red, responders are blue) and set the attributes of each device in the scene. For this example we need to configure the scene 4 times. Most at first don't realize how powerful scenes and controllers are. The attributes set at the root level are what happens when the scene is controlled by the ISY, either from the admin console, an app, or via a portal integration such as Alexa). When you click each of the RED controller links that's what happans when the scene is activated from that controller. So for example, if you have a Kitchen Scene and a controller at each end of the kitchen, the scene can respond differntly when the controller at the Left end of the kitchen is used than when the controller at the right end of the kitchen. Note: If there are buttons that need to be turned On/off on another keypad, they must be included as responders. I can't tell you exactly what you've done wrong, but perhaps a better understanding of scenes will help you find the misconfiguration.

The scene setup looks correct, but the button pressed don't seem to be. You mentioned "I'm still wondering if this is a bug in my program somewhere (even though it is very simple." Do you in fact also have a program involved in this. If so, you likely don't need it, but please post it. (right click the program name in the program tree, and pick Copy to clipboard. In the forum press the <> button on the toolbar and then Ctrl-v in the resulting window.)

Kasa SmartPlugs 4 for 24.99 They are on/off only devices (not dimmers), and you need Polyglot (either via Polisy or rPi) to run the Kasa nodeserver. If you don't need to Dim they work amazing. I have 12 total.

So Everything is off: Press C and the scene turns on. And the backlight, behind the C button turns on? The scene is on: you say it takes 2 presses to turn off the scene. What is the status of the backlight behind C? When the second condition occurs, how did the scene get turned on? Via another switch or? when you open the scene in the device tree, would you please take a screencap and show what the members of the sceen look like. (to do this in Windows, press windowskey-shift-s, click and hold top left of screencap move to bottom right and release the click. the screen cap is now on you clipboard. Click in a forum message window and press Ctrl-v)

Even tho it shows connected did you try restarting it?

Home Assistant released an official core Screenlogic Integration in April, that works very well (however does require Screenlogic, Autelis was a screenlogic alternative but could be used with screenlogic as well. HA also has an official ISY-994 integration that also works very well. I have both Autelis and HA... I could go thru and change the way things work and get rid of Autelis now and my ISY and Insteon controls could still work, so far tho the old system (Autelis/ISY/Insteon) still works great, so I have no intention of "fixing it".

Keep your eye out for those. If they come back we need to figure out why. You're on 5.3.3 so you're past the point that the known issue was fixed.

the Pentair product lines with "Intelli" included in the product name all interconnect using a semi-proprietary protocol over RS484. It was one labeled "proprietary", but effectively it's been reverse engineered so now I'd call it semi-proprietary.

I spoke too soon, I was confusing Superflo for Intelliflo. Superflo you simply need relays to control 1 of 4 relay inputs the pump has. As @midrar points out that could be using relay of an Elk integration. there's a few other ways to control relays as well.

do you have easytouch/suntouch/intellitouch control system? If so do you have ScreenLogic? Yes my ISY can control... unfortunately the Autelis interface is no longer available, however if you have screenlogic you can control via Home Assistant, which can be interfaced to the ISY thereby giving you Control via Insteon. There's also this thread via rPi and nodeJS.

@bpwwer I attempted to collect your data 3 times and all 3 times it loaded correctly from logged out state without pausing.... (although that wasn't true an hour ago).

Still not working here.... I wonder if @bmercier is around....

Mine worked this morning... but is now exhibiting the same behavior as described above.

Open tools > Diagnostics > Event Viewer Change the dropdown to level 3. "Clear" the window Make the malfunction occur. at the end press copy to clipboard (the button looks like a clipboard) reply to this thread, press the "<>" in the toolbar then paste the clipboard here.

You're past the bug that relates to "adjust scene".... which creates a lot of need to write to wireless devices. To solve your problem tho, you need to get rid of all the 1101 icons sitting on the left side of the device name in the tree. To get rid of them the devices needs to be put into linking mode and then "write changes". Once you've gotten rid of them be hyper vigilant about allowing them to build up which as of 5.3.2 shouldn't occur from use of "adjust scene" by a program. From 5.3.2 release notes:

any that have a grey icon "1101" have pending writes waiting. If you have pending writes for a bunch of sensors and then make a change the ISY tries to update all of them. There is a reason I asked your firmware revision. too much typing to explain if it doesn't apply to you... an additional related question is "do your programs use "adjust scene"?"

Do you have wireless Insteon devices? What firmware version are you using? Do you have pro or non-pro?

If you formatted the SD card the default is user admin and password admin Upon logging in you must reinstall firmware 5.3.0 and THEN restore your backup.

Bet it's noise.... I don't think mobilinc does any kind of monitor/retry you're just getting lucky when you reach that try...

You'll want to be sure to set Level 3: What type of fixture and bulb is this? is there a transformer or ballast? or LED bulb?

I thought I typed that that part doesn't make sense... as far as I know it should be no different between mobilinc and the admin console. However using the Event Viewer you can see if anything is different between what is sent. The question about Alexa is relevant tho. Alexa may not be set up to turn off the correct thing, if she never does it. Again use the event viewer to see what is actually happening. BTW... What kind of light/fixture is it?

What kind of light/fixture is it? I suspect noise. It doesn't effect the ON because the noise doesn't start until the light is on, preventing the OFF from being consistently received. What happens if you manually run Then from the ISY (right click the program name, run then)? does it always turn off or only some of the time? For troubleshooting open the Event Viewer (Admin Console) > Tools > Diagnotics > Event Viewer) and set it to Level 3 before 10PM then if you don't understand all the entries you can copy them and paste them into a message in this thread. (I can't read the event log as well as I should, but others here do.) From this wiki: https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors Other things to try for troubleshooting purposes... if you have multiple 10PM events try moving this one to 10:01 or 10:03. You can also try adding multiple off's to the program, separated by wait's... Set 'YardLights' Off Wait 30 sec Set 'YardLights' Off Wait 30 sec Set 'YardLights' Off Wait 30 sec Set 'YardLights' Off Then if you start seeing more consistency in the lights "eventually" getting turned off it's more likely a noise problem. Also if 'YardLights' is a scene, try turning off the load instead. What happens from the admin console (right click, run then) should be the same thing that Lastly, does 10PM in the error log (Admin Console > Tools > Error Log) shed any clues?

@mangoJust to toss this out there..... You can swap faces between 6 and 8 button keypads if that helps you get brightness levels side by side to behave better. there's also a paragraph in that post for 6 button to 8 button. I know your specific problem is v.44 vs v.45, but if you can swap hardware around to get what you want it may be worth it.

There may be a few programs that need manual adjustment particularly if you use "adjust scene". Programs requiring manual adjustment are relatively easy to find... look for Yellow on the programs summary page after the upgrade is complete. Also programs that have a statement that doesn't automatically upgrade will have a comment in place of the missing program line. Another step you can take to make certain you know what the old program looked like is to left click "My Programs" at the top of the program tree (or the very top folder if you've renamed it) then Right Click and pick "Copy Folder to clipboard", now open Notepad or any text editor (preferably one that doesn't add formatting) and paste the clipboard. now you can save the file or leave it open and in addition to your full ISY backup you now have a text backup of the programs for reference. Be sure to BACK-UP as the first step. Also don't stop at 5.3.0 go straight to 5.3.3. There are some programs that don't update automatically... for the most part tho upgrade from 4 to 5 is a smother process than it once was especially with no z-wave.

The problem is that you've only configured it for when they keypad button is the controller. how to accomplish this is a bit differnt between V4 and V5 off the ISY firmware. In V4 there is a copy button you can use. In V5, you need to click the root level of the scene and also configure the scene there. The Red controller link for the keypad button is already done. For Example: with this scene, I need to configure it 3 times, Once at the root level (highlight now), and then again for each of the Red controller links. Each can be different, or all three can be the same configuration.