larryllix

We are having problems with SMS messaging lately and it seems to be getting worse over time. After deleting messages from my IoP they sometimes pop back up 3,4 days later ad new messages. For years, now I have noticed the same thing happening g with old messages, when they show up gain, along with actual new messages. I always figured it was my android os but now, not so sure. Sent from my SM-G781W using Tapatalk

Yes. IIRC ISY and polisy have a wide range of tolerances for power supply, although 5V sounds a little low.

Just my own NRbridge that translates NR commands to MagicHome RGBW bulb and led strip signals. That includes a keepalive thread that polls bulbs every few minutes each. Only running about 8 devices now. Previously (old home) about 50 devices without problem. New router and AP for WiFi delivery since move. Installed inside polisy again also. Polisy hard wired to router. Sent from my SM-G781W using Tapatalk

I believe this may be centered around my software also running on polisy. Previously, it seemed to be a problem running under polisy O/S and I moved it back to an RPi again where it has ran without problem for a few years. I suspect it could be related to a different python 3 implementation under freeBSD, and/or a threaded keepalive task running. I need to implement a logging system to record operation successes and failures, if any, so that I can zoom in on this. Hiccoughs have been very rare...maybe once every few months. I do have a SiLabs ZWave stick plugged into polisy, unused at this time, also. WE do seem to get a lot of power blinks, early in the mornings here, so I may watch those times more closely. Just as an aside my lat/long produces a sunrise about 20 minutes later than actual. However I am 26 floors up and that may be the reason. No the earth isn't flat!

No. RPi is gone, PG2 is gone, IoP programs started fresh, only a few devices connected, NRbridge software moved from RPi to polisy and using :localhost URL via NRs, new lat/long, new ISP. This happened after a power blink that morning. Seems to be a polisy power up sequence problem...maybe.

Yeah, but for the second time now I am contemplating going back to ISY994. Too many bugs and lockups on IoP. Had another one last night where my NRbridge firmware driving my MagicHome lights would not operate some RGBW strings after a power blink. Still not up quite to par with ISY994 and a RPi, unfortunately, at least the way I use it.

Too many "irons in the fire"?

May be geek vs. user advice.

What are you using to bridge ISY to it? NS, NR?

Getting the "busy text box" in your admin console?

All Insteon devices have a factory reset method. They are complex CPU based devices and can get goofy at times. Always, always factory reset new Insteon devices before linking them into ISY to avoid many hidden problems. They come out of the factory in many unknown states.

Most of the time you have to at least reload the admin console. Most of the setup is a load with boot-up thing. Admin console is not dynamic in many cases.

Mine did a similar thing but I can't remember what I had to do. I did have to reinstall the PIN key into the ecobee website setup. The first one took OK and then failed right after for some reason. With mine I deleted PG2 ecobee NS as I moved. New stat and new PG3 install. Not sure if that made any difference. Check the ecobee NS logs. IIRC I had several PIN rejected lines inside the log.

If you have good backups (IoP and PG3) , you could factory reset your polisy and re-install. Open a ticket with UDI. They may have some techniques to sniff your password. Your port address may have changed or be forgotten.

You don't upgrade PG2. It is not supported any more. Stay as you are or upgrade to PG3.

Yup cloud dependence is awesome and easy... ...until it isn't. Roger's seems to be back up again. Sent from my SM-G781W using Tapatalk

Most advice is to never use automatic lighting in staircases. It is dangerous, as the sudden darkness makes people freeze and they can fall down the stairs from the sensory/brain confusion it causes.

IoP admin console doesn't display/load Notification Menu @Michel Kohanim The custom notifications menu is always blank until a notification is edited and then updates. This happens each time the admin console is loaded.

The forum needs a sticky (permanently at the top) thread with announcements for new features only from our fearless leader(s), so that user stay informed of recent upgrades and avoid some of the new feature confusion in the forum as well as lower the WTF? traffic here. Sort of like a digital Vatican balcony? Thanks!

Is that the button I didn't know I needed to push because I didn't know there was one?

"Don't use SSH anymore to update"? ..but it is so much simpler and I gave up on clicking that hard to find reset button. I don't think it every worked properly on my Polisy, yet. I cannot tell if it is pushed or not. Blindly pushing a metal object into a hole is not a good thing. I have never been sure there is even a PB back there.

Thanks! 2.1G still avail here.

Sounds like another device may have got onto the IP address and clobbered your comms with polisy. Have you assigned an IP address for it in the DHCP reservation table or manually assigned an IP address inside your polisy? If this is the problem you may need to assign an IP address in your router for a fixed address and then power cycle your router to force the other device to assume another IP address.

What doesn't work about it? Give more details (what does it do and doesn't do) as the logic looks good here.

@Michel Kohanim @bpwwer Battery device MS 1 device Option button, hangs IoP while Battery Write option is disabled. Trying to set an option on a newly -reinstalled Insteon MS I. Trying to use the deferred writes feature to write to the MS using the triggered write program technique. However every time I click the MS device "Options" it hangs IoP and it has to be rebooted. Restarting it on the admin console configuration page doesn't seem to do it. After I get a TCP error message box or the one below, the ISY admin console goes into a perpetual busy indication and most functions lock up. I can see some programs updating variables from the ISY internal clocks but not much else works. After 10-15 minutes the busy boxes still keep coming up. I have only installed about 20 program so far on this new environment. The only way I can get any control of my IoP v5.4.4 is to reboot the whole polisy or SSH use sudo service ISY restart Note that "sudo sevice udx restart" did not reset the problem, although when reloading ISY Launcher, the UUID address only ever shows 00:00:00:00:00:00 until ISY is restarted or power cycled. This has been repeated with the same result at least 10 times now.