larryllix

Does this mean the lack of chip sourcing was just BS or just ordering person dependent? Strange how it could suddenly be "fixed". ROFLMFAO!

I am with Virgin Mobile in Canada, a subsidiary of Bell Mobility (100% owned) , using the same networks and towers, and possibly the same software and servers? I have the same problem occasionally. I get text messages hours later, as well as get the same text messages days later after I deleted them. This has been going on for years now and getting worse. I thought it was just my lack of noticing the messages coming in but it has been happening too often lately for messages labeled as new, (in bold) but the ISY text tells me it was sent 2 days earlier. IOW: I believe this may be a Bell Canada SMS server problem with messages not being cleared properly and/or handled properly (getting lost).

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

You been cross-border shoppin', or that can is over 40 years old.

Careful with WD40. It connot be identified as a lubricant in Canada and is very corrosive. Took us a few dozen corroded brass locks with dissolved tumblers before we got the service technicians stopped using it and our purchase agent stopped buying cases if it for field usage. American cans may still label it a lubricant. Great penetrating oil but will eat the plating off almost metal going. Note the WHMS hand skeleton on the can? Sent from my SM-G781W using Tapatalk

I have 7 or 8 of these leak detectors and they all operate with the required link button press to reset them. However, mine are all older versions, possibly. I think the designer's idea was to force you to check out the leak location, and you have to clean the water out of the unit before it can be used again anyway. The compact design ensures you will have electronics underwater if you have a serious leak. The insides of the LDs usually need to be dried out before re-using them.

It's either McAfee or Pfizer always trying to tell us we need them for something. Sent from my SM-G781W using Tapatalk

Sure would be nice for Ken to run a thread here, so people can feel 'homey' with him and develop that trust feel that makes UDI so great. Nothing like users feeling like they are part of an Insteon family, as well as the ISY family, for a comfortable feel they can 'write home' about. Welcome Uncle Ken! Sent from my SM-G781W using Tapatalk

..to elaborate, that is why we advise to use 'control switched' construct as 'status' would not function for a non-alternating status. 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.

UDI could sell their PLM through Insteon and save them some development time and help get Insteon back on it's feet faster. This could be an Insteon marketing breakthrough indicating their real user co-operation intent. @Michel Kohanim Sent from my SM-G781W using Tapatalk

If I read it correctly, the new owners bought Insteon while Smartlabs still exists and was never for sale or in trouble. I don't know the twisted corporate tree structure here, but who knows in this world, these days? Sent from my SM-G781W using Tapatalk

Will the load work from a remote location via signals? If so, then some contact cleaner shot down the throat of that switch may clean up the contacts and make it work again.

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.