MrBill

Have you tried completely deleting the program and recreating it? or even create a second identical program and disable this copy.

I did miss the 994 in the title when i as i thought through the possibilities and wondered if it was an IoP issue... Does the Program Summary tab give you any clue? Like a yellow warning message for the program. If the admin console was open when the program quit responding you may need to close the admin console and re-open it to see a non-normal status on the summary page.

v5.3.4 generally implies you're speaking of an ISY994 and not a Polisy running IoP, but since there was a 5.3.4 at one point on Polisy it's ambiguous which hardware you're running on.... I essentially do the same thing, only updating 1 state variable, and never have the problem. Perhaps you should post your programs. (Right click the program name, Copy to Clipboard, and then paste into a post.) The only other issue I can imagine is that your programs becoming corrupt which would hint at a bad SD card, but I think you would be having much greater issues than just this...

Something really sounds off here.... at one time @InsteonNut had a great relationship with UD. The only thing I can figure is mobilinc is asking for a change or update that UD can't accommodate in the current vision. I choose to move away from mobilinc long ago... but still actually use mobilinc pro for one obscure needs that pops up a few times a year.

As mentioned elsewhere, you're also running HA, you can add the screenlogic integration. Then pick the values that you need updated to ISY and I'll be more than happy to assist you getting them there and/or creating automations on the HA side that meet your needs. Unfortunately there are only about 3 users: you, me and one more that have Screenlogic, there is not a great demand for the node server.

@Michel Kohanim specificity stated PG2 can't be stopped just yet. Remove all the node servers and ignore it. Shouldn't use any noticeable resources running empty.

My point is the best way to do it is just create programs that do everything themselves.... the way you're using programs as subroutines can work, I do it several places such as my goodnight and away routines that use the same list of turn off's. You're not saving a million lines of code doing it the way your doing it, but you're creating a buffer timing issue. I thought you could work around that by moving the Run program to the bottom of the program and adding a wait before it, but you said that didn't work. My best suggestion is have your programs do everything they need to do within one program. In the case of my Goodnight / away situation yes the turn off list is a common THEN block but it's the only string of insteon commands being sent, so once insteon is being executed there are no other programs to inject "noise" or "confusion".

Gosh I guess your right, I'd have trouble imagining a complex installation. I have 346 Insteon Nodes, 112 scenes, 67 node server nodes, 87 state variables 109 integer variables and 507 programs, that the ISY, on the Home Assistant side there's even more.... but I likely can't imagine an installation as complex as yours. Good Luck!

UD's always been a hardware company. Polisy and eisy are brothers... they both based on FreeBSD. UD chose a platform purposely so that it wasn't simple to just go the Pi route. Unfortunately we are at an odd time in the lifecycle of the product. Last April Insteon closed it's doors, as a result there was huge unprecedented and unexpected demand for Polisy. To UD's surprise it was unable to order some parts with appropriate lead times, so Polisy was redesigned and 'eisy' was born. Very similar to Polisy similar main board, slightly different ports and a different case, both run the same software under FreeBSD. Actually it's not difficult to figure out... but by your own admission you haven't been paying attention. @Geddy explained it all... but you seem to have chose to either not read or not absorb his post. Polyglot 2 which was NOT originally created by UD is deprecated. The Developer is gone, no longer working in the project. Polyglot 3 was developed by UD to run on hardware produced by UD. As noted, you may be able to get PG2 running on a Pi, but the developer is no longer around. UD's new hardware will be available very soon, its has taken a little longer than originally predicted and the ship date hasn't been announced but we are down to weeks, not months.

@GTench I agree with @Geddy even if it's informational when they are posting sometimes two rows per second as in your log, it's time to get to the bottom of it. You can send your entire log to support@universal-devices.com they maybe able to identify an issue. Your error log shouldn't get hammered like that. My error log gets just a few rows per day usually.

A feature is that each scene controller can control the scene differently. Click first on the Scene name, or the root of the scene, look at the right window, that's how the scene is configured when the ISY itself is the controller. Now click each scene controller one at a time (each RED link) and check the the scene is correctly configured for each scene controller/button.

What I would do if I were you is just simplify this. If Time is Sunset - 30 minutes Then Set 'Scenes / Device Scenes / Front Outside' On Set 'Devices / Master Bedroom / Master Bedroom KP Dimmer / A: Master Bedroom Outlet' Backlight On 1 / Off 0 Set 'Devices / Living Room / Living Room Lamp Dimmer' On 60% Set 'Scenes / Special Scenes / KitchenIslandAndSink' On Set 'Scenes / Device Scenes / Office Brian' On Set 'Scenes / Device Scenes / Office Lori' On Set 'Scenes / Program Related_Scenes / KPL All Off On / prs_KPL_All_Kitchen_On' On Resource 'Hue Morracan Lamp On' Else - No Actions - (To add one, press 'Action')

Yes don't stop it. Also I would NOT upgrade firmware until you get your system back to normal. Beware upgrading from 4.9 to 5.3.4 may or may not be a simple upgrade. Don't just upgrade from 4.9 to 5.3.4 without doing your homework, and get your system working correctly first.

@headless, I agree with @TFay... also keep in mind that @io_guy isn't making any money off nodelink. It free software and it's supported pretty darn well for free stuff.

FYI, File > Restore devices should be reserved for specific cases. Also you need to avoid other insteon traffic during that process. if your system is large it takes awhile, other traffic will often times create new problems you didn't have before. Before using File > Restore devices I would try to stop programs with a false IF statement in the My Programs Folder (be sure to remove it later), and if you have motions either put paper over them or make sure no one triggers them. After "Restore Device" (the individual device) doesn't work, the next step should be to Factory Reset the device, and "Restore Device" a second time. If you create new profiles with your "Restore Devices" above just use individual "Restore Device" to try and fix it.

I have a lot of H is "all off" instances, but I don't really use the concept of all on. H is simply set as "Non-Toggle Off" and is attached to a scene only, not a program. If your use case is working for you go for it.... but it does increase the amount of insteon communication required, thereby creating some of the collisions you're dealing with. I really think moving the "sub-routine" to starting 3 seconds after the other commands will improve your situation.

Comcast Mail: Server: smtp.comcast.net user: the part before the @ only From: Home:full@email.com (Note: TEXT COLON full@email.com -- both halves of this field MUST BE populated) Use TLS: Checked Port: 587 Password: YOUR PASSWORD Timeout: long, I use 3000 on a 994, there are reports it needs to be longer like 10,000 on Polisy. Don't Fill out the FROM line in customization, leave it fully blank, not even a space.

If these programs are about turning keypad buttons on an off, just include them in scenes. You don't need programs for this. Insteon has what I call "sloppy" scene's. You can create scene's that are separate and include those devices and buttons in other scene's. For example I have two buttons at the front door that are scene controllers for the top and bottom of the front porch outlets. Those outlets, and the buttons are also included in other scenes, one in the general outdoor lighting scene that has many members, and the other outlet and its button appears in the "holiday" scene.

@bjs169 I'd rewrite the first program like this: If Time is Sunset - 30 minutes Then Set 'Scenes / Device Scenes / Front Outside' On Set 'Devices / Master Bedroom / Master Bedroom KP Dimmer / A: Master Bedroom Outlet' Backlight On 1 / Off 0 Wait 3 seconds Run Program 'Downstairs Some On' (THEN) Else - No Actions - (To add one, press 'Action') I suspect the Insteon buffer is getting trashed, because two programs are sending commands at once. The error log probably shows these collisions. Let the first "sunset program" get it's commands out, then trigger the second program. What's the purpose of the variable that is being set via the third program? That program seems like there are better ways to approach the issue? how is the variable used? I assume it's a state variable? i See you already answered that let me study that a minute...

Did you install Java version 8 from https://www.java.com or some other version? The official version 8 is supported, others versions may work but often require fiddling.

Blinking error light likely means your microSD card went tits up. Try to reseat it, and/or check if the file system is readable by removing it and using a usb adapter on your computer. If isn’t replace it, reload firmware, and restore your last backup, in that order. there’s a wiki article, but I’m having issues getting the link at the moment.

Or if it’s the 3 dots… there’s exactly one font size, I believe 14, that causes that, change the font size.

Change the “Time” Is drop-down to “From” I think that’s what your asking about.

I doubt anyone except @Michel Kohanim can answer, you might want to open a ticket for a speedier connection to him.. let us know the outcome!

what does the admin console show as the node address at the top? Does that match?