Is anybody else have troubles with Konnected’s ability to stay connected, or be reliable to any degree? I bought into this fully expecting it be a sort of novelty and having such expectations, it hasn’t broken them. But I have a moment to tinker and this ONE bit just will not play well with others. I have flashed to the latest and greatest firmware, it shows connected on my wifi with an appropriate address, hell I can ping it for days, but Home-assistant seems to have other plans. Has anybody gotten it to work as more than just another nifty gadget collecting dust in a steel box in the back of a closet?
Yes, I have Konnected working on Home Assistant (probably 0.86), but yeah, I had some trouble initially due to the odd setup I have (running both HA and SmartThings). I have an older Konnected board I bought a little less than a year ago, flashed to latest firmware and latest SmartThings SmartApp. It connected to Home Assistant just fine (though Home Assistant was spitting out errors even though I didn’t set it up yet, probably due to Discovery component) but when connected to SmartThings, the sensors would stop responding after a few hours and I would have to uninstall the SmartApp. Everything else was working–it was connected to WiFi, the status page shows the correct status of the sensors.
I tried turning off Discovery on the Konnected board, and that fixed everything. It’s been running fine on both for two months now.
Some general troubleshooting tips I have for you:
- If you have set a static IP address for the Konnected board and have it saved, then you should try turning off Discovery on the Konnected board. That basically fixed all problems for me.
- Go to your Konnected board’s local status page and see that your wired sensors are all reporting correctly. So you can narrow down the point of failure.
- Don’t use auto-discovery, setup the Konnected module manually in HA’s configuration.yaml file.
One the connected board is setup with the wifi how do you access the status page? Also I wasn’t aware, more specifically made certain by the creator of connected that discovery was not even supported.
Are you using https on home assistant such as duck DNS? I have found that Konnected struggles with https.
Not currently. I stopped using https when things like konnected were having difficulty
OK. I got them to work… kind of. I’m still not putting much faith in them actually alerting of a real incident (I have other measures for that) but it’s a step forward.
I updated the firmware and did a full reboot on all devices and HA, it took a minute but seems to display (almost) everything properly
I just got my Konnected that I bought last summer connected. My devices show up in the frontend, but when I test them, no changes in states occur.
I don’t know how to access the device’s status to see if it is even sending signals. Nor do I know what firmware it is running. Is there a way to figure this all out remotely without having to disconnect everything which will be a pain in the behind?!
Initially, when I plugged everything into the board, my motion sensors didn’t work. So, I have the power to the sensors running through the old alarm panel (Nate previously said that was okay), and the other parts running through the Konnected panel using the DC adapter.
Here’s my error logs:
Sun May 05 2019 10:49:04 GMT-0500 (Central Daylight Time) Error doing job: Future exception was never retrieved Traceback (most recent call last): File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 131, in device_discovered setup_device(host, port) File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 121, in setup_device discovered.setup() File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 284, in setup self.sync_device_config() File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 388, in sync_device_config if self.desired_settings_payload() != self.current_settings_payload(): File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 368, in current_settings_payload settings = self.status['settings'] KeyError: 'settings'
I’m running HA 0.91.4. I have DuckDNS working, with NGINX. My config is:
> konnected:
> access_token: XXXXXX
> api_host: http://192.168.86.52:8123
> devices:
> - id: my MAC all lower case
> binary_sensors:
> - zone: 1
> type: motion
> name: ‘Entryway Motion’
> - zone: 2
> type: window
> name: ‘Glass Break Livingroom’
> - zone: 3
> type: window
> name: ‘Glass Break Basement’
> - zone: 4
> type: window
> name: ‘Basement Bathroom’
> - zone: 5
> type: smoke
> name: ‘Smoke Detectors’
> inverse: true
> - zone: 6
> type: door
> name: ‘Exterior Garage’
Thanks for your help.
I also got a new Konnected system at one point I was able to have all my sensors working without any issues and it even saw my siren that I have connected into the Konnected board but then my static IP addressing on my Hassio went into affect and the siren just disappeared. I’ve been trying for 3 days now to get everything back up and running, I can get the sensors working no problem but getting the siren back to show up as a switch hasn’t been an easy quest.
I’m pretty new to HA too could someone tell me or show me how to disable discovery on konnected so I could try that?
I know it all works it’s just keeping it working for more than 3 hours is the challenge for me. I’d just be happy if I could get my siren to show back up as a switch so I can actually use the system. I hope someone here might be willing to help?
So I took the wireless part of Konnected out of the board, and followed the directions from the website to update the firmware. I flashed the version 227 released 2 days ago. After reinserting and restarting HA, my sensors are magically working.
Regarding @jaysinism’s siren issue, I dont think you can disable discovery via the Konnected device, but you may want to try disabling the discovery in your HA configuration.yaml file.