Jimbo.Automates

This is the new plugin interface which I've not tried yet. It looks like there is a problem since it says no configuration parameters. Download the log and PM it to me and link to this thread, I'll try to review during the week.

It's a few steps, can you describe which you have done and where the problem is? Make sure to reload the config page as mentioned in #5 (thats a PG3 issue I can't control) and lok under Custom Typed Configuration Parameters for your ecobee. Quick pairing (DISCOVER)Add HomeKit Hub from the PG3 store and start the Node Server. Put the accessory in HomeKit pairing mode (see vendor docs). Confirm it is unpaired from Apple Home and other controllers. IoT / separate VLAN (optional): only when accessories are not on the Polisy primary LAN — see Discovery networks (setup) below. Skip on typical single-LAN installs. On the HomeKit Hub controller node, run DISCOVER. Read Notices on the Node Server Configuration page (Custom section): HomeKit discover includes scan results and a Zeroconf / hub diagnostic summary when the new build is installed. Open Configuration → Custom Typed Configuration Parameters → HomeKit pairing slots. Reload the Configuration page in your browser if the new row does not appear yet (the table refresh button alone may not be enough). Find the row for your device (id and name are filled in by DISCOVER). In HomeKit pairing code (hap_pin), enter the 8-digit code currently shown on the accessory while it is in pairing mode (12345678 or 123-45-678 — either format works). Save. Wait for pairing to finish. A Paired HomeKit device child node should appear; ST should show paired/connected. Check PG3 Notices or logs/debug.log if pairing fails. Order matters: run DISCOVER before entering hap_pin so id/name are prefilled. If you already typed a PIN, clear it, run DISCOVER with the device in pairing mode, then re-enter the current code.

Did you follow the quick start instructions? You have to enter that code in the Homekit hub config as instructed. GitHubudi-poly-ecobee/CONFIG.md at master · UniversalDevicesInc...Contribute to UniversalDevicesInc-PG3/udi-poly-ecobee development by creating an account on GitHub.

Discussing on the issue: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/27

@bmercier, @Javi Is this an issue with plugin configuration, the migration or eisy-ui?

@DNewkirk Thanks for the detailed email, and sorry for the delay. Issues should be fixed in 2.0.20 CHANGELOG

HomeKitHub 2.0.19 released for Standard and Professional: CONFIG.md Please see OP for all the information on this Plugin.

Hopefully this will now work with 2.0.19 which will be released soon.

Should be fixed in HomeKitHub 2.0.18 which will be released soon

PG3 Ecobee Node server 4.1.11 is released to production. See the README and CHANGELOG for more information.

@photogeek54 Update to 4.1.11 and confirm @Cosmin Munteanu Update to 4.1.11 and confirm And everyone, please create a new thread if its a new issue instead of posting on this one.

Please restart the plugin, let it run for an hour or so then go to the plugin log page and "Download Log Package" and email that file to me at jimbo.automates@gmail.com with a reference to this forum topic.

Try to pair one of them, then go to the plugin log page and download log package end email that to me with info about the thermostat you are trying to pair, and reference this post so I remember what it's about.

This is the first production release of the Konnected Standard Production edition. Currently only supports the Konnected BLAQ. I will add support for the White sometime in the near future. See README, CHANGELOG and CONFIGfor more information. If you have issues or questions create a new post in this sub-forum. But if it's a bug please enter it at Konnected Plugin Issues so I can track it better, and if it has been discussed in the forum include a link to the post.

Yes, that's what is detailed in the issue link Need to ignore this, AT is the command code for an Alarm Reporting / Ethernet Test Command. It is a system keepalive or signaling message—frequently sent when the ELK panel or its M1XEP ethernet module runs an internal network/IP pathway test. https://www.scribd.com/document/508689172/Elk-m1-Rs232-Protocol-Ver-1-84