Jimbo.Automates

The Configuration Instructions which are shown on the configuration page describe what to do with your API Key. For #4, can you give a little more detai what you are trying to do? What is a UBIBOT External Probe? Does that show temperatures on the IoX? If you are trying to read that probes temperature from IFTTT, that is not currently supported as mentioned in the README -> Limitations

This is an internal error in the harmony client module I use, which is not really supported anymore, but I'll try to take a look and see if there is a way I can detect and restart when this happens. It'll be difficult since it's not repeatable, and I've never seen or heard if this before. Issue created https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/issues/38

Thanks @bigDvette I will try to pull this into production soon. Issue added: https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/issues/37

The Polyglot Version 3 Node Server for Kasa TP-Link 3.1.3 is released. See the Release Notes for all information. IMPORTANT: You must have the latest updates released 12/03/2023 for this to install. If you are not sure, please 'Update Modules' and reboot when complete before installing. Thanks to @Michel Kohanim for the fixes.

Energy values are updated on the long poll intervals only, there is no real time updating from Kasa.

Released 3.1.2 which backs up to a previous version of python-kasa library which is what causes all the install issues. Once those can be figured out I will release a new version.

No you shouldn't for UDM as long as you don't re-sync until it's all fixed. For the AC it's possible, I would not recommend deleting the node server since that can remove the nodes from any scenes, but your programs should be fine. Before ever deleting a node server, create a backup. Please select the "Kasa Controller" node, click "Update Profile", then close/open the AC and see if they look correct.

Please download log package and submit a ticket and include that zip file. Sent from my Pixel 8 Pro using Tapatalk

@bmercier updated a couple days ago and that has resolved my issue so far. Sent from my Pixel 8 Pro using Tapatalk

No worries. For others info the problem was solved in another thread. https://forum.universal-devices.com/topic/42457-elk-m1-with-eisy-and-alexa-voice-control/#comment-375488

Please run the reinstall all plugins from the PG3 UI. There have been a couple recent fixes to the PG3 Python interface recently that resolved similar issues. Sent from my Pixel 8 Pro using Tapatalk

@dantoronto what happened? I thought we had it working for you? Sent from my Pixel 8 Pro using Tapatalk

I like the Zooz, I also have Aeotec but Zooz seems better. Also,.FYI the Insteon leak sensors are still available and were on sale, I bought a couple more yesterday. Sent from my Pixel 8 Pro using Tapatalk

I'd try and upgrade modules again and after rebooting reinstall plugin. If still fails submit a ticket and include a new dowl log package. Sent from my Pixel 8 Pro using Tapatalk

Not when initially released, but dependencies were updated at some point which caused the problem for new installs or updating to the latest. Sent from my Pixel 8 Pro using Tapatalk

The install log shows: error: can't find Rust compiler So the last upgrade modules must not have completed.

Strange because it looks like install of plugin failed. Please download log package and PM to me. Sent from my Pixel 8 Pro using Tapatalk

Have you completed this update? This is needed for: 5. Added Rust to dev packages (needed for Kasa)

#1 do not open the node server configuration in the Admin Console, those settings are controlled by PG3, and modifying it will cause errors like you are seeing. Delete the node server from the PG3 UI, then install again. If you were charged twice, please submit a support ticket and @Michel Kohanim will take care of you. The old plug will likely work, the new ones will likely not work. But developers are trying to figure out how to make them work and progress is happening and looks to be close. This is mentioned in the README "This nodeserver relies on a mostly undocumented and unofficially supported local API which of course TP-Link could break at any time, and has in the past, but luckily others figure it out." Frustration will be reduced if you follow Installation instructions.

More information about what you did when you received this error would be helpful. Sent from my Pixel 8 Pro using Tapatalk

What Kasa devices do you have? Some of the newer devices are not yet supported because Kasa changed the unsupported API. Sent from my Pixel 8 Pro using Tapatalk

Yes I did. Good luck with Rachio. Sent from my Pixel 8 Pro using Tapatalk

Yeah! Glad it's all working. That is correct. and yes, if someone is able to get onto your LAN they can connect to the unsecure port, but they still need a user code to arm/disarm. I could allow connecting via the secure port, but then would have to store the username/password in PG3 which does not yet have a secure way to store the data. Yes, it's the same. and it really could be done either way, but most prefer to control it on the router side not on each individual device. The secure port still works same as before. You can also now use UD Mobile now to control it remotely My bad, yes it's M1XEP.

It's M1XEP When you say unchecked static, I assume you meant you checked "Assigned an IP address via DHCP"? When you say "Now ELK Won't connect to Network" how do you know? Do you mean you can't connect to the ELK? It likely went to a different IP address, confirm your reserved setting is correct on your router. I reviewed the log and it looks like the Elk library is having trouble with the host you entered, earlier you said it was "192.168.50.xx:2101" can you confirm that's exactly what it is? Then on the same page where you did Download Log Package, set the Log to "Debug + Modules" and restart the node server. After you figure out what is wrong with your IP reservation. BTW, I deleted your attached log package, there can be sanative info in those logs so you should PM it instead of attaching.

This should have been posted in the PG3 -> Elk forum, and is being discussed here: