No state changes seen in Home assistant

Smart Home Integrations SmartThings
21

jprev, are you talking about this part - https://help.konnected.io/support/solutions/articles/32000023470-flashing-konnected-firmware-software

I did that so I can setup the wireless.  It didn't come up as "Konnected" board, but some ESP..., but it was new on the WiFi, so I assumed it was that.  Since I couldn't change it as it was, I updated the firmware.


Thanks for checking the post.  I'm sure it's something I'm missing somewhere!

22

That is what I was referring to, and was what solved the problem for me.  The board is an ESP8266 rebranded as a Konnected board, so that is the correct one.  Sorry the firmware update didn't help you!  It solved it for me and it has been working great since.

23

Perhaps I need to flash again!  Worth a shot.  Something is wrong though.  I setup the new SmartThings hub and it's not seeing it either....after following the steps for Konnected/SmartThings.  


Thanks again....have a better one!

24

I flashed the boards (wifi adapters) again - a few times -, reconfigured, and still no dice.  I had my wife open a door in the kitchen to see if the wifi would flash, and it did not.  It doesn't detect sensors.  


I also got SmartThings hub, went through the steps, no discovery.  In theory, it would discover with no sensors connected, correct?


I have two boards...I wouldn't think both would be bad, but who knows.

25

Tod, Bill and for others having troubles with connections like me.  Sharing what Nate is having me try.  I'm still battling....


You may want to try some of our discovery troubleshooting steps here:

https://help.konnected.io/support/solutions/articles/32000023644-device-discovery-troubleshooting

https://help.konnected.io/support/solutions/articles/32000023786-device-debugging-with-screen

https://help.konnected.io/support/solutions/articles/32000023681-debugging-device-discovery-with-netdisco


I use a Mac at home, so the Network tool works on scanning.


Another option is to place the config in Hassio and forgo discovery.  Haven't tried that yet....just sharing.

26

Same issue for me Konnected 2.2.7, Raspberry Pi running HASSIO 0.95.4

27

This fixed my issue....


From Nate....

 

Make sure you enable discovery. HA changed the default and this is disabled by default now in the most recent version. Just add the following to your configuration.yaml:


discovery:


After adding this one line and rebooting my PI, all is well.

28

I did add the discovery: line, but still a no-go for me.  Looks like I have something in either my AP, switch, router.  

Network setup - I have 

  • Netgear C7000v2 cable modem/router
  • Aruba 2530 8 port POE switch
  • Older Netgear switch (since I'm using more than 8 ports) that plugs into the Aruba
  • Aruba AP 305 that receives power via POE from the 2530
The Konnected boards - I see those on the AP via the web interface.  I also see them in the Netgear router having an IP.  
Raspberry Pi running Hassio (0.95.4 or something like that) is wired into the Netgear.  I also have SmartThings wireless connected to the AP (did wired also at first).

Nate says I have a Discovery problem with the router, but not sure how the router fits in - everything is internal and only the default VLAN.  One subnet, one DHCP, one scope.  Anyway, uPNP is enabled on the C7000.  On the Aruba switch, I enabled IGMP just to see.  On the Aruba AP, I disabled the broadcast filter (it was enabled for ARP) and enabled multicast optimization.  Rebooted everything and still nothing.

I can see the Konnected boards and get to the status page.  Apparently you can put an entry into the configuration.yaml file to point to the IP addresses of the Konnected boards and bypass discovery, but I can't seem to find that.  I that's possible, I'll give it a shot....would be nice to have the same thing for ST.

Next try, setup a personal Hot-spot with my iPad, connect ST, Konnected, and phone into that and see what happens.  That should take my network out of the equation.  

29

FYI, got it working with Hassio.  I added the host and port lines within the konnected: section...

konnected:

  access_token: #!secret konnectedtoken

  api_host: http://192.168.0.46:8123

  devices:

    - id: bcddc23125d3

      host: "192.168.0.54"

      port: "11220"

......


Now on to the next steps!  Hope this helps someone...

30

I'm having the same issue. Konnected was working perfectly on Hassio for the last ~1year, until this morning I did a clean install. The only thing that I believe will have changed is that I am now running the latest version of Home Assistant, which is making me think a recent Home Assistant update might be to blame?


I've tried enabling discovery etc but no luck so far.

31

I've managed to fix my issue - flashing the latest firmware onto the konnected board did the trick! 

32

no sensor state changes all of a sudden with my NodeMcuEsp8266.    I was reading about HA being in a different VLAN .    How do you enable mDNS on mac computuer to get sensors to communicate?

33

I tried flashing my wifi module , nodeMCUEsp8266 with konnected flash tool using lastest updated firmware and filesystem, 2-2-7

When I connect back to breadboard , I get a solid blue light from LED gpio2

device is not transmitting any information to connect to wifi, even using 192.168.4.1



However, when I flash with older firmware, filesystem, 2-2-4, I get flashing LED at gpio2 and able to connect to the wifi and blue light goes out


Any explanation?


Recently , alarm working well with home assistant but one day I realized no state changes with any of my binary sensors.  I saw something on discussion board of that happening to many others.  


Eric 



34

I read through this thread but have not found a solution to this issue that works for me. I am able to see the Konnected zones in my HA setup, but do not get state changes an am unable to control buzzers and alarms attached to the Konnected boards. I ran into this problem during two separate hardware upgrades that I did at the same time, so I am unsure of which caused the break. I was previously running HA on a Rasberry Pi 3 and upgraded to a VM in VMWare Workstation running a fresh hassio image with a dedicated IP address. I am running HA 0.96.5 and have manually flashed the boards with the latest Konnected firmware. I also upgraded from an older Netgear router to the Netgear  Orbi mesh router system and have assigned static IPs. I have attached my .yaml configuration for konnected below. Any help would be greatly appreciated, thanks ! 


 

# Konnected Alarm Configuration

access_token: !secret konnected_token

api_host: http://192.168.1.18:8123

devices:

- id: !secret konnected_04D6

switches:

- zone: out

name: Siren

momentary: 200

pause: 400

repeat: -1


    - zone: 1
      name: Buzzer
      momentary: 65
      pause: 40
      repeat: 2

    - zone: 1
      name: Warning
      momentary: 65
      pause: 40
      repeat: -1

  binary_sensors:
    - zone: 2
      type: door
      name: Front Door
      # wire id: 1

    - zone: 3
      type: door
      name: Utility Door
      # wire id: 18

    - zone: 4
      type: door
      name: Sliding Door
      # wire id:  10 & 11

    - zone: 5
      type: window
      name: Office
      # wire id: 2 & 3

    - zone: 6
      type: window
      name: Guest Bedroom
      # wire id: 4


- id: !secret konnected_73AA
  binary_sensors:
    - zone: 1
      type: motion
      name: Foyer Motion
      # wire id: 5

    - zone: 2
      type: window
      name: Dining Room
      # wire id: 6 & 7

    - zone: 3
      type: window
      name: Kitchen
      # wire id: 8 & 9

    - zone: 4
      type: window
      name: Master Bedroom
      # wire id: 14 & 15

    - zone: 5
      type: window
      name: Den
      # wire id: 17

    - zone: 6
      type: garage_door
      name: Garage Door
      # wire id: 23

 

35

You could try adding the host and port under each id of the board.  Mine is like so:

host: 192.168.1.55

port: 11220


Look up the IP within your Netgear.  You need to use a network tool to discover your port number.  

36

did this ever get resolved,  i have the same issue and i have updated to the latest firmware tried with and without discovery and nada odd thing is it has been working until recently.


Does not matter if Home assistant is running on docker, RPI 2b+ 3B+ or 4B.


I have noticed that my module seems to be rebooting, complaining about DNS but network wise nothing has changed as far as i know. and everything else is fine getting out to the net.


Mo

37

sensors: 


put that in configuration yaml and everything works fine now 

38

I’m on hassio 97.2 RP3b+, just flashed to konnected 2.3.0 and now my switches for arming my vista 20p and sensors no longer work. Any other ideas?

This worked a couple days ago.

39

Cracked it just according to the zones you may have but the important bits in the layout are in bold.


hope this helps you all.


konnected:

  access_token: !secret kcon_access_token

  api_host: http://xxx.xxx.xxx.xxx:8123 # or home assistant port

  devices:

    - id: <Konnected board Mac address >

      binary_sensors:

        - zone: 1

          type: motion

          name: 'Zone 1'

        - zone: 2

          type: motion

          name: 'Zone 2'

        - zone: 3

          type: motion

          name: 'Zone 3'

        - zone: 4

          type: motion

          name: 'Zone 4'

      switches:

        - zone: out

          name: siren

        - zone: 6

          name: 'Beep Beep'

          momentary: 65

          pause: 55

          repeat: 4

        - zone: 6

          name: Warning

          momentary: 65

          pause: 55

          repeat: -1

      host: !secret board1host

      port: !secret board1port

      discovery: false


40

Just wanted to confirm that setting the port, ip and discovery to false resolved the issue for me.  Also, an easy way to the get the port is to use Esplorer as described in help.konnected.io here.