landolfi

I'm not an expert by any means, but I have that sensor and some experience with programming. If you go to Programs tab/Details tab, click New Program, then under the heading "Add to Program", click Condition, then go down to Status, click your Zooz Multisensor, it will show you the various values the sensor collects and you can add the tests for those values you want (> < = not, etc.). When you have the condition you want, click "Add to If" at the bottom. Continue for all conditions you want in your program, then add the Actions you want in the Then section. When done, be sure to click the Save Changes button on the left side to save the program.

Not too preachy, in fact very helpful. Thanks!

So to be clear, the Yolink is online and recognizes motion events, but the Yolink Node server says it is online and does not recognize motion events after a certain undetermined period. For instance, I just got a notification of a motion event from Yolink but the Yolink Node server says there is no motion even if I click "Update Motion Status". It worked a few hours ago. Also, I think you probably know there is a typo in "Motoion State". UPDATE: I just got a "TCP response failed" error from ISY in response to clicking the update motion status button, in case that tells you anything.

So you're referring to the Yolink hub being online? If so, I know the issue isn't with the Yolink hub, because I get motion notifications from it and Alexa, just not from the Yolink node server.

Thanks. How do you check the router connection to see if it's there, do you run some sort of command line in a cron job or something similar?

Thanks. I assume there is no workaround in the meantime (e.g., use Ethernet instead of wifi)? It's probably a good thing until the dogs get used to hearing "Signed, Sealed, Delivered". They now know it's the mailman and one of them goes to the window to bark at him before he gets to our nextdoor neighbor's house.

Hi, First of all, thanks for developing this, now I can actually play music on my Sonos when the Yolink mailbox sensor activates. This may be the issue you are working on, but 24 hours ago the node server did not detect a motion event, so I restarted the Node server. Then it did detect it, but now it's back to not detecting again. If there is any log info I can provide that would help, glad to do it. I have a Yolink hub with firmware version 0323 connected via wifi and am running IoP with firmware 5.4.4. If it would help I could try connecting the hub to Ethernet.

Are you still looking for 500 series Zwave? I got everything migrated to Polisy.

How soon do you need it? I'm migrating an ISY to Polisy, but don't know yet when I'll be done. Could be as early as next week.

Thanks, I stand corrected on the board version and that removes some of the initial confusion for me. I was expecting considerably more range than I was getting from the ISY. So if I went full Polisy, it sounds like I could get 700 series range (with the Aeotec dongle). I have a Polisy that I'm hardly using so far, so that would be a good reason to finally migrate. I've updated the neighbors on these devices more than once in the past, but since I'm within the first week of the current physical network config, I'm inclined to leave it for a bit. I'll try clearing the java cache in the meantime and then retry the add closer to the ISY as you suggest should the problem persist. As for these particular devices, they are Minoston and I've seen reports elsewhere here on UD forums of defective Minoston devices. Unfortunately other affordable zwave plugs seem to be hard to find.

ISY with the new 700 zwave board.

Thanks! Are you getting these errors randomly or after sending a command? I noticed it is sometime unrelated to a command but most frequently happens right after the command.

ISY 5.3.4, 700 Zwave board here. I added an Aeotec Siren 6 and 2 700 series devices to improve Zwave network coverage and also replaced what I thought was the problematic Minoston plug with a 700 series Minoston plug. The Minoston 700 is within 5 feet of an Enbrighten wall switch and there are also 3 other Zwave devices in the garage, all of which work reliably and without errors. So at this point I don't think it's a question of range, although the siren is on the inside of the house, about 20 feet away from the Enbrighten and the other switches in the detached garage and there's a wifi router alongside some of the garage Zwave devices. I still get reliable, immediate responses to commands on the 700 series Minoston plug, but the occasional error in UD Mobile and ISY admin (image attached). I also get errors from another Minoston 500 series plug that is within 15 feet of a 700 series device here in the house. The Zwave network in its current form has been in place for about 6 days now. This occasional error only happens with the Minoston plugs. My question is, what should I be looking for in the log, or how else can I troubleshoot this? The only thing I see in device communication events for the Minoston devices causing trouble is Error 0. What is an error 0? And if you tell me not to worry about it, I won't, except why is it causing the iSY to throw a "Can't communicate with device" error?

Thanks very much. I had that query a long time ago before I used the ISY much and deleted it because it seemed unnecessary. This explains why it might be useful.

Thanks, Geddy. Yes, that makes sense. It also makes sense that most, no basically all of my devices just work fine and I also probably shouldn't be querying them over and over again and wondering why the queries sometimes time out, particularly after I have added a new device. So this is mainly because I have too much time for things to work properly without my intervention.

Thanks for the quick reply. Yes, the laptop running the admin console is on wifi. I'll check sleep settings and also try remote desktop with a wired PC running the console to see if that's the problem.

I have searched without success for a help topic concerning admin console timing out after some period of time, seems to be 30-60 minutes. When it does, sometimes it presents the ISY login dialog, and others I have to completely relaunch admin. The result after this happens several times is orphaned instances of admin console with dead buttons in the button bar. Not a showstopper but very annoying. I found an old post with a similar issue that suggested clearing the java cache, but that's greyed out because "Keep temporary files on my computer" is unchecked. Running 5.3.4 firmware and UI, Java 8 Update 333 (64-bit) on Windows 10.

Has anyone had trouble getting these devices to show status in the ISY? I can control them fine but the ISY always says "Request Failed" when I try to get status. I tried excluding and re-including without success. The nearest ISY-controlled zwave device is about 50 feet from the Minoston, so it could be that I just need to add a repeater, but it's puzzling to me that the device works but can't report status.

Just this message, but it seems irrelevant. I don't use any integer variables. The network resources in question are similar to the one in the ISY screenshot below, and in particular, the screenshot is of the DenonOn network resource that produced the error above.

When trying to run network resources that work fine on the ISY994i, I get the error "Node Object does not have nodeDefObject" in UDMobile (v0.7.6). I have tried syncing with ISY (v5.3.4) to resolve this without joy. Any other ideas?

Thanks, this worked for me too. I didn't realize I had to explcitly install PG3. The "PG2 (Deprecated)" suggests you don't need to do anything except not use it unless you have to, or at least that's what I thought. I'm hoping PG2 stays around for a while because stuff I have been using free on PG2 now costs $ on PG3. I'm also hoping the $ brings better functionality and support than I've experienced on some of the free things I've tried on PG2. My impression is that what was available in PG2 was mostly POCs.

I'm experiencing this too. From the ISY Finder. Just upgraded Polisy to 5.4.4. It appears to be using HTTPS on Polisy port 3000. Related: All my node servers are on PG2. Do I have to start over with PG3?

Yep, sure enough, that's what ISY support asked. But it seems to me that it's a little kludgy that ISY gives me the option to delete it but doesn't handle it gracefully.

Thanks, all. I'll open a ticket I guess. UI and firmware are both 5.3.4 with the same date/timestamp. It is not in a folder and if I try to move it to one, it does nothing. Java is v8 update 321. The scene only appears on the ISY, not in UD Mobile.