-
Alexa no longer responding to state variable motion.
Wish there was a free solution but I might have to give this a try.
-
Alexa no longer responding to state variable motion.
Hi All, I have a couple Alexa routines that are triggered buy a "fake" motion sensor associated with a state variable on the ISY. This has been working for years but just recently stopped. The device in the Alexa app indicates "Device is unresponsive". I found another thread (now closed) where other user(s) have had the same exact issue and it seems to be something on the Amazon side. There doesn't seem to be a solution other than spend hours on multiple support calls with Amazon and then hope it will be magically fixed. Even if I could get through to a real person for Amazon support, I'm not sure how I could explain what's going on? I'm sure they would suggest deleting all the routines, deleting all the devices, deleting the app, reboot, etc etc. I've already tried this with no success. The problem is obviously not wide-spread. Any suggestions on how to resolve this? Anyone else dealing the the same issue?
-
Cannot restore plm error: Could not read config file
I'll give this a try, thanks!
-
Cannot restore plm error: Could not read config file
Is the only way to recover from the bad file is an eisy restore? There must be some way to get the eisy to re-read switch data?
-
Cannot restore plm error: Could not read config file
I disabled the switch and then I was able to restore the PLM. Still not sure what's going on with that switch.
-
Cannot restore plm error: Could not read config file
Hi All, Recently we've been having some issues with our motion sensors not working (any of them) and some other intermittent issues. In the past to resolve this we've restored the modem (plm). But when I try to do that now, it gets to about 7% and then fails with an error message: Could not read config file [./FILES/CONF/50B976.REC]. The device that seems to be an issue (50.B9.76) is a Dual Band SwitchLinc On/Off switch (2477S) and it seems to be working fine, although if I try to restore that device I get the same error. Any suggestions on how to resolve this?
DGG
Members
-
Joined
-
Last visited