Jimbo.Automates

@apostolakisl Thanks for the Log Package. Issue is fixed in 3.5.4. Everyone using ELK Node server should send yourself a notification when 'Node server Error' > 0, the you can send the ERR driver value to see the error. Then download log package as soon as you can and PM it to me. I use the program and notice shown in the attached pics.

Please download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

Ok, finally found someone [emoji16] Are you using ELK node server now? Sent from my Pixel 6 Pro using Tapatalk

I assumed that was the case for most, but wanted to gauge the need. Sent from my Pixel 6 Pro using Tapatalk

Is there anyone with ELK that would like the node server to support thermostats connected to your ELK? It's on my list, but I don't rember anyone asking for it yet https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/50

Either way will work. Sent from my Pixel 6 Pro using Tapatalk

How to handle lighting is still under discussion between @Michel Kohanim and myself. I didn't realize if you imported all from ISY that it would then make them show up. I guess I need to add a configuration option in what lights to import. If you delete on the nodes tab they will come back on restart. So not much you can do besides delete them all from the ELK, setting the show option may work but I'm not sure. I'd need to test that when I have time later this week. Sent from my Pixel 6 Pro using Tapatalk

https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#isy-portal

This is a "Trouble" message, honestly I'm not sure what it means. I'll try to re-read the ELK docs to see if I can find what it means.

PG3 ELK Node Server 3.5.3. released See the README

This is fixed in 3.5.3, it has been broken since version 3.4.1.

@wmcneil Why can't you trigger a program based on Status change? That should work fine. Adding Control is not really possible with this type of Driver since it's not a simple On/Off value.

The problem is the Python library this Node server uses to interface to the ELK mad non backwards compatible enhancements. I've release 0.5.18 which should fix this issue. But, I'm not sure if the update will force a downgrade of that library. I no longer run the PG2 version so I am not able to confirm. But give it a try, otherwise you can manually install the older version. Please PM me the log instead of posting it here if you still have issues.

Issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/89 Sent from my Pixel 6 Pro using Tapatalk

I actually noticed this on the notifications I send while I'm away. I will try to take a look when I return home this weekend. Sent from my Pixel 6 Pro using Tapatalk

I reopened the issue and will confirm and look into it when I get time.

Everything in the ELK nodes is available in UD Mobile Sent from my Pixel 6 Pro using Tapatalk

Everything should be available for notifications. Some examples are provided in the doc: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md

If there are missing features you need that are not listed here https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues then please add them.

This issue has been discussed here: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/13#issuecomment-1193197934 Please comment there if the solution doesn't work for you.

Yes, that all looks good. I wonder if it's an iOS issue? I'm on Android. Sent from my Pixel 6 Pro using Tapatalk

What does your network resource look like? Sent from my Pixel 6 Pro using Tapatalk

Strange, it works fine for me, even using a custom sound. Mine barks every time the doggy door opens. Post a screen shot of how you are using it.

@Javi the INIT editor solved my issue with non dimmable KPL, thanks! Sent from my Pixel 6 Pro using Tapatalk

Now the very odd thing is back on the LAN and it works just fine. Very strange because now I see the little spinning icon for a split second, where before that was not happening.