MrBill

I'd suggest everyone take a moment to read this article..... it's the one I thought I read a few months ago... Apparently it was last September when Sidewalk was announced. Sidewalk creates its own 900Mhz network. IT DOES NOT USE YOUR WIFI for foreign devices. Your Alexa connects to your Wifi yes... the Sidewalk mesh is in the 900Mhz band and is only other devices talking to your Amazon. Your wifi password is NOT SHARED. https://www.cnet.com/news/amazon-sidewalk-extends-your-network-but-security-is-already-in-question/

Except they haven't... Amazon Sidewalk does NOT USE YOUR WIFI.

The whole point of my post was Apple did the same thing with everyone's iPhone, and Apple didn't even give a way to opt out.... Crickets... no one is complaining about Apple pulling the same stunt but without an opt-out method. If I thought Amazon Sidewalk would help me I'd probably leave it on, I don't believe it's a security threat-- but I only have limited information. I have a bunch of Alexa's, No Ring tho, and I think all my Alexa's except one are too old to participate in "Sidewalk". I don't know what my neighbors have or do I care. And I can't imagine how my Amazon network would help them anyway. To be Clear, sidewalk doesn't share my wifi, but does use some of my bandwidth bucket that isn't unlimited... although I never reach the bandwidth cap. The CNET article I read sometime back (months) seemed to indicate the devices that might be using this most were Fitness Trackers and Dog Collars (a product I don't even think is on the market yet). I just find it hilariously funny that there is so much hype about Amazon Sidewalk right now when Apple does the same thing and not a single eye is batting...

@Eric Toggle mode is under a button named none other than "Buttons Toggle Mode" What I meant was remove that from all scenes, then remove the keypad itself from the ISY (right click it in the tree and pick "delete"), then factory Reset it. After its factory reset... you can tell from the detail under Step 4 of the factory reset instructions above if it factory reset, then relink the keypad to the ISY as if it was a new device (since we completly deleted it. Finally, since there are suspensions that they device might be bad, do you have another button somewhere else on another keypad that you could use to experiment?

@Eric to add to that.... After you get the module deleted from all scene's, delete the device from the ISY as well. Then factory reset it one more time. and then add it back from scratch.

Good plan. I had trouble following your scene setup it might be that you have conflicting settings in two scenes that are each being activated. Make a single scene and test, then add in complexity, testing at each step. From a few posts back: Make the outlet a controller (instead of a responder) and then the backlight button will stay in synch when the button on the outlet is pressed.

@Eric That is an old model keypad. However I'm not sure if you got the factory reset correct. You need to hold the set button in until it beeps. (source)

This is reasonably easy to do, but you need a second variable. and for that variable a simple integer variable will do. Since the state variable is sMusic, let's call this one iMusic. Program 1 If sMusic = 1 then (do whatever need to always be done) Run Program 2 (if) else (none) Program 2 (DISABLED) if iMusic = 0 then (do whatever needs to happen if the old setting was 0 iMusic = sMusic else Run Program 3 (if) Program 3 (DISABLED) If iMusic = 2 then (do whatever needs to happen if the old setting was 2 iMusic = sMusic else iMusic = sMusic /* keeps variables in sync if old was neither 1 or 2 The key element here is that Programs 2 and 3 are disabled, which means they will not run automatically when the IF statement becomes true. In actuality in this case since the IF statement is only using a integer variable it wouldn't anyway, but if the variable was a state variable or some other object that could become true, if the program is disabled it won't run by itself, but will run if linked from another program. Obviously you have to have the variables in synch to start with, but they should stay that way with this program series.

I find it funny that when Amazon does this it's publicized like it's a national emergency. On the other hand... Apple essentially did the same thing with its new AirTags. An AirTag can use any nearby iPhone to phone home the GPS coordinates of the AirTag. Apple opted everybody in, and didn't even give a method to opt out. For some reason no one even noticed. Do we trust Apple more than we trust Amazon? That said, I turned Amazon sidewalk off a few months ago when the setting first appeared in the app. I'm not sure why I did. Maybe I do believe it's hackable, maybe I just don't want to study what it is and how it really works in detail.... i.e. an informed decision. But with Apple there was no decision.

Have you followed the instructions in this wiki page: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Garage_Door_Kit As far as inverting it for the A button, you can add that button to the same scene and program it with the opposite logic in the scene.

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.)

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