- Code: Select all
2017-10-05 12:23:46.225 Error unknown command bytes received 00 00 (ignoring)
2017-10-05 12:23:48.305 Error unknown command bytes received 00 80 (ignoring)
2017-10-05 12:23:48.958 Error unknown command bytes received 00 00 (ignoring)
The errors got worse as the day went on, and Indigo became unresponsive, with all sorts of strange network timeouts for Fingscan, Weather, and Sonos plugins. Indigo touch clients would not connect, nor would DomoPad. When I got home, my first thought wasn't the PLM, mostly due to the network errors. I checked the OS install, scanning the drive for errors and then running a full virus scan. Both came back clean. Network "things" outside of Indigo on the server behaved normally, Indigo had just taken a s@%t so it seemed. I thought perhaps something had happened to the Indigo Install, or the DB, so I deleted the install, restored from a week-old backup, and did a re-install of Inside on top of that. No change.
Thats when I noticed that the PLM didn't have a LED on. The Hue hub is plugged into the same outlet and it was on so I pulled the PLM and re-plugged, nothing. I disabled the interface in Indigo and then Indigo came back to life, the Sonos plugin, weather plugin, Fingscan, all of it started working. I enabled the PLM interface in Indigo again, and everything went to hell. Anyone ever seen anything like that?
I went online to order a new PLM and Amazon kindly told me that I had last ordered a 2413U on December 24th, 2013 (Merry Christmas to me ). I had forgotten about that horrible failure, but then I was pleased to see that I had gotten almost 4 years out of the PLM, which is supposed to be the bad one (PLMs prior to rev 23). I'll write the date on the new one one in case I don't get the next from Amazon. We'll see how long the new one lasts - I actually thought almost 4 years was pretty decent, considering the failure rates I read about on the various forums. How long is everyone else's PLMs holding up?
Terry