Initial Setup / Connection to Home Assistant

Smart Home Integrations Home Assistant
, ,
1

This seems so easy, but is kicking my butt.

I have just purchased a Konnected Pro. I am running the ESP ethernet firmware. I can see the board in ESP home. I can communicate with it without issue there. In the konnected.yaml: (Default conf / but calling out a few things)
I have the ethernet type of RTL8201
Under Ethernet I have have manual IP conf, and it is on the same subnet, etc. There is no issue there.
I have an entry for api: (with encryption, key, and a non-standard port)
and entries for logger: / ota: / and webserver

The board shows online in the esphome web UI.

I know there have been many changes and I am getting confused where the old intergration vs. the new ESP versions go.

I see entities for my sensors etc. in HA. I do see an entry for alarm.control.panel but the only entity is for my wireless doorbell. I am not able to find a way to control my Konnected Alarm panel.

I thought I may be still needing the konnected.io intergration but when I enter the IP address and port I get a failed to connect and the log shows an entry like:

Exception trying to get panel status: 400, message=“Expected HTXX/:\n\n b’\x01’\n ^”, url=‘htXX://xxx.xxx.xxx.xxx:x/status’ (where X is the expected IP and port why is there only one / after http? )
Exception trying to get panel status: Cannot connect to host konnected:23625 ssl:default [DNS server returned answer with no data]

If I try to go to mykonnectIP:myport/status I am not able to connect. I see the port as active when the config loads and it shows as open in NMAP. I did try to hit it once with konnect (it does resolve to the correct IP. - and I believe I have IP v6 turned off in the HA setup. - most of my important devices are static v4.)

so my questions are:

  1. Do I still need the konnect.io integration with the ESP firmware and having it online there?
  2. If yes, Is there something needed in the konnect.yaml file that’s missing in order for me to connect? (it did ask me for the enc key and it was correct)
  3. Is this a DNS/mDNS issue and can I flush it or correct it?
  4. I’m missing something - probably simple. What’s the sauce?

tyia.

j

2
  1. No, you don’t need the deprecated konnected HA integration. On the newer firmware platform, the device connects to HA using the built-in ESPHome integration.
  2. No, it should connect to HA automatically out-of-the-box. If you are managing your own firmware via “ESPHome Builder” then ESPHome builder will automatically create an encryption key for you.
  3. Nope, shouldn’t be. If the device is online simply go to http://DEVICE_IP to see its internal web page.

The default/stock configuration just gives you 12 default zones labeled “Zone 1” thru “Zone 12”, two Alarm outputs generically named, and one buzzer output. If you want to customize the zones/names/types then you can either use the Konnected app to customize or if you want to self-manage your firmware you can edit the configuration in ESPHome builder.

To enable the alarm_control_panel.konnected_alarm entity you need to enable the “Standalone Alarm Panel” feature. This is easily done in the Konnected app, or if you’re the DIY type, see: Alarm Control Panel Component — ESPHome

3

Nate,

Thank you. Your response was a great help. I am rocking and rolling now. If there is any suggestion, it would be that some things are not 100% clear on the pre/post ESP change. And a clear banner that says, if you use the App and push firmware, don’t push from ESP. It’s one or the other, not a combination. Hopefully this thread may save someone else a bit of headache. But thank you again for your prompt response!