Jimbo.Automates

@William Olsen 3.8.0 Uploaded to the store with new light_method ELKALL which should work for what you want.

I don't. I could pull it out of git and release it but then you'd be stuck on an old version which would never get fixes or updates. I started looking at adding this back earlier today,.will try to work on it more this weekend if I have time. Sent from my Pixel 6 Pro using Tapatalk

I have asked Ecobee to allow the API to set Vacation mode but it hasn't happened yet. What I do is create my own "Comfort Setting" called "AwayExtended" or whatever you want to call it, then restart the node server and once it completes open the Admin console and your new comfort setting will be available. I prefer to have ISY control my vacation mode, when I arm my alarm in Vacation mode it sets the Ecobee as well.

The Polyglot Version 3 Ecobee Node server 3.1.5 is released to production. See the Release Notes for more information.

That's strange, the n002_e868e786c58b_2 looks to be a valid node, so not sure why it's not showing up. Can you delete it and type it in manually instead of being copied from the PG3 UI? @Michel Kohanim @bmercier or @Javi any other ideas?

The first attachment didn't come through?

That's very odd. Can you post a screenshot of the notification you receive?

What is your IoX, PG3, and notification node server versions? Sent from my Pixel 6 Pro using Tapatalk

I don't see how it could be an issue, we are just controlling a light that is defined in the ELK, but I'll like @Michel Kohanim give his opinion.

OK, understand now. What you want is currently not available, it was actually how it worked when I originally released, but nobody wanted it that way. It'll take some time, but I can add that as a different light_method.

Yes, I understand. But can you point out a ELK Light from your Olsen Lighting.pdf which matches an EXISTING node name in the ISY? That's how it works. You define a Light in the ELK which matches the node name of an existing light on the ISY. Very cool about the Morgan, we were on a Bali 46.

Sorry, I don't have time to sort thru the 2 lists, can you point out one ELK Light whose name matches a node name on the ISY that you expect to be linked together but is not? We are booking another sailing trip for next year already

Why are you looking for "light"? You configured the NS for ELKNAME mode, as the documentation mentions: This attempts to match the name of an ISY Node with the Name of an ELK Light node to control. The table on this page will show the matches. In other words if there is a "light" configured in your ELK, and the name of that light matches the name of a node on your ISY then you can control it from the ELK and status changes from the ISY will be updated on the ELK. What lights do you have configured in your ELK?

Yes, the XML is from your ISY which shows the node names that exist in the ISY so you can confirm if they march up with a light name on the Elk. Sent from my Pixel 6 Pro using Tapatalk

Yes, I know the link is bad, this is due to a recent change in PG3, you need to instead use http://localhost:8080/rest/nodes but change localhost to your ISY IP address. So device 123 does match between your ELK is ISY, what other light names configured in your ELK to you expect to match with an ISY name?

You aren't able to select Armed Status in UDM to show this? Sent from my Pixel 6 Pro using Tapatalk

Yes open your area node and set armed status. You can create a favorite to armed status to make it easier. Sent from my Pixel 6 Pro using Tapatalk

Yep,. sailing away. Back home Tuesday. Sent from my Pixel 6 Pro using Tapatalk

Yes I realize it's showing you the link to 127.0.0.1:8080. You need to change that to your IoX IP address. For some reason I can't download your PDF on my phone while on a catameran in the Caribbean, I'll have to look when at a computer at home. Sent from my Pixel 6 Pro using Tapatalk

Change 127.0.0.1 to the Polisy/eisy address . PG3 used to give us the real IP but not anymore I guess. Sent from my Pixel 6 Pro using Tapatalk

I've never seen this happen with the ELK NS. If you have the issue please download log package and PM it to me. I'll try to test when I am home from vacation. Sent from my Pixel 6 Pro using Tapatalk

Sorry, I can't do anything about the order of the list. That has also been reported to UDI.

Yes, as mentioned in doc https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#system-customizations "This feature allows sending messages defined in the Admin Console Configuration->Emails/Notifications->Customizations" The issue with it showing the ID in the Admin Console has been reported to @chris UDI and will hopefully be fixed in a future release of the Admin Console. BTW, you don't need a unique customization for each Leak Sensor, just create one and reference like the example in that section of the doc mentioned above.

Great, glad it's working. Sounds like I need to update my documentation? Sent from my Pixel 6 Pro using Tapatalk

Did you restart the nodeserver after adding the groups? Then once it fully completes the restart the open the admin console (if you already have it open, then close and reopen) Sent from my Pixel 6 Pro using Tapatalk