MrBill

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.

There's an uglier aspect also, if you haven't thought of it.... deleting devices one by one, factory resetting, then re-adding to a hub or USB PLM. I won't do that until I can't buy anymore PLMs, but I have like 100+ Insteon devices--If your system is smaller, maybe it's not a big issue for you. Also Insteon hubs aren't immune from the power supply problem, my son uses one in his non-isy, Alexa as the brain set-up. The hub failed once, the difference is that smarthome will replace it free of charge and they do some magic so that recovery using the replacement is plug and play. With shipping It took over a week tho. All in all, I think the ISY programming is easier, and it's definitely rock solid, maybe that changes over time as one learns, but for the few HA automations I have written I find it difficult. Comparing the communities, people here in this forum and much more helpful than the much larger in number HA community. The few posts I've made on that forum have not brought any useful help.

I have almost no automatons set up in HA. Using it almost exclusively as a front end to the ISY. I like that I can design my own screens for mobile. I like that I can control a scene but when it's on have the control change to a device dimmer (this requires a lovelace add-on from HACS and an understanding of how to use HA services directly). I've only had HA since about the start of this year and I have been expanding my usage slightly, but I have no intention of moving "programming" that's already working well to HA. It does however provide a level of control that didn't previously exist. It's also WA (or Wife Approved), she disliked both mobilinc and Agave she however enjoys HA as a user... it works like she expects, things are in the order she expects and she doesn't need to remember things like whether to use a scene or device for this or that. As a footnote: I agree with what others have said, that PLM might be on it's way to failure. PLM's are out of stock at smarthome, but there are still 16 available (as of 2 seconds ago) at Amazon. You may want to order a backup.

I use the HA ISY integration and I very sincerely doubt this is caused by that. The UDI HA integration is actually fairly rock solid and actively developed, personally I've never had a problem. Two observations: First, you didn't say you tried restarting the ISY... If you haven't that is the very next thing you should try. Remember that after a boot no battery sensor will have a known status. After reboot I always make a test walk and force them all to report once so that there status is again known. Given that your event viewer window is all blue like that, I think that's further indication you need a restart. Also verify via Help > About your firmware and UI versions are the same. Second, you have a lot of unwritten instructions. Those cause problems even with wireless writes turned off, like you have it. I would put each device that has wireless writes that need to be written into programming mode and get rid of all those. Then if your on a ver. 5 branch less than 5.3.3 get your firmware upgraded because that bug has been fixed and they should no longer accumulate via "adjust scene". Before the fix, I was constantly having to restart the ISY, until I got rid of all the "adjust scene" situations then I could go months again without restart. Finally, what does your ISY error log look like? Any clues there?

you can actually connect two bodies of water by siphon too, and there levels will remain constant. we actually use the concept in out greenhouse, but I googled for a graphic to illustrate: http://www.gardengrapevine.com/RainBarrelDwg2.gif In the greenhouse the hose we use is flexible and has a male hose fitting on one end, so I just submerge the hose and get all the air out of it, then screw a cap onto the end with a fitting to bring it to the other container. As long as both ends remain underwater and no air gets into the hose the siphon principle works. How could you use this concept with a pond? Bury a 5 gallon bucket nearby. Use PVC parts to make a semi rigid mount and feed assembly for a toilet float and position it in the bucket. then use a garden hose remnant to connect the bucket to the pond with a siphon.

they do. I just downloaded both versions from this thread. Please tell us what is happening for you.... and/or include screenshots.