So I have the device-discovery etc. part working, and ESPlorer shows Konnected trying to send updates when my sensors change - but the updates aren't "received" by HomeAssistant. My HA setup is TLS-enabled (using the DuckDNS addon) Doing a packet capture in the docker-container running HA, and filtering for the IP of the first Konnected device - I can see the TCP connection establish, and the SSL connection proceeds as expected:
=> Client Hello
<= Server Hello
<= Certificate, Server
Key Exchange, Server
Hello
Done
And then, Konnected/NodeMCU's TLS implementation returns the following 'Decrypt Error' on the wire
Secure Sockets Layer TLSv1.2
Record Layer: Alert (Level: Fatal, Description: Decrypt Error)
Content Type: Alert (21)
Version: TLS 1.2 (0x0303)
Length: 2
Alert Message Level: Fatal (2)
Description: Decrypt Error (51)
I can obviously connect to HA using TLS from multiple browsers, and from the Linux 'openssl' command-line client. The relevant logs from the NodeMCU device are:
HTTP client: Disconnected with error: 46
HTTP client: Connection timeout
Heap:33472 HTTP Call: -1 state 1 pin 2
E:M 528
HTTP client: Disconnected with error: 46
HTTP client: Connection timeout
Heap:33288 HTTP Call: -1 state 0 pin 2 E:M 528
HTTP client: Disconnected with error: 46
HTTP client: Connection timeout
Heap:33288HTTP Call:-1state1pin2
Any hints as to where to go next - I do know some lua, but I couldn't see if the Konnected scripts had any way to interrupt the boot process.
I just spent a few hours on this and can confirm it is an issue. Hassio gets the initial sensor status but then will not receive updates if duck dns/SSL is enabled.
Ugh - the forum ate all my formatting… Thanks for the response.
I’m gonna break out a spare NodeMCU board I have and see if I can’t get it talking TLS to the same HA instance - that will at least prove whether this is specific to the Konnected firmware build or not. I really don’t want to turn off TLS at this point.
Hope someone find an easy fix for this. Only ideas I can think of are to see if it is possible to have a TLS connection facing the internet and a non TLS on a different port but only accessible on the Lan. Second idea is to have a dedicated HA install just for konnected and output the sensors to Mqtt to be picked up by the main HA install.
This looks like a similar issue
https://github.com/konnected-io/konnected-security/issues/60
If tls support is fixed won’t we have another issue if it configures konnected to use the duckdns address instead of the local ip which will fail if the internet and dns server is down? It really needs to use a different port, maybe using a konnected addon for Hassio.
I did a custom build of Konnected firmware, but based on the NodeMCU -dev branch. (actually - I’ve done about 30 custom builds of the firmware to get this far 
But - some success - Konnected is now talking to my SSL-enabled HA instance.
Now to rationalize those semi-random changes to figure out which are really needed.
2018-05-29 23:11:23 INFO (MainThread) [homeassistant.components.http.view] Serving /api/konnected/device/600194751d6b to 192.168.2.68 (auth: False)
2018-05-29 23:11:23 INFO (MainThread) [homeassistant.core] Bus:Handling , new_state=>
2018-05-29 23:11:33 INFO (MainThread) [homeassistant.components.http.view] Serving /api/konnected/device/600194751d6b to 192.168.2.68 (auth: False)
2018-05-29 23:11:33 INFO (MainThread) [homeassistant.core] Bus:Handling , new_state=>
I noticed that TLS was upgraded in the latest version of konnected to resolve the krack exploit. Has anyone tried an older version from before this upgrade?
I need an update too to at least get a timescale. If it is going to be a drawn out fix, am wondering if I can achieve similar by using Hassio with the raspberry pi gpio as Hassio has built in support and also wired ethernet. I dis want to give konnected a go but can’t use it without this feature.
Look at the end, Nate says there is no reason why it shouldn’t work with ssl and he is going to look at it. He says it could be because konnected does not have all the ciphers installed to save memory.
Thanks Nate, I have posted the https information from Google Chrome in the home assistant forum thread. Let me know if you want me to test anything.