landolfi

I am on Polisy 5.6.0. Not all are battery devices. And as I mentioned, some of them (like Aeotec Siren 6) are showing active ZW nodes as well as ZY nodes. The ZY nodes are all working, so that part's OK. I just can't get rid of the ZWs. What's odd is the Aeotec seemed to be a backbone of some of the routing to my garage with the Zooz, so I would have thought it would be a strong candidate to migrate correctly. I didn't see anything in the post-install instructions saying what to do about ZWs, and that would be consistent with the expectation that they should remain ZWs. Also, there is nothing in the post-install insructions about having to update Alexa, which would be consistent with not having to change device names from ZW. But that is what I had to do, Alexa had the ZW devices and thus the spokens no longer worked post-migration.

I migrated from Zooz to Zmatter and all went well, but I still have about 30 ZW nodes and the rest are ZY. Some of the ZW nodes report status and some seem to be dormant, but even the live ones have duplicate ZY nodes. Can I delete the ZW nodes and if so, how? I tried "Zwave/Remove Failed Node" but I get this error: I'm running Iox 5.6.0.

Just purchased a Yolink valve controller to irrigate my garden and in creating a daily timer to water the garden, I noticed the switch control commands (Open and Close) do not work from the nodeserver and therefore I can't control the valve. Open and Close commands do work from the Yolink app. The AC correctly reports state and I can set the off delay in a program, just not the open and close valve commands. There is an error in the NS log, which I've attached. YoLink_5-19-2023_33127-PM.zip

Just wanted to say thanks to the UD team for a painless migration experience from a Polisy IoX with Zooz dongle to ZMatter. The migration instructions in the wiki were comprehensive and easy to follow (despite my confusion several times about how I had opened the Eisy User Guide and what the heck happened to those migration instructions I was looking at). I was especially impressed that the node names were preserved, even for the devices that weren't automatically migrated, so I didn't have to change any programs. Once I restored the backup it took about an hour elapsed time to get all the unmigrated devices included, mostly because some of them are either hard to wake or very anxious to get back to sleep. Most of my battery devices didn't migrate and per the wiki that is expected. For anyone with Zooz devices that hasn't yet migrated, the trick seems to be keeping them awake during the "Synchronize/Update with Interview" process, particularly the ZSE 44, ZSE 40, and some of my open/close sensors. I found it took multiple attempts and frequent button pushes on the devices to keep them awake during the interview, and that anytime the interview duration countdown went quickly down, the interview failed. (I noticed later that I could have changed the interview duration, which might have been helpful). One helpful tip I learned after the fifth failed attempt to include a Kaipule ceiling motion sensor was to first start the interview, and only then wake the device up. A few suggestions I'm pretty sure have been mentioned elsewhere: 1) The X-Ray window at 1920x1080 is too large for my screen. Eventually I figured out I need to resize the window by dragging the right edge, and then the controls at the top appeared. 2) This might be a personal preference but I found the Zwave/Sync/Update with Interview cascading menu followed by a Yes click annoying, particularly when trying to start it with one hand and have the other hand ready to wake a battery device. I understand that the verification is there to make sure everyone knows the impact on scenes and the importance of waking devices, but how about a "Don't show this message again?" checkbox? 3) The interview failure message flashes so quickly I was puzzled why it said "successful" but didn't include the node. Eventually I looked at the event viewer and realized the message was saying it failed but showing the number of successful and unsuccessful attempts. If it is failing it would have been nice to see an info dialog showing the result, something like "Interview failed, node not added" rather than a message that disappears leaving me wondering.

Thanks Mr. Bill, for the as always excellent insight. The Marantz is invisible to ISY, but as you said, sending it an off is no problem unless I'm in the room. The notification isn't important, that was a debugging relic when the Marantz would occasionally accidentally on purpose get turned off because I had sat still for too long. My use case is to detect when the room hasn't seen motion for a while. I'm confused why detecting motion is better than not detecting any motion? It seems to me that either way the timer gets reset when motion is detected. But maybe you mean detecting motion means I don't have to wait some arbitrary amount of time to determine whether the room is unoccupied? I checked and the two motion sensors (one is an Aeotec multisensor and the other a Kaipule ix32 PIR ceiling motion sensor) both have a node "Basic Control". is that what you mean by control, and that gets set to 1 when motion is detected? The "Media Room Sensor" is a Yolink via node server and doesn't have a control node. Is "control" more reliable than motion detection?

Similar question here concerning the following program. In this case, am I correct that if motion occurs while THEN is running, the THEN execution is canceled and the IF is subsquently re-evaluated the next time all conditions are true? TVRoomEmpty - [ID 000E][Parent 0001] If 'Ceiling Motion Sensor' Status is Off And 'Wall Motion Sensor' Status is Off And 'Media Room Sensor' Motion State is No Motion Then Wait 1 hour and 30 minutes Resource 'MarantzOff' Send Notification to 'Bob' content 'TurnedOffAV' Else - No Actions - (To add one, press 'Action')

Are you using the Zmatter board (I assume so since you mention you used S2)? I have the Zooz stick with firmware 5.5.9 and two of them work reliably. In the past I've noticed these can take an hour or two to update properly after a firmware update, if this was all done recently.

It's an Ethernet connection because I had some infrequent but annoying issues with streaming over wifi. I love this receiver's features but not all of it is implemented well.

OK, will try that. Thanks!

Weeell, my excitement was short-lived. Looks like I am back to the REST API, the AVR Remote not only doesn't reliably control my Denon X1200W, it also seems to make it unresponsive to other devices controlling it, so I need to send commands on ad hoc basis. My question is: What are my options for running the REST API commands to set my state variables? Is there any way to do this from within the ISY IDE, or do all of the REST calls need to run outside ISY? My current sketchy plan is to use the network resources I already have with a REST routine that periodically sets the volume state variable in case the value was altered by another means (such as a remote key press).

Hi, I'm running PG3 3.120 and IoX 5.5.9, just installed AVRemote 2.05, which does exactly what I need for voice control of a non-Alexa Denon AV1200W. I'm noticing inconsistent command response, the properties seem to be read-only. The only thing I can get to work consistently is a report of current volume level. Ideally I'd like to be able to set volume level and volume up, but I get a response about every 3-4 tries in the UI, and a program I have to set volume (no conditions, just set volume in Then) doesn't work at all. I noticed the UI shows the Denon online but commands still don't work. I've tried both true and false for connect on demand, false seems to work better but not consistently. The Denon has a static IP and I have the node server config set for port 23. Any other settings I need on the receiver or on the ISY? I know this receiver can be weird if it thinks multiple devices are controlling it at once, so I've made sure to disconnect everything else that can control it. I can control the receiver from a web browser and from the iPhone app without any delay in response (in general, not simultaneously with the node server) but direct ISY control would be preferable. At least as it is I can sync my state variables with reality from the node server in case another control (a remote, iPhone app, or something else) changes the volume. Thanks in advance for any suggestions.

Yes, exactly, now I can set it directly. As well as get rid of all the network resources I had set up to change inputs, etc.

Looks like I may be able to do the whole thing using the AVR/Denon node server, which seems to be able to return the current volume setting. Thanks for the tip! I had installed the AVR node server before but never explored it until just now when I realized most of its properties get exposed only after an IoX restart.

The REST API! Sounds like a nice rabbit hole for me to fall into. Thanks, will check that topic in Search.

I have a volume control network resource set up that sets a state variable to control the volume of my Denon receiver. It works well with Alexa, provided Alexa responds, which she doesn't always do. So I also sometimes use an app to set the volume outside of IoP control, and then my state variable is out of sync with the current volume setting. Has anyone come up with a way to ensure IoP knows or can find out the current volume level setting, or do I just have to make sure I set volume from IoP always? I can't find a way to query and set volume level using IoP, though Denon supports returning the level via an IP command. Here's my current program: DenonChangeVolume - [ID 0014][Parent 0001] If $State_Denon.Master.Volume > $Int_AV_Denon.Zone1.Vol.Min And $State_Denon.Master.Volume < $Int_AV_Denon.Zone1.Vol.Max Then $Int_AV_Denon.Zone1.Vol.Current = $State_Denon.Master.Volume $State_Denon.Zone2.Volume = $State_Denon.Master.Volume Resource 'DenonSetVolume' Wait 1 second Resource 'DenonSetZ2Volume' Else - No Actions - (To add one, press 'Action')

Yes, in today's log it looks like the ZWave module that controls landscape lights (not controlled by a node server) failed to turn off at the exact time of this notification (involving a node server).

OK, thanks for the replies. I already have custom notifications set up in other programs, it was just laziness that I left the notification default in this case. But here's another topic for my best practices book. It seems a bit odd to me that Default just dumps errors unrelated to the devices of interest to a program, but that's just me. Any other day this notification is in fact "a schedule was met", which is why I got this notification at 0709 because Sunrise + 1 hour was true.

Thanks for moving. The actual text of the notification is in my original post. I would have posted the program text rahter than an image but it's so simple I didn't think it would need any modifcation.

I have this program checking a Yolink water sensor. I'm running ISY on Polisy firmware 5.5.9: Today I got this notification email: Monitor Pump Status 'Landscape Lights' ERR set to 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 at 2023/04/16 07:09:01 AM. ---------------------------------------- At: 2023/04/16 07:09:01 AM Program: Monitor Pump Status Device: Landscape Lights (ZW012_1) Action: ERR Value: 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Is this a bug? Landscape lights might not have been responding, but what does that have to do with the program above? In other words, is it normal to get a dump of non-responding device status in a notification when a device isn't responding for some reason, even if unrelated to the devices the program checks?

I got this message today from a program that monitors a Yolink leak sensor and since it looks odd I thought I'd report it here. The program sends an off command to a switch if the sensor is dry and also sends me an email notification, which is how I got this message: 'YoLinkSetup' Off set to 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000 at 2023/04/09 07:20:35 AM. Normally the program would say the destination switch name set to Off rather than "'YoLink Setup' Off", but the switch is offline. Could this be why?

I was thinking the same thing. It seems the leak sensor will be too sensitive to splashes and humidity. It's a 6x6 plastic box that the pump is in. And it may turn out that I'm overthinking this, because generally I want to simply be able to turn on the pump remotely when I see water collecting in my back yard. That is already working.

Thanks! This is very helpful. One thing I discovered by accident is that I really didn't need a program at all for this particular purpose, since it seems the wet sensor triggers the pump on but if I turn the pump off manually using the AC or UD Mobile, the sensor doesn't turn it back on because the sensor state (still Wet) hasn't changed.

Thanks for the detailed reply! Very useful stuff. And I solved the mystery of why the pump was never shutting off even though the water level had dropped by wiping off the leak sensor contacts. These things are apparently quite sensitive.

I have a program set to turn on a pump based on a Yolink water sensor reading. Since I'm new to the Yolink water sensor, I don't know how reliable it will be at detecting moisture, I'm not sure how reliably I have it set up to detect moisture, and the pump won't survive running completely dry, so I'd like to be able to toggle the program execution to limit when it runs to times when I can monitor it. I know I can disable the program but is there any way to detect that a button was clicked in the UI in either ISY admin or UD Mobile? Ideally the logic would be if the device is turned off outside the program, leave it turned off. I think I just explained it to myself that I should create another program that I could trigger from Alexa or using some other event to set a state variable that gets checked by the pump starter program. Or simpler yet, use some event to disable and enable the pump starter program.

Thanks. I did try both, but since my computer couldn't resolve the polisy host name using what it thought the IP was (i.e., the old IP for that host), it didn't work. I also tried what I usually do, IPaddress:3000 to try to get to PG3, which didn't work for the same reason. It was just a random event I guess with the second device grabbing the Polisy's IP. So all this is here in case it helps someone in the future.