landolfi

Somehow during the power outage the IP address of Polisy/IoP got reset, I thought I had set it to manual but my router or Polisy or both forgot that. I looked in the PG3 log and Yolink was trying to connect to the old IP. I changed to the new IP in PG3 and now it works. This may make sense to you, but the strange thing to me was that my other node servers were working. Or is there a best practice for Polisy/IoP addressing that I should be following?

I cleared cache and restarted IoP and AC. Still no status for Yolink Setup and no response to events. I also restarted Yolink just to be sure.

Attached. YoLink_9-23-2022_122800_PM.zip

I rebooted. Now the node server shows as connected. It takes a while for the node server to make the nodes on the IoP active, right? It's been about 5 minutes and I don't see any node status on Yolink Setup or either of the other nodes yet.

Tried reinstalling, no joy.

It seems to me it was working fine yesterday after the power outage but before the 3.1.10 update. I also noticed when I start or restart the Yolink node server, the uptime refreshes to what it was when the server originally started as if Yolink knows it’s been running all along and there’s a disconnect between Yolink and PG3.

I had a power outage here yesterday that took everything offline. I also upgraded PG3 to 3.1.10. Running Yolink 0.5.5, the server won't keep running, it starts/restarts but then almost right away goes to "Not Running". Log attached. Could this be related to the PG3 update? Yolink router accurately shows state of all devices. Does secret key/other Yolink parameters change when the router restarts? YoLink_9-22-2022_80312_PM.zip

I was about to agree about the delay, but apparently the 0.5.1 update happened for me automatically, and I can confirm that where there was previously a delay, the ISY response is now immediate.

I just checked too and don't see it. Aren't node servers supposed to automatically refresh if you stop and restart them? Or will this version be a completely different entry in the node server catalog like last time?

Great news! I have email alerts set for Yolink in a room with two other redundant non-Yolink sensors so I can see whether all are responding to motion or all except the Yolink.

In my case I was running ISY 5.3.4 and adding A10/X10 was available in the Link Management menu (still there on IoP 5.4.4 as "New Insteon/A10/X10 Device"). It added the device to the tree on ISY, but not on Polisy, so it could be the menu item is just misnamed and the A10/X10 functionality to add to tree deprecated. In case you are wondering why I'd want to add it to the tree, it was to make setting it up for Alexa spoken a step or two simpler since it could be treated as a device rather than a program.

FWIW, it's been working for me for almost 4 days. That has never happened before.

I am using the latest version of the Yolink Node server (0.4.4) and it appears to now be working consistently for me, at least so far. Thanks for the update!

Sorry for the delay in responding, I thought my notifications were on but they were not. REST is basically specifying an HTTP command with parameters, and there are numerous examples once you know what the allowed parameters are. The wiki is the best doc I know of: https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface But I also noticed just now there is someone asking about writing the sensor values from an Aeotec sensor to a log file, so you might want to keep an eye on this one: When it comes to the ZSE40, I conclude from my experience that it's important to keep it awake manually during inclusion and not implement it too far from the hub.

Will post when I hear back, and thanks for moving to the right place, it's still confusing to me where the best place to put some of these questions is. As @MrBill pointed out, I was trying to use an ISY solution on Polisy thinking it was worth a try :).

Thanks! I forgot about this. The weird thing is, adding the device as if it was an Insteon device worked for me on ISY and the option is there to do it on Polisy too. But ultimately it doesn't matter as long as I can control the device.

I'm getting this same error on Polisy 5.4.4 when trying to back up, except the filename is: ./FILES/CONF/frontend.pwd I found a post on this error on ISY backup mentioning a remedy is to use the RF command with the specified filename, but when I do that on Polisy, it says --bash: RF: command not found ?

Thanks. I already have a single migrated from ISY X10 device that works fine, but the issue is that I am trying to add a new X10 device and not getting an error message but also not getting any result. The quoted post mentions trying a different outlet, I have already tried that without success. I just need to get the Polisy to add the X10 module and I'm pretty sure the rest will be fine.

I was searching for a LampLinc and instead thought I'd just use an old X10 Lamp Module I found first. But when I attempt to add it to ISY on Polisy, I am able to add a new Insteon/X10 device and specify generic X10 as the device type to add, but Polisy just takes all the info I put in and the dialog disappears, and no entry ever appears in the device tree. Does this mean that Polisy only supports migrated X10 devices and not new ones?

There's another Zooz alternative, the ZSE40 700: https://www.thesmartesthouse.com/products/zooz-z-wave-plus-4-in-1-sensor-zse40

I see what you're after. If I recall correctly there's a way to make REST calls to the ISY, and I would think that would include queries like the one you're talking about. I don't know about you, but I have found this sensor to work well most of the time but occasionally it gets "stuck". I think in my case this may be because it's fairly remote from my hub, so I've taken some measures to improve the mesh.

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.