sorka

You mean on the same 15 amp circuit? A router, multiple apple airplays, tivos, an hdmi switch. Is there something you think that could be on the same circuit that would cause the PLM to lose links that WOULDN'T cause bad communication?

So this didn't fix the problem. The folder did turn red but programs inside the folder continue to execute. I didn't have time to debug this back then and have come back to it now: The state variable is 0. The condition is "$AlarmType is not 0". The folder is red. Programs continue to execute inside the folder. This used to work once upon a time.

This is still occurring. Just happened today. Lost ALL links on my 2 month old PLM. I don't believe for a second that it's a PLM defect. It's happened on every PLM I've had and doesn't appear to happen more with the age of the PLM. I'm losing hope that this will ever be fixed.

Interesting. So I tried something different. I selected the dropdown and selected remotelinc. I then added the address and pressed OK(even though this remotelinc is in my device list already). It started writing and immediately blew through the first 3 links in the list. It then stuck on 4 until it finally stopped. The write updates icon remained next to the switches on the remotelinc so it obviously didn't finish. I did get responses from the remtelinc for the first three lincs so it's not a transceiver hardware failure. Seems more like a bug. Additional repeat attempts have it coming up starting at link 4 and just sitting there.

I'm having the same issue. Just replaced the PLM a few months ago straight from Smarthome. My 3 PLM. All the other wireless sensors updated just fine when "write updates to device" were selected. But both remotelincs won't update. They actually still work because the links are still the same but the ISY thinks they need to be updated. Brand new batteries in the remotelincs.

That seems to have done the trick. At least the folder turns red now when the state is 1 and green when the state is 0. Thanks guys

Strange. I'll change it to a state variable but I've had it like this for at least a year and it has worked just fine before that.

Yes, UI is also the same version. On 6/27 it was rebooted because the power went out(my UPS failed). When it came back up, I manually set that variable back to 1. The programs run if I manually trigger the then case but not if I trigger the if because the if is triggered on a motion sensor turning on so just right clicking and running the if case does nothing.

Used to work fine but suddenly not working fine any more. I have a bunch of programs in a folder where the folder conditional check is to run only if a variable is == 0. Variable set to 1: Check that variable is set to 0 before programs in this folder can run: Currently running 4.3.26.

OK. I guess you have to stick the the "turn on" and then program name. I can live with that but no spoken phrase can include "alarm" in it at all. Alexa will intercept this and ask you for an alarm time. Major bummer and means I won't be able to integrate commands to my alarm system unless this is fixed.

So I added some more spoken terms for those programs that didn't include alarm in the hopes that Alexa is just getting confused. When I use those alternates, I get a funny hi low beep from Alexa and nothing else.

I added a new scene with a preset level to 30% that includes the living room load. I called it "Living Room Lights Low". I added to the portal in the spoken / node section and called it "Living Room Lights To Low" and "Living Room Lights Low". Ir re-ran discovery and then tried various "turn on living room lights to low" or "set living room lights to low" or "set living room lights to low on" but to no avail. Alexa tells me every time there is no device with that name.

Interesting. So the ones I tried adding earlier are now there without me readding them. I re-ran discovery just now but the Echo won't run the programs. I have "arm alarm" and "disarm alarm" and if I speak "arm alarm" or "run arm alarm" or "run program arm alarm" Alexa asks me each time to set the alarm for ;(

Works fine if I create a portal entry just for the dimming light switch itself, if I use the scene which includes remote switches, it doesn't work. Brighten and Dim work fine but then I'd have to say it a bunch of times to get it at the level I want. Not a good user experience.

Still getting this same thing this morning but for me it just says "error returned".

Whenever I select a program from Spoken Nodes and Scenes, I get an error "Error Returned" on the portal page. No issues adding devices or scenes. Just programs.

Yes, the original PLC never had an issue.

I've replaced my PLM 3 times since moving to the 994 and never before that. This only started happening after moving to the 994.

I don't think it's the PLM. This has been happening to me every 2 to 3 months since I first reported it back in 2014: http://forum.universal-devices.com/topic/12107-all-my-motion-sensors-stopped-working-simultaneously/page-2 I've been through 4 PLMs and it doesn't get any better with the new PLM. It just happened to me again. Extremely frustrating as I've got a load of motion sensors, wireless closure sensors on gates, and photobeams attached to i/o lincs. When this stuff goes down, I lose all of my external security. This never happened with the 99i but has been day 1 almost since I switched to the 994. BTW, an automatic detection and restore method would be really nice since this seems to be so common. I check the link count and it's 0. I then do a restore. Perhaps something like this could run on a set schedule and restore the lincs to the PLM and send an email.

I was getting excited until I saw that constraint. Being able to say "Alexa, turn on living room lights" would be really useful, but if it required adding a "tell ISY to" in the middle of that, it would pretty much kill it and wouldn't be worth while. It would just take too long to say it.

You misread my post. Check for at least one link. i.e. check that any links at all exist. Once you find the first link. Stop. Every time this problem has occurred it has wiped out all links, not just some. It won't take ten minutes to check for ONE link. That would be cheap and since this seems to be a wide spread issue, it would at least give some peace of mind to those suffering from this. I'm still convinced the 994i is wiping out the links. This never occurred before going from the 99 to 994 and then it started happening all the time and on both old PLM and new PLMs.

Is there any chance we could get a time based auditing function in the ISY to check the links. i.e. say I want to check them twice a day or every 12 hours and the ISY execute a link read to see if there is at least one link. If not, then you get notified that there's a problem.

Well that's unfortunate. I no longer have the old PLM. I still have the 99i. But I was convinced by folks on this forum in my previous thread last year that the old PLM was defective and that I needed to get a new one.

I first had this happen to me last year right after I upgraded to the 994. I discovered that every few weeks or so my wireless devices would all stop working. If I did a PLM restore, it would fix it for a while. I replaced the old PLM with a new dual band PLM. However, it started happening with that one too. I discovered that if I used the PLM links uploader menu on the ISY gui, when the wireless devices stopped working, the number of links was 0. It turns out I was just assuming it was the wireless devices because they would no longer send events. But it turns out nothing was sending events. I could still control hard wired devices through the ISY because the PLM will still respond to requests and send them on even if it doesn't have links. So now I've gone through 3 new PLMs all having the same problem. At seemingly random times, they essentially completely reset and have no links in the link table. I can't believe I've gotten 3 defective new dual band PLMs and now I doubt pretty much completely that the old PLM was bad as well. This is a very serious problem for me because I'm using a variety of motion sensors and photobeams (tied to i/o links) to greatly enhance the security around my home and when this happens, all I have left is the alarm system. I originally upgraded to the 994 because I added some of the new wireless devices only supported by the new 994, but I'm at the point now where I feel I may have to dump the new devices and pull out the old 99i and go back. I never had problems in years of use with the old ISY like I'm having now.

Got it. That makes perfect sense. Does this mean I need to walk around to every motion sensor, leak sensor, and door sensor and put them in programming mode one at a time? It's too bad smart home couldn't have had the wireless devices put themselves into programming mode when receiving an ack when they they send an event. Yes it wouldn't mean instant programming, but it would mean all you have to do is either wait or walk around and trigger motion or open doors to get them to have their updates written.