MiBoxer 2.4 Gateway Model. NO: WL-Box1 cant be found by Domoticz
Posted: Thursday 26 March 2020 13:26
Dear Domoticz users,
Situation
The homemade exterior lighting I built in under the edge of the roof uses a Mi-Light RF Wireless Led Dimmer. Connected to this is a Led strip without RGB lighting.I used the remote control, especially for the white LED lighting, to turn it off and to dim the lighting. To finally be able to switch it via home automation, I bought the MiBoxer (Model no.: WL-Box 1).
At this moment I can control the outdoor lighting with an old phone on which the MI-Boxer app is installed. But of course, this was not the end goal.
Domoticz is now installed on a freenas server which is also used for a website and plex server. The freenas server is connected to a Fritzbox where the DHCP is enabled. An Orbi mesch network is connected to the Fritsbox. This network transmits at 2,4 and 5 G and where DHCP is disabled. With computer, laptop and phone it is no problem to communicate with each other.
In the Fritzbox I gave the MI-Boxer a fixed ip address, namely 192.168.178.37. So to add the Mi-Boxer to Domotiz all I need is a port.
In the terminal of Linux I used;
nc -z -v 192.168.178.34 1000-9999
As a result:
nc: connect to 192.168.178.34 port 6666 (tcp) failed: Connection refused
nc: connect to 192.168.178.34 port 6667 (tcp) failed: Connection refused
Connection to 192.168.178.34 6668 port [tcp/*] succeeded!
nc: connect to 192.168.178.34 port 6669 (tcp) failed: Connection refused
nc: connect to 192.168.178.344 port 6670 (tcp) failed: Connection refused
In this (https://www.domoticz.com/forum/viewtopic.php?t=30674) topic on the domoticz forum I read that this is the port used for communication with android, along with port UDP 6667. I also tried port 5987 and 9988. I also enabled “accept hardware for 5 minutes”.
Still, none of that makes any difference and in the log I get:
2020-03-26 12:05:28.955 Status: AppLamp: Worker Started...
2020-03-26 12:05:33.085 Error: AppLamp: Bridge not found, check IP Address/Port!...
2020-03-26 12:05:33.085 Error: AppLamp: Worker stopped....
I've been reading for several hours looking for a solution. I strongly suspect that the solution must be sought in Domoticz. But who can point me in the right direction? Do I use the wrong port?
What I've read/found:
https://www.domoticz.com/forum/viewtopic.php?t=30674
https://ehoco.nl/milight-ibox2-installeren-domoticz/
https://baptiste-wicht.com/posts/2017/0 ... ystem.html
https://www.amazon.com/gp/customer-revi ... B01N7C3HXQ
For the Dutch people
https://gathering.tweakers.net/forum/li ... 50755/last (Not all messages read, cause 37 pages random problems with milight)
Domoticz version V4.10717
Jail Release 11.3
OS FreeNAS-11.2-U8
English is not my first language, so there could be some writing errors
Situation
The homemade exterior lighting I built in under the edge of the roof uses a Mi-Light RF Wireless Led Dimmer. Connected to this is a Led strip without RGB lighting.I used the remote control, especially for the white LED lighting, to turn it off and to dim the lighting. To finally be able to switch it via home automation, I bought the MiBoxer (Model no.: WL-Box 1).
At this moment I can control the outdoor lighting with an old phone on which the MI-Boxer app is installed. But of course, this was not the end goal.
Domoticz is now installed on a freenas server which is also used for a website and plex server. The freenas server is connected to a Fritzbox where the DHCP is enabled. An Orbi mesch network is connected to the Fritsbox. This network transmits at 2,4 and 5 G and where DHCP is disabled. With computer, laptop and phone it is no problem to communicate with each other.
In the Fritzbox I gave the MI-Boxer a fixed ip address, namely 192.168.178.37. So to add the Mi-Boxer to Domotiz all I need is a port.
In the terminal of Linux I used;
nc -z -v 192.168.178.34 1000-9999
As a result:
nc: connect to 192.168.178.34 port 6666 (tcp) failed: Connection refused
nc: connect to 192.168.178.34 port 6667 (tcp) failed: Connection refused
Connection to 192.168.178.34 6668 port [tcp/*] succeeded!
nc: connect to 192.168.178.34 port 6669 (tcp) failed: Connection refused
nc: connect to 192.168.178.344 port 6670 (tcp) failed: Connection refused
In this (https://www.domoticz.com/forum/viewtopic.php?t=30674) topic on the domoticz forum I read that this is the port used for communication with android, along with port UDP 6667. I also tried port 5987 and 9988. I also enabled “accept hardware for 5 minutes”.
Still, none of that makes any difference and in the log I get:
2020-03-26 12:05:28.955 Status: AppLamp: Worker Started...
2020-03-26 12:05:33.085 Error: AppLamp: Bridge not found, check IP Address/Port!...
2020-03-26 12:05:33.085 Error: AppLamp: Worker stopped....
I've been reading for several hours looking for a solution. I strongly suspect that the solution must be sought in Domoticz. But who can point me in the right direction? Do I use the wrong port?
What I've read/found:
https://www.domoticz.com/forum/viewtopic.php?t=30674
https://ehoco.nl/milight-ibox2-installeren-domoticz/
https://baptiste-wicht.com/posts/2017/0 ... ystem.html
https://www.amazon.com/gp/customer-revi ... B01N7C3HXQ
For the Dutch people
https://gathering.tweakers.net/forum/li ... 50755/last (Not all messages read, cause 37 pages random problems with milight)
Domoticz version V4.10717
Jail Release 11.3
OS FreeNAS-11.2-U8
English is not my first language, so there could be some writing errors