oberkc

I can't say much regarding mobilinc app. I recall that there were different benefits to each, but don't remember exactly what those benefits were. It seems possible to me that this is contributing to some problems, but I perceive that the Polisy/ISY interface is direct over your LAN and I would not expect a portal connection to interfere with the communication between the two devices.

One thing I don't see mentioned is the possibility that your ISY has a new IP address (from power outages, or rebooting of the router for whatever reason). Do you have a static address configured in your router? If the address has changed and the polisy is looking for the original address...well...this probably won't work out. I suggest double-checking the ISY address and seeing if it matches the address configured in the Polisy settings.

Did you ever use network resources to control Hue lights? Is it possible this program is calling up a network resource?

I have never had a mismatch of ISY versus UI. Every time I have upgraded, the UI followed with the rest of the system. I do not believe that there is a separate upgrade process for the UI versus the rest of the operating system. Given this, I can offer a couple of thoughts: - You could try the update again (not sure about the risk) - make sure you are using the correct launcher. Instructions say to use: http://your.isy.ip.address/admin.jnlp - clear your Java cache

On a slightly related topic...we have had a couple of windy days lately, causing some momentary power outages. After each outage, I notice that my hue lights are no longer controllable via ISY and the polisy says it is not connected to the ISY. I am currently operating under the theory that the polisy boots up faster than does the ISY and, during power outages (and, perhaps, purposely unplugging both) the polisy may be looking for the ISY before the ISY is online. Resetting the connection, or individual node servers, seems to solve these problems. I expect that unplugging the polisy would work as well, but not if you simultaneously unplug the ISY. Both my ISY and Polisy are on their own UPS now.

No. "AND" takes a natural priority over "OR". The parentheses simply duplicate the natural hierchy of Boolean logic. If, for example, switch1 is toggled on, the individual condition "switch1 is controlled on and switch1 is not controlled off" would be true, and the entire condition would also be true.

From a pure logic statement, I don't believe adding the parentheses changes the logical outcome.

Can you see any relationship between when you program does not work and when the washing machine is running? Given the critical nature of the PLM, I tend to like having it on its own circuit or having anything else on that circuit filtered. Regardless, it sounds as if you are having intermittent communication problems and you need to identify the source.

Even if your primary device is not showing status change, it may be worth trying something... For the zwave device in question, right-click>>z-wave>>>add/refresh button press node. This might add an additional node for that device that can be used in programs to trigger things. Give it a shot.

Sorry for the misdirection, @phatmatt. Thanks to lilyoyo for getting it right.

I had very similar experience...updated board, updated firmware. Switches that once reported status no longer do so. It is, indeed, my understanding that this is a UD issue and that there is a fix coming.

There are probably opportunities to use scenes here, but below is a programmatic approach. I made the assumption that there is no harm in turning off switches that were already off. if status switch1 is off or status switch2 is off or status switch3 is off or.... then turn off switch1 turn off switch2 turn off switch3 turn off....

I, too, have had a difficult time recently with Z-wave. It got worse when I upgraded to software version 5.2, along with replacing z-wave card with newer version. Switches that used to update status no longer did so. In some cases, I could partly resolve the problems by removing the z-wave device, resetting it, and adding it back. In one case, I replaced it with a new one. In the end, I got a response from the company that told us that these problems were going to be resolved in a software update. This experience would only be relevant to you if you are on 5.2 firmware.

So...it looks like it last ran today, and ran TRUE, as expected. Given this, I expect that it runs consistently every day at sunset. I would focus on comm problems. Do all the lights come on when it works? Do all the lights not come on when it does "not work", such as yesterday? Your PLM....is it located on a circuit with lots of other electronic devices? Computers? Printers? Routers? Chargers? Power supplies? UPS?

After adding the parentheses, you will likely need to move these to the proper location in the program.

Even if an extension cord solved the problem for now, I would still get a filter. This printer is now a known problem for insteon, and it has been my experience that interference can be cumulative. You don't want the occasion of plugging a charger into a wall outlet somewhere causing problems because your communication environment is marginal (due to a printer). I assume, also that you have computer/router/switch/UPS/etc types of devices at your house. Plug them all, along with the printer, into the filterlinc, if practical.

You will probably need some parentheses in your condition. Add them ahead of the first line and after the third.

I am assuming you are using insteon devices. For the bathroom, it sounds as you want motion detection to turn on light automatically, and off again in 5 minutes, when walking into a dark room. Additionally, you want a manual control of the light to disable the motion response, but the lights to automatically turn off in an hour when manually turned on. (I will not address the risk of someone walking into a fully-lit bathroom at minute 59 and the reaction when the lights go out at minute 60). You could use scenes and MS settings for some of this, but I will address entirely from programs, assuming there are no scenes involved. Forgive the inexact wording of the program language: Program 1 if control motion sensor is on then turn on light wait five minutes turn off light Program 2 if control light switch is turn on And control light switch is not turned off then disable program 1 wait one hour turn off light swith enable program 1 else enable program 1 For the driveway program, you do not state what you want to happen, if anything, when driveway motion is triggered and it is not late at night, so I will assume nothing. . Program 1: if control driveway motion sensor is triggered and time is from late at night to not late at night then run program 2 (then path) program 2: if nothing then enable program3 wait thirty seconds disable program3 Program 3: if front door is triggered then turn on hallway light wait 2 minutes turn off hallway light

This might work as well if you rely exclusively on programs, but for those who use scenes extensively, it may fall a little short. I have used the "replace device" function only a couple of times, but it has seemed to work for me. I would rather use this than manually delete the old device from the existing scenes, and manually adding the new device to those same scenes.

I look forward to seeing whether this update solves the problems that I am having.

I don't know about most people, but I have posted more than a couple of times that my z-wave devices do not respond to "control" conditions, as well as opened a ticket with UDI about a z-wave device and made such a point. If this response was ever given, I have completely missed it. I consider myself mostly unknowledgeable on things Z-wave, including nodes, associations, groups, and whatever else applies. I have, simply, treated z-wave devices as I would have insteon and been less than fully satisfied with the results. Along with lack of control conditions, neither could I successfully use them as a scene controller. FYI...I followed your solution and, yes, I seem now to be able to use a z-wave device as part of a control condition in a program. I am still investigating whether I can use it as a scene controller. Edit update...So, the newly-added custom button press node sorta acts as a scene controller. I added it to a scene that includes a micro-module and a keypad button. The micro module responds to the z-wave node command, but the keypad button does not. Interestingly, the node does not act as a scene responder, so I must also keep the primary z-wave node/device in the scene, as well. Still not quite right, in my view.

Unless the program has changed, and assuming that it worked before, the only things I can imagine are: - time (or sunset location) on ISY has gotten out of sync - device failure - something unique to sunset that is now causing communication problems Yes, please post the program. Also, check the program status to see when it has last run, and whether it ran TRUE or FALSE. Was the last run time the most recent sunset? No, I would not expect comms problems to a single device to affect all other devices.

I have non-toggle off buttons that I turn on with a program. As far as I understand, the non-toggle mode is only applicable when physically pressed. Otherwise, such buttons can be controlled remotely as can any other button. I wonder if a longer wait would have worked.

And you came to understand that how? (I did not see this stated anywhere. Edit: never mind. I now see this.) This sounds correct to me. Like lilyoyo1, I would convert it back to 6-button and link the primary node to your lamplinc. I see nothing in your stated desires that makes me think this is not the optimum solution. I think non-toggle OFF mode has been eliminated from some of the newer keypads. Also, I am not sure that I am following that last sentence. Regardless, if you insist upon keeping it in eight-button mode for reasons that I am not fathoming, I do not believe you would require non-toggle-off mode. Buttons A, B, G, and H should all be in non-toggle-ON mode. The lamplinc response levels for buttons A and B would be whatever brightness constitutes ON. The response levels for buttons G and H would be zero. Also, you would need to determine why your programs are not working. I offered some suggestions and questions earlier, but you did not answer them.

I was wondering the same thing as lilyoyo1. To attempt to answer your question...I, too, am a little puzzled why this would not work. Are your keypad buttons in non-toggle mode? If this were me, I would attempt to isolate the problem. If you manually run the program (THEN and ELSE path) does the keypad respond as expected? If you toggle the buttons, does the ISY reflect the correct status for "master bedroom nightstand"? Is your program disabled?