sorka

Lots of good info. Question, I don't see magic home in the nodeserver list. Running v0.9.31.

So my problem is that when I was selecting the little right arrow for the source to assign to the variable, it was cycling between Number, Variable, and System. After restarting the UI, I now see a fourth option which is the device pulldown along with status. So with that I can do what I wanted.

Using either CAI 8 or Insteon thermostats. Same issue. There is no way to assign the temperature value from either of these to a variable.

Such a seemingly simple task that I can't figure out how to do. I need to activate a program when the difference between two temperature values exceeds a threshold...say greater than 10F difference. I can easily check a temperature value in an if statement that it is relative to some absolute value or even another variable.. If I could just assign a variable the value of the temperature sensor + an offset, then I'd be able to do it. So what's the trick? What am I missing to be able to do something so basic?

Just for reference, the z-wave module: https://www.amazon.com/Fibaro-Micro-Controller-Z-wave-Strips/dp/B00P1N68FW

Been waiting for Insteon to come out with a low voltage x 3 output device that could be attached to RGB controllers that have low volage RGB inputs but I haven't seen anything. Besides using an IR linc or something which I'd rather avoid doing, are there any hardwired solutions using either Insteon or z-wave that would allow me to control RGB strip lighting and set 0-255, 0-255,0-255 levels arbitrarily from scenes so I could create different scenes with specific RGB values?

If it was possible to do such a thing on Insteon devices without having to hold the button for 3 seconds, why wouldn't the ISY just do it automatically? It already knows when it needs to and for which devices so why not just have it do it as soon as a device reports in with a state change or heartbeat?

Oh, and none of these devices are part of any scenes. Just realized the scenes wouldn't work properly if you didn't update wireless devices part of scenes.

I'm doing my yearly replacement of my PLM...actually in this case it was last replaced in March. The last few times I've done this I've just simply not written updates to motion sensors. They continue to work fine. I tried it on the open close sensors and leak sensors and same thing. Everything works fine. Obviously this won't work on devices that the PLM needs to change the state on as the addresses would be different. The only consequence I can think of is if the PLM receives a message and then tries to respond. The response will go unheard. What's worse, one of my most recent water sensors is BEHIND a built in refrigerator IN a wall sitting on the wood stem on the floor of the wall interior. I recently had a frig water valve leak and it caused quite a mess because the water went where there wasn't a sensor. This was the ONLY water supply in the entire house that didn't have a leak sensor and is the ONE place where I needed it. It's a two hour job to pull the built 48" refrigerator back out just so I can hold the button for 3 seconds. I should have been smart and soldered leads on the board where the switch hooks up to create remotely located switch that I could get to.

Cool, is that a 5.x thing?

I'd like to post an http get to blue iris to activate camera setpoints based on sensor status. i.e. I zoom several cameras in on the mailbox when it's opened. I currently do this with HS2 but would like to dump it and move to something else that either integrates with the ISY or form the ISY directly. Does 5.x have any such facility?

Currently I'm using HS2 to speak various security and HA notifications on six zones inside and out. I'd like to dump HS2 but that means finding another solution that will work with airplay. Anyone else doing anything similar?

And since this is such a common problem, how come UDI hasn't added a schedulable PLM link audit check so that it can notify you when the links have disappeared or even do an a automatic restoral? They we I confrm it is I select "list links" and none come up. Why can't the ISY do that for me????

If that's the cause of all 4 of my PLMs going bad, then that is pretty sad.

Nothing like that even close. Why do you think line noise would cause the PLM to lose links? And why did this never happen with the 99i and the PLC?

This is already the case with everything else on that circuit and then the power strip is plugged into a filterlinc on top of that.

The motion sensors are not part of any others scenes. BTW, if I simply add the folder state condition to the a program in the folder such that: if ($alarmType is not 0) AND Control 'Motion Sense Garage Inside' is switched On it works just fine. It's only when the condition is on the folder that it doesn't. So my fix is to move the condition off the folder and copy it to each program in the folder but that's really dumb.

State. Already discussed earlier in this thread.

And support from the very beginning has insisted that it was the PLM. I never said I didn't contact support. I just haven't done it recently.

No. Those programs are triggered only from the motion sensor. Nor are the test programs I stick in this folder just to triage this triggered by anything other than the motion sensor.

That's nice if it doesn't need to be replaced to fix this issue but if it does, then I'm long out of warranty despite having the issue from the very beginning.

Updated to 4.5.1. Made no difference. Change to "AlarmType is 1" and set the state to 0. Folder still red. Programs still execute. Very frustrating. This is clearly just broken and nobody is relying on this parent folders like this. I can fix it by modifying every program to include the "AlarmType is not 0" and that works, but not when setting it as a condition in the root folder.

The 994 is the only thing that is in common. I never had this problem with the 99i. If it's the 994 it's well out of warranty although I've been experiencing this issue long before the warranty expired. I've said all along that I don't think this is a PLM issue.

Yup. Very odd. So I did that and it actually worked. Why???????

Not sure I understand the question. Each program in that folder triggers off an insteon motion sensor.