Small addition, after I finally managed to update my firmware again, then re-installed your app, I noticed a new version v1.0.81 and could finally get the Konnected alarm Panel installed, but:
Armed in Homey is setting up the panel in ARMED_AWAY
Disarmed in Homey is triggering an error Cannot arm night when not supported in Konnected
Partially armed is in reality setting up the panel in DISARMED
The Cannot arm night when not supported is probably due to the fact that I did not setup any sensor as Bypass Armed Night or Bypass Armed Home in Konnected, because I have same problem in Smartthing triggering Cannot arm home when not supported, but still your app is mixing up Partially armed and Disarmed.
And now with this new version 1.0.81, it seems that what used to be Out 1 in my previous test now became Alarm 1, and that I cannot make my Reboot button anymore, which was quite handy actually!
Thanks @ugrbnk! Looks like you’ve been busy this weekend, 19 new versions I just saw new test version 1.0.85 this morning, so I tried it quickly but same problems:
It looks like it cannot differentiate between different zones of same type, so you can only add one of each type, and the activation of any physical of a type will trigger the one you have installed. Tested only Door and Motion types, but I guess same for any other type.
Window sensor missing. I guess it would be same type as door but different icon, or rename existing “ESPhome Door Sensor” into “ESPHome Door/Window Sensor” and change the icon into both door and Window icon?
Konnected outputs are not supported, or only as Wall plugs. It can be up to 3: Alarm 1, Out 1 and Out 2/Alarm 2. I don’t think Out or Alarm types are different for Konnected.
Konnected Alarm Panel support is missing one type, should be totally: DISARMED, ARMED_AWAY, ARMED_NIGHT and ARMED_HOME, and currently you send DISARMED when selecting “Partially Armed” in Homey, while you read the DISARMED status correctly.
Reboot as button would be nice to have, as it was in 1.0.78
At this point, firmware update of the Konnected board can happen only if your app is disabled, probably because some Com remains open. Not sure if it can be fixed, but at least explained somewhere because firmware updates of the Konnected happen all the time, everytime you change it’s configuration in fact.
Let me know what I can provide to help you, for example log of Konnected says a lot.
I wanted to give a huge shout-out to the developer for the incredible support. I was having trouble getting my ratgdo (ESPHome) to trigger the garage door through the Homey Pro, even though the state was reporting correctly.
The developer worked with me through several iterations and custom drivers until we got it 100% functional. If anyone else is looking for a solid way to integrate ESPHome devices/ratgdo into Homey, this is it. Fast, responsive, and world-class support!
Thanks for the new ESPHome Window Sensor, perfect
But same problem as before: When I try to add the second Door, Motion or Window, I get an error message:
And same as before: The Door/Motion or Window sensors I added will get switched if ANY Door/Motion or Window is physically switched on the Konnected Panel. Only difference is that now Window BJ is the one changing status for any Door or Window Sensor, but that makes sense since Window ir just another Door sensor with another icon. I also confirmed checking Konnected Web or SmartThings that all physical sensors changes are seen correctly, only your app cannot differenciate and treat all Door or Window physical sensors as Window BJ and all physical Motion Sensors as Motion HA.
For fun, I tried to add again REBOOT as ESPHome Button, but not working anymore:
So that’s it for tonight and version 1.0.87 Test. A lot of improvement in the Konnected Alarm Panel itself, thanks a lot for that, but still the biggest problems remain:
It looks like it cannot differentiate between different zones of same type, so you can only add one of each type, and the activation of any physical of a type will trigger the one you have installed. Tested only Door and Motion types, but I guess same for any other type.
Konnected Alarm Panel support is missing one type, should be totally: DISARMED, ARMED_AWAY, ARMED_NIGHT and ARMED_HOME, and currently you send DISARMED when selecting “Partially Armed” in Homey, while you read the DISARMED status correctly.
And small points:
Reboot as button would be nice to have, as it was in 1.0.78
Cannot control Alarm 1 as just another Output (While Konnected definitetly can)
Window and Door Sensors show battery capabilities, while by definition on Konnected Panel they are powered by main
Motion Sensors show Luminance or Temperature, which by definition cannot be on Konnected Panel, it is only binary sensors
History does not show which sensor or output, so that makes it quite useless
I want to thank you again for all your efforts, it is really amazing I realize that you probably do not have the panel at hand to test it, so what’s why I give you so much details, but if you need, I could let you play with my Homey remotely, even temporarely open a few ports for you on my router or Teams session? I am a former hardware Engineer, now Sofware Engineer, so let me know what I can do to help?
Thank you very much for your feedback. I am trying to provide the best support I can, but I am encountering some limitations with Homey. I will look into what else I can do and make updates. Thank you for your support.
Good evening @ugrbnk , I noticed you released 1.0.90 Test so I gave it a quick check, but now it became impossible to add the Konnected Alarm Panel at all, I get the error:
Same as if I try to add a second Door Sensor, Windows Sensor or Motion Sensor.
Only choice is to close or cancel and nothing added at all. I can still add separate sensors, but from the second sensor of same type, I get the same old:
Okay, actually, it seems like we’re making great progress. Since I don’t have this device, we’re moving forward through trial and error. When added via SmartThings, is it added locally or via the cloud? I’m trying to implement an addition method similar to the SmartThings structure.
Yes, definitely, and again I am really impressed and happy how fast you reply and how many builds you make to try to address all issues. Did you see what I posted for you on Konnected community? Not only it should bring you a lot of Users, but I hope Nate (the founder of Konnected) sees my message and sends you a Konnected Panel to thank you for your efforts That is the least they could do since this will bring them full support in Homey, which is pretty big in Europe, at least in the Netherlands where I live.
Yep, I figured out! But you are doing great programming this “blind“
If you want, I could open the port 6053 on my router for you so you could talk to my Konnected panel directly? If you are interested, send me an email to morisse@ziggo.nl, since I do not want to give my router details here Alo, I don’t know if you are aware, but Konnected has a great API doc at Introduction, it is not completely up to date, but I could test my panel yesterday evening using Powershell examples, really cool I can also give you the few calls missing from their doc when spying on the Web app, such as:
text_sensor/ESPHome Version
text_sensor/Project version
text_sensor/Reboot Reason
And I do not mind to test a new version everyday, that is kind of exciting to come home everyday and discover the progresses you made! I cannot wait for the new version
SmartThings is definitely using the cloud and so far it worked perfectly. it is also documented at Introduction
And finally, if I try to add each sensor manually, same problem as before: I can only add 1 Door, 1 Motion and 1 Window, and from the second one I get the same old error:
And this time, their status is incorrect (should be ON), and do not update at all:
I didn’t see this mentioned anywhere, but it looks like the limitation Mark M referenced (only being able to add one entry per type) might actually be tied to the group that the Konnected panel is associating the sensors with.
In my case, it appears they’re labeled as something like “Door Main HA,” but that seems to just represent the overall group of door contact sensors rather than individual zones.
When I add my sensors, the name I assign doesn’t seem to matter. No matter which specific door I open, the same “door contact” alert is triggered. The same behavior applies to the windows. Because of that, I don’t think this is tied to the actual control panel zones themselves, but rather to the sensor type grouping.
I hope that makes sense.
For context, I’m in the U.S. and available for a few more hours if anyone wants me to run additional tests.
Example: regardless of which door is opened, the system shows the same door contact as triggered, and it clears only when all doors are closed.
All sensors and outputs show the Alarm icon, not the Windows/Door/Motion or output icons, and pretend to be the Alarm Panel and show the same error when trying to Arm, Disarm or Partially arm:
All Sensors are showing an incorrect status, they should all be triggered (ON)
That’s it, you fixed the adding the sensor problem, but all sensors and Panel have this Could not get device by id error. I find this strange because you manage to communicate correcty to the panel when adding it (you get back the list of sensors), but not once all are installed. I do not know if that helps, but from spying on the Konnected Web page, I can see all correct id’s:
I just saw new test version 1.0.85 this morning, so I tried it quickly but same problems:
I realize that you probably do not have the panel at hand to test it, so what’s why I give you so much details, but if you need, I could let you play with my Homey remotely, even temporarely open a few ports for you on my router or Teams session? I am a former hardware Engineer, now Sofware Engineer, so let me know what I can do to help?
That is the least they could do since this will bring them full support in Homey, which is pretty big in Europe, at least in the Netherlands where I live.
Alo, I don’t know if you are aware, but Konnected has a great API doc at 
