MikeB

I knew they weren't manufacturing much at all, and I knew they were prioritizing switches over things like PLMs, but based on this thread I thought they had officially dropped the PLM. That would have been incredibly stupid, but perhaps not out of character.

When did they kill the serial PLM? I wasn't aware of that.

Another device I had to remove from its scene and re-add it, which corrected the issue. Looks like I'll have to take each problem switch on a case by case basis.

This worked to fix at least some devices, but today as I'm testing it seems it to not fix all devices that have this issue. Some devices show "Request Failed" when trying to set the PLM Communications retry parameter.

My post was over complicated. Even if I remove the devices from the scene and test each 1 individually, the same symptoms occurred - the status very briefly turns on then immediately back off when the switch is pressed on. After some testing, I found some of my devices exhibited the same behavior but others did not. Poking around a bit, if I right-click a problem device and choose Advanced, PLM Communication, the ones that had issues were set to "Unsupported Value". If I change it to "1 retry" the device seems to work fine! Will be testing more tomorrow.

Tried upgrading to 5.3.3. - same issue. FAST ON (double-tap) works fine. It's almost as if the ISY thinks the on level of the device/controller is 0, but unless I'm missing something with the new v5 firmware I don't believe that's the case.

Long time ISY user here. Things have been pretty much status quote for a long time, I have not had much time to invest in my system other that replacing failing switches, etc. I decided to upgrade to firmware version 5 a while back for compatibility with a phone app if I recall. Upgrade was pretty painless. Was having some intermittent issues with my ISY a couple months ago that I believe were caused by a failing SD card. After replacing the SD card I reinstalled the latest firmware and restored from backup. Everything seemed to go without a hitch, except my ISY is not seeing device traffic (switch presses, etc.). I could control my devices from the ISY (and my Amazon Echos) without issue, but device statuses were not accurate because it was not seeing switch presses. I checked out the Event Logs and no switch presses were being shown. I went ahead and restored my PLM thinking perhaps it got reset somewhere along then line. That restored most functionality, however I'm still noticing at least flakey issue. For example, I have a scene "OfficeMain" that includes 2 SwitchLincs as controller/responders (OfficeMain1 and OfficeMain2). If I press the switch OfficeMain1 to turn the light on, on the ISY both switches will show as ON, but then OfficeMain1 (the switch I pressed) will immediately change to Off (though the switch itself stays on - the problem is just the ISY device status). The problem is the same if I turn on OfficeMain2. Both switches turn on as they should. In the ISY both show as on, but then OfficeMain2 immediately changes to Off. Here is a log showing when I press OfficeMain1 on: Sun 03/21/2021 04:34:28 PM : [ 57 36 D0 1] DON 0 Sun 03/21/2021 04:34:28 PM : [ 57 36 D0 1] ST 255 (uom=100 prec=0) Sun 03/21/2021 04:34:28 PM : [ 52 8A 75 1] ST 255 (uom=100 prec=0) Sun 03/21/2021 04:34:28 PM : [ 57 36 D0 1] DON 1 Sun 03/21/2021 04:34:28 PM : [ 57 36 D0 1] ST 1 (uom=100 prec=0) Sun 03/21/2021 04:34:28 PM : [ 57 36 D0 1] DON 1 57.36.D0 is OfficeMain1 52.8A.75 is OfficeMain2 I tried removing both devices from the scene and re-adding them, but the same behavior remains. I'm not sure if I would have noticed this issue unless I was troubleshooting communication problems in the Admin Console, so not sure if this occurred after upgrading to version 5 or after replacing the SD card. Anyone have any suggestions? Thanks!

Interested in this topic as well. I only have 1 INSTEON thermostat currently (2-piece version), but I think it's time I finished this project and replaced my others. Although I want to integrate thermostat control and notifications with the ISY, integration with the Amazon Echo is priority #1.

Just got an email from a local distributor saying they will be carrying this light switch. Looks interesting! I hope there is some way to integrate with the ISY/INSTEON.

Very cool! Thanks for sharing.

I had been limping along with my Hue Emulator setup until last night. Some phrases that had worked long ago stopped working over time. Yesterday I finally took the time to migrate over to the ISY Portal and love it so far, but it did not fix the spoken word recognition issue. Long ago "turn on pink floyd radio" worked to initiate a SONOS playlist, but stopped working a while back. Just recently "turn on goodbye" and "turn on goodnight" worked but stopped probably with this last update. Using the keywords "music" or "radio" seems to be a problem. For example, "office music" worked but "kitchen music" did not, so for consistency I had to change to something else. I am using these: "office sonos" "kitchen sonos" "living room sonos" "floyd sonos" "classic sonos" ...etc. Hopefully it stays working. Spoken word changes are tough to digest, especially for other family members that get used to saying certain commands and now have to change. Really hurts the WAF. For "goodnight" and "goodbye", oddly enough changing the spoken words to "good night" and "good bye" seems to work! I hope it stays working.

Back up now over here!

I finally got rid of my Hue emulator setup and got the Echo/ISY integration through the ISY Portal working yesterday. There was a short period of time yesterday afternoon where I believe the ISY Portal was down (Echo's response to commands was "That command doesn't work on device..." Other than that I had everything working well yesterday evening. This AM Echo started responding again with the above error and lost the ability to discover devices. I came here and found this thread. It's good to know there is an outage and not an issue specific to me! As of right now I am once again able to discover devices and the Echo seems to be responding normally.

I do know that Smarthome was looking to replace the RS-232 transceiver chip in the PLM last year because of frequent failures. Perhaps newer ones are more reliable.

Although I'm sure bad power can result in frequent PLM failures for some, you would also be experiencing frequent failures on other INSTEON devices.