Jimbo.Automates

HomeKitHub 2.1.0 released for Standard and Professional: See CHANGELOG Please see OP for all the information on this Plugin.

This should be fixed in the latest release.

Do not change the "climateRef" only change the "Display name", if I could make it readonly I would, but not possible. I've confirmed over many restarts that display name doesn't get reset. Again, for new issues please create a new post. Also, read the notes about how comfort programs are now handled in the version I just released, I've given up trying to hack a way to deal with them due to HomeKit not supporting them.

PG3 Ecobee Node server 4.2.0 is released to production. See the README and CHANGELOG for more information. Please note the change to the order of Home/Away which will affect any programs referencing those. There is also a change to how all the other comfort modes are handled since homekit doesn't support all the modes. Please read the changelog and config doc, and don't complain to me since I have no control over how they are reported.

@bmercier, @Javi any feedback on the requests in this thread? More requests: When I click on an action, the Edit Action has a Copy Icon which appends a copy and closes the window. Instead can it just be an "Append" button on the bottom? This is useful when I have a similar action with a slight change to add. So I can make the change then click Append. With the current method I have to Copy then click on the new item to open it, edit it and save. If I try to navigate away from a modified program the Unsaved Actions modal options are Cancel & Discard. Add a Save button. When cursor is focused in the Programs the cursor up/down moves the highlight to a different program but doesn't select that program. In AC it would select the program and cursor left would collapse a folder and right would expand it. The "Program Selector" window always opens with every folder expanded, it would be nice to remember the previous state. Notification Editor needs ability to insert Variables etc like AC has.

Thank you, glad it's working. Benoit will look into fixing eisy-ui issues with the custom parameters not showing up pro next week.

The PG3 Plugin for Kasa TP-Link 3.3.37 is released. See the README and CHANGELOG for all information.

You are welcome. Released 3.3.37 which should handle auth failures better and resolve the query issue you saw https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/CHANGELOG.md

The latest version had many changes and likely better reporting of the issues, the only option is to stop trying to authenticate when it gets a failure, but it's always retried in case it was just an intermittent issue. I'll look at quieting it down. It's not Kasa, and I've said many times this plugin uses a reverse engineered method to communicate with Kasa devices. TP-LInk does not support anyone doing this. First section of the https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md mentions this. Personally I don't use Kasa devices for many things I care about, except their plug strips but I do my best to keep everything working with this plugin. The latest does use a newer version of the libraray, and I'm not sure why your queries are reporting errors. I'll review the log when I have some time.

Your AI should know that the authentication issues are a know problem since Kasa switched to a new method and the python-kasa library I use is working on support but it has not been released yet. I could fix the plugin to be less noisy about this if I find the time but hopefully the new library will be released soon.

That line means Ecobee is connected to the MQTT broker and has been saying hello, and the HomeKit hub has not answered. Please check: udi-poly-homekit-hub is running with mqtt_enable true, and its MQTT status is connected (hub GV1 = 2, bridge GV0 = 1). Both sides use the same broker. Ecobee hk_mqtt_host / hk_mqtt_port (normally port 1884) must be the broker the hub is using. hk_mqtt_hub_slug matches the hub mqtt_hub_slug (usually both default). A mismatch puts hello on a topic the hub never subscribes to. hk_mqtt_client_slug is udi-poly-ecobee unless they intentionally set a unique slug. The hub answers on that same slug. Restart the HomeKit Hub node server first, then Ecobee, if both look configured and the count is still climbing. Until that ack arrives, Ecobee will not load thermostats from the hub.

This looks like an eisy-ui plugin bug, or difference. I've reported it to UDI so we'll see what needs to be done. Please everyone, in the future if it's a new issue create a new post in this sub-forum. I can't keep track of every different issue in the same thread. Probably a different issue. Looks like it's having an issue talking to the HomeKitHub plugin.

The PG3 Plugin for Kasa TP-Link 3.3.36 is released. See the README and CHANGELOG for all information since 3.3.27.

Just pushed production 3.3.36 to fix this issue and it includes a bunch of changes that have been in beta for a while.

It should, but the bulb could be incorrectly identified. Please download log and PM it to me with a reference to this post.

Go to the Nodes page for the plugin and you should see the details? If not let me know. I can't look because I don't have Elk at my new home yet, and can't currently remote login to my lake house to review.

PG3 Airthings Consumer Plugin 1.3.2 released, see https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/production/CHANGELOG.md Make sure to upgrade before moving to eisy-ui plugins.

Another subtle difference with the new Plugins. Just uploaded 1.3.2 GitHubudi-poly-Airthings-Consumer/CHANGELOG.md at main · Univer...Polyglot V3 Node Server for Airthings Consumer API - UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer

I can't help if I don't have a log. PM or email it to me...

Hey Jeff, So I don't have wireless tags in my new home, I left them at my old home . I do have them in my lake house so I can migrate those when back on site, or I can install in PG3 here and then migrate and see what happens. But as always, if you have problems I can't debug without a log. If you try again please PM or email me the logs. Jim

I know your issue is related to using your own Developer Key which I'll try to look into soon. But for everyone else's info, I have migrated all of mine to Plugins and everything worked perfectly. But I am on the staging repo and don't recommend everyone use that but wait for eisy-ui 1.4.9 and PG3x 3.4.28 to be released to beta or production, although I'm not sure if that makes a difference.

Upgrade packages which has eisy-ui 1.4.8 logout of eisy-ui and back in and let me know if you still see that Internal Server error. If so you'll need to open a support ticket for them to review.

I migrated all my plugins on my production system from PG3 to Plugins and I had no issues. But I am on the staging repo which I don't recommend for everyone, and I'm not sure if that is the reason everything worked. I don't recommend switching to staging but once eisy-ui 1.4.9 and PG3x 3.4.28 are released to production or beta please reinstall and try again.

Also it's not able to set variable init values yet? Ah, I completely understand now! You are entirely correct: routine actions in NuCore (set_var) only update the current runtime value of a variable, not its stored persistent init value. Because NuCore's routine DSL does not have a built-in action to change a variable's init value on the fly, setting both the current value and the init value simultaneously from within the routine itself isn't supported by the routine syntax.

Can it be updated to allow this? I'd rather keep the template and just have it add new values. That's correct—I cannot directly edit or create new custom notification content templates in NuCore's system configuration, as those templates are managed globally rather than inside individual routine definitions. However, we can achieve what you want directly inside the ~Leak Sensor Battery Low routine by using a text-based notification or variable logging approach if needed, or by keeping it linked to the built-in templates I also found that it can't organize programs it creates by moving them into folders, and in eisy-ai it's very painful to move a bunch of programs.