Iâm looking forward to testing it. Iâll install it over the weekend.
I have the Niko Home push interface behind all the switches in the house, and I would really love to be able to start a flow from these. Same with the virtual flag on Digital Black.
If thatâs something youâd like to make, Iâd be happy to test it.
I donât have the motor module, but otherwise Iâll go through the rest over the weekend.
Hey @Andreas_Soll
I donât have those push buttons myself but they should work if there is an action tied to them (like turning on a light)
I checked the niko API documentation and virtual flags seem quite simple to implement (page 76) so Iâll add it to my list.
Iâm not the best at development, but Iâm doing my best. Hereâs what Iâve found so far â hopefully itâs useful.
I can confirm that the push-button interface doesnât work âdirectlyâ in the sense that I canât listen for an actual button press via MQTT. I donât get a dedicated âbutton pressedâ event from the push-button interface itself. Instead, I only see the effect of the press â for example a dimmer changing state â as a devices.status message (On/Off) on the UUID of the device/action that the button is linked to. So the input can only be detected indirectly through whatever the button controls.
To get a cleaner input signal, I also tested binding the push-button interface directly to a virtual flag in Niko Home Control. That works really well: the button toggles the flag, and then in MQTT you can simply listen to the flagâs Status (True/False). So it is possible to use push-buttons as an input, but only if you build it using virtual flags. Itâs a bit of a âworkaroundâ and adds extra (and slightly confusing) configuration, but we can only work with what we have.
I was hoping to get clear short/long-press events, but I donât see those as separate events in MQTT in my setup.
I have a really good contact at Niko Home in Denmark, if at some point you find something where it would make sense to get their help.
iâm very impressed/happy with this App. Ever since Niko stopped the support of IFTTT i was looking for an alternative!
is it in your roadmap to also support âNHC routinesâ (like âeverything OFFâ). this could be useful to e.g. enable your alarm when the âeverything OFFâ routine is enabled.
@FlorisVandeVijver The all-off routine has been added to the latest test version. Should be approved in a couple of days, but you can already download/test it here:
Hey all, Iâll work on a step-by-step guide on how to setup Homey + NHC2 since I the app is installed many times by people but not all have successfully added a connected-controller.
Is there a roadmap for integrating moods/scenes? I use these extensively in NHC to activate different shading configurations on hot days by setting multiple blinds to predefined positions.
Alternatively, would it be possible to extend the motor integration so that blinds can be set to a specific position (percentage) instead of only supporting open and close commands?
Hey @Jeroen_De_Roeck
I dont use moods/scenes in my installation because I didnât think it was that useful. The API (on the niko side) is quite simple so Iâll add it to my list
Setting blinds to certain percentage also seems like a nice feature, Iâll add it too
I work on the app it in my spare time so I canât promise a concrete timeline.. soon
I just installed the Niko Home Control 2 app, and successfully added the Connected Controller (with JWT). However, I donât see any lights appearing in the Homey app. I uploaded the NHC II configuration again, and I did reset the Connected Controller. Does anyone have an idea?
New test version available here: Niko Home Control 2 | Homey
You can already test it by installing through the test page.
It will be available somewhere next week officially after approval from Athom/Homey.
@Jeroen_De_Roeck Added option to set percentages for blinds/motors. The Niko hobby API only reports the percentage once it has stopped moving (there are no gradual updates during movement). Let me know if you see any issues
=> I will also add mood/scenes support later, but I postponed it because I have to design images & SVGs to get it approved to the homey store, and I didnât have a lot of time
@KJE I added a diagnostic report to the connected controller so it will be easier to me to help you. Once you add a connected controller, go to settings â advanced settings and please share the diagnosic report with me after installing the test app from the link above.
See screenshot example of how it should look on mobile: (also available through the web UI ofc)