Hi folks. Really struggling here. I had my NodeMCU devices working with HA 100.1. I have updated the NodeMCU devices to the latest firmware, and am now running HA 107.5 (and the new way to auto discover the konnected devices) I have fixed their IPs to their MAC IDs using my router. Now with the HA update, I see them as discovered devices, but cannot configure them any further. I can’t find the correct Port Number… Also the Konnected app does not find them. I am trying a brute force NMap port find on their respective IPs, but so far not working for me 
Is the Konnected Alarm Panel still being supported?
There’s no reason why it wouldn’t be. The device communicates locally and the software is open source.
Yes. Still alive and well!
In fact, we just released our Konnected Alarm Panel Pro with Ethernet/PoE capability.
Yes! I have the new Alarm Panel Pro and it works great. However, I had no problems with the original panel. I switched because I like the hardwired connection and the additional ports.
Poe? Awesome. I was thinking that was the biggest pitfall with the other boards. I didn’t see the new one on the website?
Thank you. Ill have to take a look. Idk if I’m ready yet but I did just buy some reed sensors and a fibaro smart implant for my front door so I might end up going this route instead.
Just seen your reply. Of course it is still being ‘supported’ by the community. But I was referring to the developer of the panel. Community support of an open source product is a far cry from support from the developer/vender.
Hi @heythisisnate what would be the best way to determine if the konnected panel is available from within HA or Node Red?
I have a large flow in Node Red where I monitor the availability of my devices and make an alert if something goes offline. Currently I ping the konnected IP address, however I wanted to see if there is a better way to do this.
I would probably try an nmap tracker.
I have a custom sensor (python script parsing output of the board : ‘http://192.168.xxx.xxx:yyyyy/status’) to return some information about each board:
HwVersion 2.3.0
SwVersion 2.3.5
Ip 192.168.xxx.xxx
Rssi -48
Uptime 962
Error 200
the script is built to set rssi = -100 if the board is unavailable. This way I can build some automations and notificaitons.
1 Like
What’s the final verdict on the Konnected Pro with Ethernet. I’ve read few mixed reviews, though it’s typically those who are unhappy that are more vocal.
In any event, I have an old ADT SafeWatchPro 3000 system, with 8 zones (door switches + PIRs). I want to replace it with the Konnected Pro and have the following questions:
- Ultimately I want to add some wireless windows sensors. Can the Konnected Pro handle wireless sensors or I need other/additional boards?
- Has anyone replaced their SafeWatchPro ADT system, if so, any feedback on the pros/cons of the new solution?
I’m leaning towards getting the unit, but need some more reassuring feedback first.
I have been using the original konnected alarm and it has been great. I’ve had no stability issues at all and the device has never gone offline. I assume the latest system can only be better as it includes ethernet and a better board.
- Konnected just creates entities for wired elements in your existing system PIR, Reed Switches etc. Any wireless sensors will be added through home assistant using whatever protocol zigbee, z-wave. You would then group all these sensors together and create the alarm automations.
- Can’t help you there
hey, can you share how you did this please? very cool!
Sure. Have just uploaded the code to Git. Take a look. Comments are welcome!
Kol,
What is the unit/value for uptime?
And the error is 200?
- uptime is a value returned by konnected api, it is a timestamp in seconds since 1Jan 1970, it is standard timestamp in unix (I believe) systems;
- ‘200 error’ it is absolutely normal state raised after successful api call. Anything different means a real error. if 200 then konnected board responded
I have created this script for myself thus something may look odd… Sorry for that. If you do not like something I can change, just let me know.
Hi Kol,
Thanks for replying.
I managed to figure out the uptime was seconds. 
I’m not interested (as such) in RSSI as being the sensors state, so changed that to be uptime and formated it to be in days/hours/minutes. The RSSI is still an attribute 
I thought the error/200 was the HTTP return status (200 being ok), but thought I’d checked. Thanks for the script.
J.
I’ve noticed that, when Home Assistant is restarted, the states of some of my Konnected sensors (door is open, alarm is armed) are no longer correct. I have to change the state of the thing (arm the alarm, close the door) for it to pick up the current state.
I seem to remember hearing that there was a change in Home Assistant a couple of releases back where it now longer triggers certain things when it starts up. I assume that is what’s caused the issue, but I couldn’t find any details about what the change was in the recent release notes.
Has anyone else experienced this? Or does anyone know what the change was?
Thanks.
@heythisisnate Are you aware of any issue here?