[APP][Pro] Niko Home Control 2

:factory_worker: Under development. Current status:

Device Model Supported Planned
NHC Relay Action (lights & other switches) :white_check_mark:
NHC Dimmer Action :white_check_mark:
NHC Motor Action (blinds) :white_check_mark:
NHC Fan Action (ventilation) :white_check_mark:
NHC Thermo switch (Push button w/ sensors) :white_check_mark:
NHC All Off Action :white_check_mark:
NHC Touch Switch Thermostat (& other thermostats) :warning: I’d like to make this but I don’t have these devices. Will be attempted somewhere in the future.

See Niko official documentation of all available actions here: https://mynikohomecontrol.niko.eu/content/hobbyapi/documentation.pdf

1 Like

Hi,

Thank you for your contribution.

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. :slightly_smiling_face:

2 Likes

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.

If you find any bugs please let me know!

Hi @georgechoustoulakis

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.

Hi,

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.

kind regards,
Floris

Hey Floris, thanks for trying out the app!

Niko’s documentation for the ā€œNHC All Off Actionā€ is very simple so I will add it to my list. :+1:

1 Like