Ok first. thank you for your video! QQ - So nothing is showing up in my HA automatically to configure the ecobee...Do I need to add the ecobee to the homekit on an iOS device first? From there, do I need to enable any settings within the iOS HA for this to be discoverable within HA?
Yes, add it to HomeKit and then delete it from HomeKit. This will add it to your WiFi, and it will stay on your WiFi as long as you don’t have Eero WiFi with HomeKit enabled or something similar. Once it is on your WiFi and disconnected from HomeKit, you should be able to connect it with the Home Assistant “HomeKit Device” integration. Let me know if you have any questions.
@@JoshsSmartHome Thank you for your reply. Unfortunately, your suggestions were good and probably will work for most. For me, I have a Pfsense router and I believe the issue was that I needed to allow mDNS to allow communication on different vlans. To do this, I needed to install the package, Avahi, select the vlans, then enable reflection. I also turned off any IGMP Snooping on Switches and AP's. I think what eventually did it was the the Avahi part of it on my router. Thanks again.
I’m sorry my response wasn’t your solution. You have a more complex setup than most people, with the vlan. I’m glad you were able to get it working and I hope your response helps others. Thanks for sharing!
I had a slightly similar issue. Turns out the auto-discovery doesn't work well with a containerized instance of HA when the network type is something other than "host". Might need to look into avahi so I can keep my IOT stuff isolated
It would be nice to be able to add to Home Assistant for the non Apple users but Ecobee wont give up an API key so I just got rid of my ecobee and went back to Honeywell which I could incorporate without an issue. I can not recommend companies that do not allow you to incorporate in Home Assistant when you spent a ton of cash on their product. You own it you should be allowed to do what you want. Don't need ecobee as their are plenty of companies that love to work with people in the smart home environment.
I agree that they should open things up for Home Assistant users to allow alternate integration. My Honeywell thermostat was a cloud integration that had problems sometimes and we all know that cloud integrations are far worse long term than local integrations.
Only if you are an Apple user the rest of us ecobee could care less about. I just replaced my ecobee with a Home Assistant thermostat which has no problem giving up the info needed.
I don’t actually use HomeKit for anything other than the initial connection to WiFi. We have an AppleTV 4K which is the best streaming box out there which acts as a hub and allows initial setup, after that, it’s 100% Home Assistant and doesn’t actually route through Apple Home.
What thermostat do you use?
Ok first. thank you for your video! QQ - So nothing is showing up in my HA automatically to configure the ecobee...Do I need to add the ecobee to the homekit on an iOS device first? From there, do I need to enable any settings within the iOS HA for this to be discoverable within HA?
Yes, add it to HomeKit and then delete it from HomeKit. This will add it to your WiFi, and it will stay on your WiFi as long as you don’t have Eero WiFi with HomeKit enabled or something similar. Once it is on your WiFi and disconnected from HomeKit, you should be able to connect it with the Home Assistant “HomeKit Device” integration. Let me know if you have any questions.
@@JoshsSmartHome Thank you for your reply. Unfortunately, your suggestions were good and probably will work for most. For me, I have a Pfsense router and I believe the issue was that I needed to allow mDNS to allow communication on different vlans. To do this, I needed to install the package, Avahi, select the vlans, then enable reflection. I also turned off any IGMP Snooping on Switches and AP's. I think what eventually did it was the the Avahi part of it on my router. Thanks again.
I’m sorry my response wasn’t your solution. You have a more complex setup than most people, with the vlan. I’m glad you were able to get it working and I hope your response helps others. Thanks for sharing!
@@JoshsSmartHome I appreciate your willingness to help. Thank you. I hope my response finds someone who is having similar issues.
I had a slightly similar issue. Turns out the auto-discovery doesn't work well with a containerized instance of HA when the network type is something other than
"host". Might need to look into avahi so I can keep my IOT stuff isolated
It would be nice to be able to add to Home Assistant for the non Apple users but Ecobee wont give up an API key so I just got rid of my ecobee and went back to Honeywell which I could incorporate without an issue. I can not recommend companies that do not allow you to incorporate in Home Assistant when you spent a ton of cash on their product. You own it you should be allowed to do what you want. Don't need ecobee as their are plenty of companies that love to work with people in the smart home environment.
I agree that they should open things up for Home Assistant users to allow alternate integration. My Honeywell thermostat was a cloud integration that had problems sometimes and we all know that cloud integrations are far worse long term than local integrations.
Only if you are an Apple user the rest of us ecobee could care less about. I just replaced my ecobee with a Home Assistant thermostat which has no problem giving up the info needed.
I don’t actually use HomeKit for anything other than the initial connection to WiFi. We have an AppleTV 4K which is the best streaming box out there which acts as a hub and allows initial setup, after that, it’s 100% Home Assistant and doesn’t actually route through Apple Home.