larryllix

Have you used scene modifiers including battery operate Insteon devices? If so, ISY will constantly attempt to update those devices that cannot be updated without being in "linking mode". Since about v5.1.x this has been a bug in the concept and UDI hasn't fixed it. As a work-around you can disable battery device writes and attempt to empty the ISY cache for each device by putting them into linking mode and attempting to write updates to each device, one at a time. The other method is to factory reset your ISY. Unfortunately, until this bug is recognised and fixed, it will likely keep happening.

Only problem I have had with my NRs is if you change the values of the variable being substituted it may go out with the new value instead of the intended value. The values are substituted at send time, and not at invocation time. That becomes a problem for ISY as it's smallest time delay is 1 second and that makes rapid sending of NRs from a single NR very slow.

When I have events to report via NRs, I use variable substitution, using numbers for rooms or devices, I always include a small chart like this. Eg. Motion has been detected in room 23 <------ was variable substituted all from one NR. Rooms: RecRm=11, EveBR=12, AftBR=13, LLand=19 GathRm=21, MBR=23, Foyer=25, MudRm=29 Shop=31

Be aware of variable substitution also. I operate about 35 RGBW bulbs and strips from three NRs. I rarely use 1 x ON NR, frequently 1 x setLevels NR, and 1 x Off NR, for all devices. Each of the three NRs contain strings of text containing the commands.

Two of my three units were battery run and those two batteries both went dead in less than a year each. One went dead with the spare battery in that time so it consumed two batteries in less than a year. All three are on USB adapters now and that hassle is over now. My other 12 MS1s are still on 9v batteries and I get between 8 to 15 months out of most discount (alkaline Walmart, Panasonic, EverReady) batteries, depending on activities. Duracell 9v batteries lasted about 4-5 months and I finally gave up on them since they became junk.

Mine has been doing this for about a week or more. Looks like GH has some similar problems and a possible screw up in the handshake systems??

Can you say when this started? EDIT: Duh! You already reported the timeframe. I have linked this to another thread where Benoit (the author) has responded.

Go Ontario!!!! ? ?

KPLs have so many Insteon links and get messed up frequently. Try a Restore from ISY to ensure the links are all intact.

Same here since about the last ISY Portal upgrade. Alexa doesn't seem to understand the device descriptions well and reports a lot of "I don't know what went wrong". There is also a lot of "I don't know that device", even though the device has already changed state via ISY. It would seem something isn't working correctly between ISY Portal and the Alexa portal handshaking.

Note: If you have to disable and re-enable the connection on the Alexa app and your ISY Portal, all Alexa Routines will be destroyed and without triggers. This means you will have to reselect a trigger and re-enable each Routine again. The Enable switch is somewhat ambiguous as to what position it is in. IIRC it is not clear whether the control is instructive, or the current state, of the routine. Also if you select a IFTTT output you can make a household announcement from a routine. I only select specific speakers though. If you select All speakers it can become unintelligible due to sounding like being in a huge echoic chamber.

Welcome to the UDI forums!! Create a STATE variable named $sSayDoorBellBattery (or other) Write a program in ISY that is triggered by the event at 30%. In the Then section install lines to make $sSayDoorBellBattery = 1, Wait 10 seconds and then $sSayDoorBellBattery = 0 In the ISY Portal Alexa section, define a pseudo Motion Detector from the state variable created, and call it "RingDoorBellLow". Use 1 for the variable Detected value and 0 for the undetected value. On your Alexa speaker say "Alexa...Discover" On your Alexa mobile app, create Routine using the pseudo MS device as a trigger. Create a custom vocal output with the words of your choice. Note: Routines are not accessible on a Windows PC, Alexa app. Battery<30% (If) ------->ISY state variable = 1 ------>ISYPortal name ------>Alexa Routine------->Custom speaker output

I bought my first PLM in 2014. After thinking it would become a problem I have bought two more PLMs since. After testing them, I removed each one and replaced my original PLM and it still runs just fine.

Think how much better the product would be, designed by an HA guy that understands the needs and wants of HA. "end to end...." Maybe Michel could buy it, backed by HA crowd sourced money? Make the eproms in the Insteon devices open source and let the crowd go wild with other styles of comms and compatibilities.

My guess is they are to lazy to hire a sales team. How many new managements and owners have the company had now? Something wrong with the building. Insteon already includes an RF protocol. They just need to decouple it from the grid frequency protocol. Send the RF first, and if it is more than 10 feet away, back it up with the powerline protocol.

I had to disable and re-enable my CAO Wireless Tags accounts to get them back "on Alexa line" again. That was a first time for Tag problems in 2-3 years. I think Amazon has had some server problems that may have been software edit botched lately. My Alexa commands continue to have problems still. They constantly fail saying they are having trouble but still work, and at times just don't work and/or misunderstand devices substituting other room and device names that I may or may not have.

Over half the businesses in my small town have closed up, never to return now. This factor could be an excuse for Insteon's actions, or a further indication they are folding up.

I seem to have developed a problem between the Alexa cloud server and the ISY portal server or my ISY. When given a command, Alexa reports "something went wrong" or other errors most of the time. Most of the time the command is successful anyway, and functions after 5 to 60 seconds, despite the vocal complaint.. It does seem that some times during the day are worse than others, as there are times when everything works perfectly with good speed, and other times it complains every time and can take up to about 60 seconds to function. Occasionally it just fails. We have noticed a lot of Alexa substituting other room names or not understanding what we said, or just failing to function with "OK" feedback. Is there some way to determine what is happening on this system between my ISY and my Alexas? I am not sure when this started but it seems about the time the maintenance was done so it may or may not be related.

So tplink doesn't threaten legal action against the people to remove comments that libel them on forums? It's just like linux. It was rock solid (like MSDos and all the rest ) until they started trying to come up to MS standards with a GUI. Now it crashes like the best of them. My older ASUS router handled all the DHCP table I could throw at it until it actually got used. The DHCP table was fine but the rest wasn't. The third party (super bug fixing) firmware made it worse. Now I stick with the manufacturer's firmware that understands the hardware inside. These WiFi repeating systems have made it worse too. I haven't seen one yet that functions properly or doesn't grind the speeds down to a crawl. WTF are you using uPnP for with ISY? I don't even know why ISY has it as an option.

Ever try a different cable or another Ethernet location in your house, a different port on your router? Kind'o sounds like an intermittent connection. How about factory resetting the router?

Michel for CEO! Michel for CEO! Michel for CEO! Michel for CEO! Michel for CEO!

You can't expect your ISY to talk to anything on the router's subnet when you have excluded IS from that allowed range of IP addresses. You have restricted your router to a tight range of IP addresses and made all other devices blind to your ISY. Unless you set your router to "ad-hoc" LAN (not likely) it controls all traffic on your LAN and all traffic must be handled by your router. Being outside of the IP address range tells the router to ignore your ISY.

My ASUS routers handles my 75 LAN devices just fine. Only the master node router provides DHCP. However my older ASUS router caused really obscure havoc at about 51 devices. Drove me around the bend for about two years. Why are you not using the range of .0 to .254? My guess is that is causing confusion. Also using 8.8.8.8 IMHO may be causing you probems. How can an ISY without an IP address talk to a cloud based DNS server via a router that can't recognise the ISY? Again. Try the full subnet range and use the router address for it's DNS handler. Keep things standard and simple until you get it working.

Try setting the ISY DNS to your router and let it figure it out 192.168.0.1. I suspect 8.8.8.8 (Google) doesn't know what your internal LAN layout looks like.

Who knows it Insteon actually has any documentation to share? Judging by the previous actions of the company it is a one man operation in somebody's garage and all the technology is inside somebody's head, with the greatest of intent to write it all down some day. These devices are all manufactured and tested in China, and likely all the design, and misleading docs for US patent faking was done by the same Chinese workers that built them. A fancy building warehousing parts in California, can give the impression of an established American company and bypass many taxation and political border blockades. Why would Insteon be any different than so many other products in the tech world these days?