Everything posted by Jimbo.Automates
-
Version 3.0.13 on store but labeled as 3.0.12
Looks good now. I hadn't announced this version yet since I am testing on my production system and wanted to make sure there were no issues first.
-
Red exclamation marks on the controller
Thanks for the log, this means there was an, but it's not being cleared. Issue entered: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/91
-
Red exclamation marks on the controller
Check the PG3 UI for an error. Download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk
-
How to import devices into ELRP using a node server
As mentioned in the GitHub issue I previously posted, there is no easy way for the node server to know what devices you want to import into the ELK. So I'm stuck until @Michel Kohanim or @Chris Jahn can offer suggestions, Sent from my Pixel 6 Pro using Tapatalk
-
Moved/renamed devices not getting renamed
Yes, this ability was only recently added to the PG3 API and I've been adding it to my node servers as I have time. I've created an issue for this one: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/14 It's not a problem to just rename them in the ISY.
-
Is there a limit on the number of messages that can be created?
There is a tiny little box to the right which you can click on to delete the custom data item, we need @bpwwer to fix PG3 so it shows an X icon there. Glad you figured it out, I have updated the documentation to show sending custom content with the "Send Sys Short with Params" method: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#custom-content-example
-
NS Kasa - Offline devices
It looks for devices coming back online since they can change IP address after a power outage. I don't think it hurts anything for it to always be looking for your unplugged devices, but I could add an option to turn it off but then you'll need to reserve IP address for Kasa devices.
-
WirelessTag node server installation with trial license fails
If you still have issues, @bpwwer will have to help let us know what that error means. Sent from my Pixel 6 Pro using Tapatalk
-
Is there a limit on the number of messages that can be created?
Thanks for the log, it looks like your message id after 144 is not defined? This is causing my code to die, which I need to fix. If you have many messages to notify when a device is turned on or off, they can all share the same custom content, I'll try to create an example when I have time. Edit: Issue created: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/43
-
Is there a limit on the number of messages that can be created?
Wow, that's a lot of messages! But no, there is no limit I am aware of. But you may have hit the maximum number of nodes? Dona download log package and PM it to me. I'm also curious why you need so many, you can do a lot with short custom content by embedding node or program names. Sent from my Pixel 6 Pro using Tapatalk
-
PG3 ELK node server 3.5.5 fails with error: cannot import name 'FunctionKeys'
Awesome, glad that fixed it, and you are welcome.
-
PG3 ELK node server 3.5.5 fails with error: cannot import name 'FunctionKeys'
Oh, that explains it. You need to do an "Upgrade Modules" to get the latest python: [admin@polisy-dev ~]$ python3 -V Python 3.9.14
-
PG3 ELK node server 3.5.5 fails with error: cannot import name 'FunctionKeys'
Try this: sudo -u polyglot bash ./install.sh
-
PG3 ELK node server 3.5.5 fails with error: cannot import name 'FunctionKeys'
That's odd, something must not have installed correctly, can you log into your polisy and run this? Replace the _4 with the slot number of the ELK node server: cd /var/polyglot/pg3/ns/*_4 sudo -u polyglot ./install.sh
-
How to import devices into ELRP using a node server
Issue added: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/90
-
ELK node server support for thermostats?
Yes, the NS supports temperature on Zones. But do you also have Thermostats on your ELK system? I try to document all drivers, instead of temp you need CLITEMP as listed in the doc: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#zone-node
-
How to import devices into ELRP using a node server
I can look into detecting if remote buttons are pushed, but the workaround sounds great. Sent from my Pixel 6 Pro using Tapatalk
-
How to import devices into ELRP using a node server
You can also put ELK NS nodes in an Insteon scene and use update scene programs to change for day and night modes. Sent from my Pixel 6 Pro using Tapatalk
-
Elk Node server compatible w/ expected Elk E27 Alarm engine?
There are also other alarm systems supported by node server written by @Goose66 and possibly others. Sent from my Pixel 6 Pro using Tapatalk
-
Elk Node server compatible w/ expected Elk E27 Alarm engine?
Sorry, I have no idea since I've not seen what the API will look like for the new system. Sent from my Pixel 6 Pro using Tapatalk
-
How to import devices into ELRP using a node server
That's correct as mentioned it's being worked out, although slowly since I've not had much free time lately. Sent from my Pixel 6 Pro using Tapatalk
-
How to import devices into ELRP using a node server
Methodology has not been completely worked out yet. https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/67 Just curious, what do you use this for?
-
Error When Opening Elk
Starting with 3.2 the NS only supported Polisy: https://forum.universal-devices.com/topic/35577-pg3-elk-node-server-327/#comment-332777 The _sys_notify_short is used for sending text to keypads. Are you saying UD Mobile could hide it? If so that would be fine. If from the NS itself that would take some work but could be done.
-
Will UD Mobile include ELK?
Yes of course Sent from my Pixel 6 Pro using Tapatalk
-
Will UD Mobile include ELK?
Do a sync in UD Mobile to your ISY and the nodes will show up. Sent from my Pixel 6 Pro using Tapatalk