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

It is benign, you can ignore. I created a issue: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/120

Ok, I was confused because you said "fan state is on, but the program rarely is triggered". What do you mean by "same temperature"? I thought this was about fan state? If AC is not showing proper temperature, fan state or ... The please confirm you have checked the Healthy Hub Checklist

The HomeKitHub implementation was targeted to get Ecobee Thermostats working again since Ecobee removed access to their API. But the intent is to support other devices as well. Please restart the plugin then wait a few minutes, then go to the Plugin's Log page and click "Download Log Package" then email that to me at JimBo.Automates@gmail.com and reference this thread.

Sorry I am not sure, but I would assume so. But the handling of comfort settings with the HomeKit method is not as nice as the original API, but nothing I can do about that.

If AC is showing proper status then it sounds like a programming or notification issue?

Please retry the pairing then download log package and email that to me Jimbo.Automates@gmail.com and let me know the IP address of the thermostat.

Thanks @bmercier So for those having the issue you will have to delete and reinstall, sorry about that but we had to change the name of the plugin and early adopters got bit.

I have two Chamberlin LiftMaster side mount openers which are great, so quiet, and the work perfectly with Konnected BLAQ. I'll be releasing the plugin for these very soon.

Let try to get you upgraded to the latest and see if that solves the issue, hard to debug an old version. You may have to repurchase and ask for a refund, hopefully Michele or Benoit will respond to the other post. Again, sorry for the delay, for some reason I'm not receiving notifications for this forum...

Sorry for the delay, didn't get a notice that I was mentioned. @Michel Kohanim & @bmercier , This was due to changing the plugin name after it was released. Do these guys have to repurchase and ask for a refund?