MrBill

I don't think your understanding Line noise and Signal suckers yet. It's not the copper wire. Some brands of bulbs and transformers generate specific powerline noise that blocks the signal. Other devices suck or absorb signal so that it can't make it to other parts of a circuit. Here's a wiki article of troubleshooting Insteon There's another thread I can't seem to find but copy and paste the following into google (without the quotes) "site:forum.universal-devices.com Noise Signal Suckers" there are quite a few related threads on how to locate the offenders.

I have a state variable $sDark that can have 3 values: 0 = Daytime, from sunrise to sunset 1 = Early Evening, Sunset to Bedtime 2 = Late night, Bedtime to Sunrise Bedtime when we are home is determined by a specific button press, if $sAway is set bedtime is a random number of minutes (up to 72) after 9:46pm A huge advantage to using a state variable is that for testing purposes it's very easy to shift to "Early evening" or "late night" mode at any given moment. For example I can manually change the variable right now to see how things work during a different time period. Most programs that occur at a time use a combination of $sDark and $sAway in their conditions instead. The Exception is there is a folder of lighting programs that run when $sAway mode is on... the programs in that folder all have there own timers to make a random 'someone is home' look. I did end up with an area specific variable also... $sDark.kitchen has very similar except that Early Evening occurs at Dinnertime, or Sunset (whichever comes first). "Dinner time" is either pressing a KPL button or saying "Alexa, it's dinner time". 0 = Daytime, from sunrise to sunset 1 = Early Evening, Sunset or "dinner time" to Bedtime 2 = Late night, Bedtime to Sunrise

I actually wondered that as I was typing, but excluded the thought because it really doesn't address the problem that OP illustrates in their final bullet: the cost of data... whether its limited calls per24 to an API somewhere, or as it seems in OPs example hardware pushing data to a single location (maybe I'm misunderstanding their example).

The ! means that the ISY didn't get a response when it tried to talk to the iolinc, It could mean a bad iolinc, but more than likely means that you have noise blocking the signal. Especially important with iolinc is that it is not a dual band device. To test you could bring the iolinc and plug it into the same circuit as the PLM or perhaps get out a long extension cord to do the same. " I threw every breaker and still doesn't work. " doesn't tell us exactly what you did. It also doesn't eliminate a noisy LED light bulb (or someother noise make / signal sucker) on the same circuit as the iolinc. Here's a detailed wiki page on Troubleshooting Insteon Communication Errors.

Right. That was basically my thoughts but not spelled out to the same level of detail. (half my thought is actually in the post replying to madcodger).... On the other hand tho I can definitely see the need to be able to somehow copy duplicate nodes between boxes (generic word on purpose), the perfect example of why: Polisy/Polyglot/ISY A is in the house, Polisy/Polyglot/ISY B is in the barn.... weather data comes from a website who's API requires a key and calls per 24h are limited, only one polyglot instance can be updated from the weather suppliers cloud but must somehow update another instance. So the $64,000 questions becomes should polyglot itself be able to cascade to more than one instance, or should there be a CopyNodes nodesever that handles multiple boxes..... ( I have no idea but like you say it's definitely something that needs to be included in the thought process) Thinking about it there's really need to go both directions, location B may have nodes that location A needs to know about.

I agree with @lilyoyo1 you have a noise issue. Specifically when the complaint is specifically about OFF being missed it usually means the the loads themselves are generating the line noise. They always turn on because the load doesn't generate noise when it's off, but when they time to turn off arrives there is line noise and the signal gets lost. With as many loads as you have here it may not be each load, for example there might be one load that is creating noise for several switches. Suspects are loads that have transformers or drivers. etc....which leaves open many type of bulbs themselves that have integrated electronics such as LEDs. Try leaving those turned off and see if you can turn off the other switches reliably.

it's not what you're looking for but there is this nodeserver: https://github.com/simplextech/udi-poly-isynet I don't know how much work would be required to get it to mirror more node type, but let's tag @simplextech and see what he thinks, there's been at least one other thread where a remote ISY in an outbuilding would be a good solution.

You're correct, a second instance of polyglot would be required. Polyglot holds credentials to the ISY that its updating, there is no provision for multiple ISY's in a single instance. Remember that someday in the future only one box will be needed Polisy, which will be running both Polyglot and ISY. What I can't understand is if you have migrated away from the platform because you didn't like it, why do you hang around this community? It's ok that the platform no longer meets your needs but why do find the need to take time to write paragraphs over and over about your dissatisfaction with the current state?

You're mistaken about who needs to issue a fix for this issue. Roomie Remote is a third party that has has not issued a new version supporting ISY's v5.x firmware. You might want to ask Roomie Remote Support or in the Roomie Remote User Forum if there are plans to support ISY V5. You also may be mistaken about your user demographics, but I have no data to disprove your 50% assumption. There are a few posts here but overall I don't think there is a huge cross-section of users.

Any chance something was touching something that shouldn't have? It sounds like you had a dead short that blew the triac in the dimmer, and blew itself open at the same time.

@vspete Which type of error? [UDSockets] RSub:30 error:6 or Net Module Rule: 4

That's awesome error log info, added to my notes. In this case, I'm going to bet that error isn't messing up subscriptions... it's an error all the same... I'm betting on the RSub 13: Error 6 or RSub 30: Error 6.... any idea what those mean?

Wes will get notified of this because it's posted in Mobilinc, he washed his hands of this issue long ago tho. As it turns out it seems to be more about ISY subscriptions getting confused because the admin console gets drug into the arena with the "Already subscribed" dialog box. The interesting thing is that Agave and ekeypad both seem to be immune and can even seem to help. Michel may be able to help more but I suspect the output from http://ISY-IP/rest/subscriptions might be a key. Now that we've got another person getting the error I wish @TrojanHorse would also log in. I also think this has more to do with information being posted into the ISY than outbound network resources, but I'm very interested in your theory about it being Networking module Rule 4.... I've tried to learn how to read the very cryptic error log in the past (in many cases the error table in the wiki doesn't tell you much more).

@vspete I don't think it's related to the UDQ queue full errors at startup/reboot (as signified by Start -5).... my system actually does still experience that condition. I suspect the culrpit is this type: Fri 2021/01/01 12:05:23 PM System -170001 [UDSockets] RSub:13 error:6 Fri 2021/01/01 12:05:23 PM System -170001 [UDSockets] RSub:30 error:6 Fri 2021/01/01 12:05:28 PM System -170001 [UDSockets] RSub:13 error:6 Fri 2021/01/01 12:05:28 PM System -170001 [UDSockets] RSub:30 error:6 but I don't know what that actually means....

Again, I would just make 3 scene's. None of which have Adjust scene as a component. Then the programs will just do one thing.. turn on the appropriate scene at the appropriate time.

@Michel Kohanim so my take is that it seems this long running problem that we've never nailed down is the result of some error in the ISY that results in confused subscriptions, and agave and ekeypad both seem immune, or actually can help resolve the problem. to recap: Generally after the error has occurred mobilinc pro users will see "Mobilinc Disconnected... attempting to reconnect", upon subsequently attempting to open the admin console they will get the "Already Subscribed" dialog box from the admin console, there is no obvious way around that error short of rebooting ISY. Rebooting the ISY cures all, until the error happens again. @TrojanHorse first reported here, that ekeypad could be used to create a "fix". I later did the same thing with agave, however I only used one phone (as opposed to his two). Those fixes only worked tho if you didn't try to open the admin console, once you tried that you would enter the "already subscribed" area of the problem. I can't recreate the original problem anymore to test new theories because my ISY pretty much is running error free, and mobilinc works without fail whenever I try it. (at some point last summer I was trying hard to make the Mobilinc error occur, but couldn't because I had addressed the error log issues.) I don't know how relevant this is but: one thing that was contributing to my error log issues (a year ago) was that I was using a wireless tags kumo app at the time to get temp/humidity data into the ISY, moving that component to a Polisy nodeserver I believe got rid of a lot of the errors.

I agree with @Screw Loose Dan , I would not adjust scene, but create multiple scenes. Also I agree that you should post your actual programs rather than type your interpretation of them... But if you knew how to do that you would have done it because its faster and easier..... to copy a program into the forum click the program name, then right click... the very bottom item on the context menu is "copy to clipboard", choose that, then paste it into your post by right clicking and picking paste or just typing control-V.

Please try downloading the file again, its possible the file your loading to the ISY is corrupt. Be certain that you're downloading the correct file for your ISY (PLM vs No PLM), and don't unzip it after download, just upload it to the ISY as is.

Right Click "My Programs" There are options to find devices, scenes, variables, etc.... note that Raw Text is case sensitive. TO my knowledge yellow hi-lited programs do not run. I've only seen them twice tho, once when I upgraded to 5.x and recently when i did actually delete an Insteon module by mistake.

Actually Mobilinc Pro does work with iOS 14.3 I've mostly moved on to other methods but do on rare occasions open Mobilinc Pro to do something that hasn't been planned for. For example, after midnight last night when we got in bed I realized I had over ridden outside lighting to the 'early evening' scene and needed to move it back to the 'late night' scene, I did use Mobilinc Pro for that, worked fine. When you say "unreliable" do you mean that it works sometimes but then for unexplained reasons you start getting a popup at the bottom of the screen that says something like "mobilinc has disconnected, attempting to reconnect"? At that point it becomes maddening to get mobilinc to re-connect? If so, I've been there, and so have some others in this forum. If you open the admin console at this point in time, do you get an "Already subscribed" dialog box? Then you reboot your ISY and it takes care Already subscribed, and mobilinc also works again.. for awhile? The above described bug was what drove me away from Mobilinc a couple years ago. I can't tell you EXACTLY what fixed it for me, but around a year ago I was having weird ISY issues and discovered a lot of Queue Full Errors and other things I couldn't explain in the ISY error log. I ended up opening a ticket, it was a very frustrating experience, but eventually got it so that there are very few entries in my error log on a daily basis, since that time every time I make many changes I watch the error log like a hawk to make sure I haven't created something that creates errors (the ISY does a fabulous job of recovering from most, but some seem to have lingering effects). Anyway to make a long story short... I no longer have the "Mobilinc Disconnected / Already subscribed" bug. After @TrojanHorse and others revived the topic I began opening mobilinc everyday again, attempting to recreate the issue... I can't anymore. Knowing now that Admin Console "already subscribed" bug I was also attempting on 3 different iOS devices randomly thinking the subscriptions were just getting confused. I could never recreate it... the only thing I can say that was substantially different is that the discovery that I could no longer recreate the maddening Mobilinc bug was right after I attacked errors in the ISY error log.

The method I use is that every controllable plug-in module is labeled (Brother P-touch label maker) with its ISY node name, that makes finding the disabled nodes quick, then if they are repurposed I simultaneously relabel and rename in the ISY. This avoids having to delete and re-add in the ISY. I've also learned (the hard way) to search programs for the devices being renamed. Kasa plug-in modules also have a second label: kasa0, kasa1, .... that corresponds to it's name in the router's DHCP reservation table.

Have you tried a factory reset of the lamplinc followed by a Restore Device from the admin console? You might also try swapping two of the lamplinc's to see if the problem follows. Another issue might be Minimum load "small led Christmas lights" is a very minimal load. what happens if you add to it, temporarily to test... such as a 60 watt incandescent bulb...

To clarify what's been discussed so far. 2842-222 is a version 1 motion sensor, which is what @wdhille has 8 of. The screen shot showing battery level is for a motion sensor version 2 (2844-222) As @larryllix points to monitor or listen for low battery on Version 1 motion sensors you must have a program. I don't have any version 1 motion sensors but it would be very similar to the program below written for hidden door sensors. AllRecessedDoorSW - [ID 0044][Parent 0037] If 'Door Switches / Barn Walk-thru Door / Barn Walk-thru Low Batt' is switched On Or 'Door Switches / Costco Rm NEW - Door / Costco Rm NEW Low Battery' is switched On Or 'Door Switches / Front Door / Front Door- Low Bat' is switched On Or 'Door Switches / Garage to House Door 2 / Garage to House Low Battery' is switched On Or 'Door Switches / Green Rm Closet Door / Green Rm Closet Low Battery' is switched On Or 'Door Switches / Laundry Rm Door / Laundry Rm Door - Low Battery' is switched On Or 'Door Switches / MBR Closet 2 Door / MBR Closet 2 Low Battery' is switched On Or 'Door Switches / Playroom Door / Playroom Door Low Battery' is switched On Or 'Door Switches / Pool Closet - Door Sensor / Pool Closet Door - Low Batter' is switched On Or 'Door Switches / Pushbutton Block / Pushbutton Block.3 - Low Batt' is switched On Then Send Notification to 'Bill' content 'DoorName' Else - No Actions - (To add one, press 'Action') Then for the Custom notification email you would create: using the # replacement for the nodename. Note this works because the default nodename includes the words "low battery".

Click on Network or ISY at the top of the tree on the Main tab of the admin console. THEN in the right window click the column header for ADDRESS to sort by that column. EDIT: I was wrong... Click NETWORK, not either.... I didn't look closely enough at the folder structure.... I made a bad assumption...

Depends on how good you are with a soldering iron. I would tack on two more wires right there at the fan where you see the red and black wires attach. Probably the simplest way is to use some type of wire tap like this: https://www.amazon.com/Nicelux-Electrical-Connectors-Connection-Self-Stripping/dp/B07ZC4CTLW which crimps on.