larryllix

No. Look in the admin console. The field is called "Luminance". The older MS's field Night/Day doesn't exist anymore.

ISY has developed a problem writing to battery devices and some Insteon plug-in devices over the last year or so. I have no Zwave but many of my Insteon devices have had to be put into linking mode and manually updated. This is not just battery devices anymore but AC powered devices also. The battery write option can be disabled but each time ISY gets rebooted the option turns itself back on and ISY grinds to a halt with massive caching of writing to so many devices. I have attempted to bring this to UDI's attention but has been ignored many times over the last two years in the latest releases. A "run at startup" program to disable the battery write option, can help but is a poor workaround, as the a cache is already full of update instruction by the time the program runs. The updating of Insteon Scenes needs to go back to the way it was previously, and stop attempting to write to battery devices completely. The "Battery Write" option needs to remember where it was last set. as a minimum. I had to put each battery device and about 8 plug-in devices into linking mode and select update to get my ISY back to functioning again. Now every so often I find ISY's cache full of owing writes again, and crippled for HA speed, again. I have also experienced several "ALL-ON" events now, that ISY has become so famous for.

AS per @kclenden above, this is what we have seen so far. 48MotionNotificationFlash5IS0EQ112502502501112223334445556667778889991010101111112121213131314141415151516161617171718181819191920202021212122222223232344EQ0try { Object.defineProperty(screen, "availTop", { value: 0 }); } catch (e) {} try { Object.defineProperty(screen, "availLeft", { value: 0 }); } catch (e) {} try { Object.defineProperty(screen, "availWidth", { value: 1280 }); } catch (e) {} try { Object.defineProperty(screen, "availHeight", { value: 720 }); } catch (e) {} try { Object.defineProperty(screen, "colorDepth", { value: 24 }); } catch (e) {} try { Object.defineProperty(screen, "pixelDepth", { value: 24 }); } catch (e) {} try { Object.defineProperty(navigator, "hardwareConcurrency", { value: 8 }); } catch (e) {} try { Object.defineProperty(navigator, "appVersion", { value: "5.0 (Windows)" }); } catch (e) {} try { Object.defineProperty(navigator, "doNotTrack", { value: "unspecified" }); } catch (e) {} try { window.screenY = 713 } catch (e) { } try { window.screenTop = 713 } catch (e) { } try { window.top.window.outerHeight = window.screen.height } catch (e) { } try { window.screenX = 1273 } catch (e) { } try { window.screenLeft = 1273 } catch (e) { } try { window.top.window.outerWidth = window.screen.width } catch (e) { } Again. Post your programs so people can help. Right click on each program, select copy to clipboard, paste into your thread, so that somebody can understand what you are posting about.

On the webpage of the MS Motion page when you click on your "54.69.C3..1 Motion" node in your device tree.

That was the point. Many of my non-battery, plug-in, devices were a problem also and will not update without the linking mode enabled. IIRC that didn't happen before but during the PLM restore. I know there are different types of update signals and queries from ISY though. When initial linking was done with these devices, none of them required linking mode.

ahhhh. he just upgraded. Perhaps he grabbed the non-PLM firmware??

Possible PLM failure. Have you tried to power up your PLM first, and then power up your ISY994? (after) Have you attempted a Restore on any device yet?

An HVAC vent can do that. You may have the devices you can record HVAC cycle times to check for coincidental times. Alternatively you could force your heating on at the stat and watch for MS events. Review your false event times for possible HVAC recovery fro setbacks etc.. There may be some clues there.

hmmmm...dying USB wallwart?

Dying battery?

I found I had to go around and place each battery device into the linking mode and do a "write updates" to each device. Then I discovered the PLM restore doesn't work for almost half my dual band plug-in devices either. I had to put many of them into linking mode also, as they would not take an update without being in linking mode first. Until you completely update all your devices ISY will be close to being crippled at times with attempts to write constantly devices that won't take them. ISY V5.3.0 It never goes away after months of slow ISY operations until you manully update each device. About half my LampLincs and a few SwitchLinc Dimmers needed to be in linking mode first to clear out the ISY cache. I even found one OnOff module needed to be in linking mode and it resolved the constant "can't connect" errors for the last two years after my last temporary trial of a spare PLM. Query of status always works even without a proper Write Update procedure. Self update and controls do not usually work.

Post your programs.

If you are using ISY Portal you will have full access to your ISY without knowing the LAN IP address of it anyway. If you have access to the router and are using port forwarding, some newer routers had a port forwarding that would follow the IP address of the destination device.

Rev 2.0 LD with good component placement Rev 2.6 LD with defective component placement design. Great engineering from the new Insteon! (sarc) Note they gave up on procuring OEM batteries also.

None. It's in the Motion repertoire of fields.

I posted a thread about two horrible new design LDs, I got a year or so ago. Complete junk. They changed a component and didn't refabricate the lid so it wouldn't actually close. Then when the id was opened, if it opened from one the end, the other end's catch would pry on a coil and break it. I kept one unit as I was desperate for a replacement unit, but the nice folks at aartech.ca took the broken one back.

Yeah, wrong device for that application. If the water got that high your pump couldn't fix it in time (it was already failing) and you would have had to toss the LD in the bin, and buy a new one each time. The Insteon LD need extendable legs on the sensor tips so the electronics weren't ruined with bigger leaks. IIRC @Tekenfabricated one like that with long bolts.

The whole point of a leak detector is to get you to look at the water damage location and then you are on site anyway.

Oh you are using Zwave? I think this may only apply for Insteon devices and then only with ISY Pro.

Bad comms and the MS has lost some links between it and your PLM, and cannot write to the MS and get a proper response. Put the MS into linking mode ad the use the "Write updates" on it from the admin console. Turn your Battery Writes option off with the top of the admin console screen button. Unfortunately ISY will forget this setting and start attempting writes to it again after any power cycle or reboot. This can be circumvented if the MS is powered by an adapter (MS II only) or no scene modifying program lines, including the MS in that scene, are used.

Just hit the button to reload the programs or reload the admin console without saving anything.

Just factory reset it and then load the latest version of firmware. Sent using Tapatalk

Your browser is never considered a server, but always a client. The error message indicates a server. I had that error when my ports were not set up right with my ISY and now when polyglot is rebooting after a setup change. But it shouldn't vary with a different browser so a very confusing report. MY mistake. The error must be coming from your browser about the polyglot server. More programmer laziness when reporting errors. They tend to see things from their POV during the programming. Odd the browser would get half way through the webpage and then not comm anymore. I don't think polyglot has used any newer html5 tricks that may not be supported. It all looks like basic old-tech stuff to me. Another update: The last screen shot indicates polyglot cannot connect to the ISY or device also. That is definitely coming from polyglot in it's status box. It would appear your browser may be causing polyglot to crash.

That appears to be a connection to ISY problem and I don't see how the browser in iOS should be related. If Safari were not connected to the polyglot server you shouldn't have a webpage at all.

Alexa has been having some real issues in the last few days. I have been getting "Something went wrong" on every command through ISY Portal but then the action is still completed. This has been happening for several days. Today, we didn't hear this, so something has changed. I put in a beef about their Routines not triggering properly under certain conditions, and they reported back they know they have some problems and will work on it soon. Then things went weird for a bit a few days ago. Now things appear to be returning to normal again. hope, hope.