Niko Home Control II

IFTTT with NHC is ready to connect. And it works!

1 Like

Hi Bjorn,

It works but it seems Google Assistant isn’t working anymore with IFTTT?
I created applets on IFTTT for Google Assistant -> NHC but won’t work.

Grtz
Herm

I figured it out with some Googling, it was a number.
Also you had to replace = with : I guess to fix the JSON-code formatting.

Thank you, I solved the question.

Hi,

did anyone succeed in viewing the videostream of the videophone? by using the hobby API, the URL seems to be /pbhelper/stream.mjpeg, but it seems to ask for a login/password combo. Anyone an idea?

thx
F

hi @iamnohero

If you are talking about this product range, we can get you up and running :wink:

https://www.niko.eu/nl-be/producten/niko-home-control/ip-producten/videobuitenpost-productmodel-niko-b2288a3a-c2dc-47c9-8dbe-a5a200f12c86

Normally there are 2 ways of watching the videostream:

RTSP

rtsp://admin:123qwe@192.168.1.50/rtsp/video.av

MJPEG

http://admin:123qwe@192.168.1.50/pbhelper/stream.mjpeg
http://admin:123qwe@192.168.1.50/pbhelper/stream.mjpeg?width=320&height=240
http://admin:123qwe@192.168.1.50/pbhelper/stream.mjpeg?width=720&height=576?quality=80 (max = 100)

To get the list of recordings:

curl -u admin:123qwe “http://192.168.1.50/api/v1/video_list?button=1” (button = the actual button of the videophone, up to 4 I believe)

You will get a JSON reply like this

{
“ok”: true,“rv”: {“video_list”: [
{“call_ids”: [
“c3aa4549”
],
“time”: 1394113883,
“id”: “2”,
“duration”: 200,
“url” : “/recording/video-2.m3u8”,
“event_data”: {
“button”: 3,
“type”: “button”},

You can download recordings from the videophone like this.

curl -u admin:123qwe “http://192.168.1.50/recording/video-2.m3u8”

Actually, the videophone is a rebranded intercom of Robin Telecom, a dutch brand. Their API documentation is attached here :wink:

Have fun :slight_smile: How-To_The_Robin_API_v3.6.0_ENG.pdf (525.8 KB)

1 Like

Hi @bccrew,

thanks for the useful info [it explains why the model property is robinsnip],
however i seem to struggle with the IP address.
it does not seem to be the one of NikoHomeControl. if i look to the properties of the videophone [via the Hobby API], the IpAddress=172308465.00, which correspond to 10.69.55.241, but it seems that this IP is not part of my LAN subnet [192.168.0.* ].

any idea on how to access it?

@iamnohero
Unfortunately I don’t have the videophone myself so I can’t test it, but I think that the coco hands out IP addresses to mac address ranges known to Niko. I should actually try to see if the coco is running a DHCP server but I can’t seem to remember it does.

What you can try is to add a static route on your computer and make the coco the gateway for that traffic.

On Windows in an elevated prompt you can enter:

route ADD 10.69.0.0 MASK 255.0.0.0 192.168.0.x

where 192.168.0.x is the IP address of your coco. Hopefully the videophone has a route back to your PC but I have not tested this. I knew a guy that could hook up the videophone to his synology, I think he gave the second NIC of his synology an IP address in the 10.69.x.x range (in your case maybe 10.69.55.x) and hooked that up to the coco. So in that case, the coco acts as a dumb switch and bridges the 2 devices.

You can always just ask Niko if you’d like, they are very helpful on the Facebook chat. Some people within Niko are using Openhab themselves and they are aware of this binding and are very interested in people doing this as a hobby. @Mherwege and I had a meeting last summer at their office to talk about Openhab. They are really nice guys!

I have done some further development on the Niko Home Control binding, relevant for users with Niko Home Control II. The changes have been submitted for review in PR#6641.
This version does:

  • Map some extra device types that can be configured in Niko Home Control to openHAB.
  • Adds instant power measurement readings to openHAB.
  • Implements Niko Home Control II API token based authentication:
    You need to enable the hobby API in your Niko Home Control profile at the Niko website. This will be used once for authentication. All communication afterwards is still local. The token will expire after one year.
  • Bug fixes and stability improvements.

You will need to be on openHAB 2.5 for this version of the binding to work. Remove the binding from your installation and copy the development version in the addons directory. Reconfigure the bridge to use token authentication.
The binding .jar file can be found here. Updated documentation is available here.
As always, please provide feedback how things work out. I am keen to improve on this.

2 Likes

Hello,

I am new in Openhab but have connect the subnet 10.69.55.1 to the second port of the QNAP and installed the QVR-client to open the Nikohome Videophone with IP-address 10.69.55.107.
It works very well.

First don’t forget to make a BACKUP of the ROBIN-videophone with name: backupsettings.txt (3.6 KB) backupsettings.txt. When you change something in the properties the phone doesn’t work! even when you restart NIKO HOME!!! ATTENTION.Don’t change the SIP ACCOUNT !!!

1 Like

Does someone have an example rule to get the recordings from the videoPhone?
I’m messing around with it, but am unable to do this in Openhab for now.
I’m pretty new to OpenHab, and an example would really help.

curl -u admin:123qwe http://10.68.55.107/api/v1/video_list?button=1
then you get the answer:

{
“ok”: true,“rv”: {“video_list”: [
{“call_ids”: [
“c3aa4549”
],
“time”: 1394113883,
“id”: “2”,
“duration”: 200,
“url” : “/recording/video-2.m3u8”,
“event_data”: {
“button”: 3,
“type”: “button”},

You can download recordings from the videophone like this.

curl -u admin:123qwe http://10.69.55.107/recording/video-2.m3u8

Yes, that indeed I understand.
But I would like to download the recordings (to for instance a NAS) every time there is a new recording.

the Curl commands work when I use them on my pc, but when I try it in Openhab I’m keep getting “null” as my string value:
testCurl = executeCommandLine(‘curl@@-u@@admin:123qwe@@“http://192.168.1.62/api/v1/video_list?button=1”’)

I was able to resolve it by adding a execution time to the executeCommandline
testCurl = executeCommandLine(‘curl@@-u@@admin:123qwe@@“http://192.168.1.62/api/v1/video_list”’,10000)

Thanks for all the info regarding the Niko Doorbell!

2 Likes

Hi @dstammen,

What IP are you using? Is it the one from the Niko controller?

@nicovdz

no I’m using the IP of the Niko VideoDoorbell.
I have my doorbell connected to a PoE switch in my own network (so not behind the Niko home controller)
but this is not a problem for the controller, it detects the VideoDoorbell just fine, and then I can directly access the doorbell with openhab

Hello,

I’m new to openhab and would like to connect my Niko Home Control hub. It’s discovered by Openhab but i can’t connect to the hub. I see that the ip adres of the discovered hub is the same of the computer his ip. Can anyone help me to set up the connection with my Home control hub?

Thnx

I don’t know if the hub is already supported. Probably only the nhc controllers. If i’m correct, it’s currently not possible in the nhc software to use the controller and hub together.

@SCT I can’t guarantee 100% it will work with the hub. However, the programming software is exactly the same, and to my understanding, the API should work exactly the same as well. So I expect it to work with, at most, minimal change to the binding.
To my knowledge, you are the first one to try with the hub. You state the hub is discovered. What version of the binding do you use? Is it the version that comes with openHAB 2.5. or the development version? For the release version, you will need to follow the instructions from the documentation and set up a profile with password in the Niko Home Control software. Add this to the configuration parameters and start discovery for the binding again.
I am surprised you state the hub’s discovered IP is the same as the IP of your computer. What computer are you running openHAB on? Do you have any routing in your network set up?
To further help analyze, I would need you openhab.log file. It would als help to switch on debug logging. The may be hints there on what you did and what works/doesn’t work.