Domoticz

I've readded the buttons and that was the solution, thanks.

But I've also removed the Gateway to readd it.. but that one never appeared back.
(i've triggered the light of the gateway multiple times with the mihome app)

Without any problem I was able to add the Xiaomi RGB Gateway as a new Device to Domoticz (v. 3.6669) on a Synology NAS. I can see in the logs that Domoticz sends an on / off command (2017-02-11 21:42:38.810 User: nielsvdv initiated a switch command (67/Xiaomi RGB Gateway/On)). But nothing happens with the led on the gateway.

Does someone has a solution for this problem?

get the latest version from corbin git, should work fine

nielsvdv wrote:Without any problem I was able to add the Xiaomi RGB Gateway as a new Device to Domoticz (v. 3.6669) on a Synology NAS. I can see in the logs that Domoticz sends an on / off command (2017-02-11 21:42:38.810 User: nielsvdv initiated a switch command (67/Xiaomi RGB Gateway/On)). But nothing happens with the led on the gateway.

Does someone has a solution for this problem?

Which model? I mean Synology NAS model.

galadril wrote: But I've also removed the Gateway to readd it.. but that one never appeared back.
(i've triggered the light of the gateway multiple times with the mihome app)

The "Xiaomi RGB Gateway"? I tried deleting mine and it was found again when restarting the gateway in Domoticz. There is no need to trigger the light anymore.

murtadin wrote:

nielsvdv wrote:Without any problem I was able to add the Xiaomi RGB Gateway as a new Device to Domoticz (v. 3.6669) on a Synology NAS. I can see in the logs that Domoticz sends an on / off command (2017-02-11 21:42:38.810 User: nielsvdv initiated a switch command (67/Xiaomi RGB Gateway/On)). But nothing happens with the led on the gateway.

Does someone has a solution for this problem?

Which model? I mean Synology NAS model.

I have a DS216Play with the latest Domoticz Beta installed. So not the version from Corbin.

nielsvdv wrote: I have a DS216Play with the latest Domoticz Beta installed. So not the version from Corbin.

Ok great, if you try my version, does it still not work?

So I have a time script to turn off a gateway led after N seconds without motion detection. For some reason, turning off the light sometimes fails.

example:
017-02-13 21:15:00.646 EventSystem: Script event triggered: HallOff
2017-02-13 21:15:00.685 Activating Scene/Group: [grp_led]
2017-02-13 21:15:00.686 Activating Scene/Group Device: Xiaomi RGB Gateway (Off)
2017-02-13 21:15:00.837 (Xiaomi_Gw) Lighting Limitless/Applamp (Xiaomi RGB Gateway)
2017-02-13 21:15:01.110 (Dummy_Gw) General/Custom Sensor (Sun Azimuth)
2017-02-13 21:15:01.579 (Dummy_Gw) General/Custom Sensor (Sun Altitude)
2017-02-13 21:15:01.634 (Xiaomi_Gw) Lighting Limitless/Applamp (Xiaomi RGB Gateway)
2017-02-13 21:15:01.653 {"cmd":"report","model":"gateway","sid":"286c0785ad14","short_id":0,"data":"{\"rgb\":0}"}
2017-02-13 21:15:25.637 (Xiaomi_Gw) Light/Switch (Xiaomi Motion Sensor)
2017-02-13 21:15:25.656 {"cmd":"report","model":"motion","sid":"158d000127ca18","short_id":54285,"data":"{\"no_motion\":\"300\"}"}
2017-02-13 21:19:45.703 {"cmd":"heartbeat","model":"plug","sid":"158d00012aead2","short_id":21811,"data":"{\"status\":\"on\",\"inuse\":\"1\"}"}

we see the domoticz sending the off message (Activating Scene/Group Device: Xiaomi RGB Gateway (Off)) and then a reply from the gateway confirming it 2017-02-13 21:15:01.653 {"cmd":"report","model":"gateway","sid":"286c0785ad14","short_id":0,"data":"{\"rgb\":0}"}

now this one:

2017-02-13 21:04:00.497 EventSystem: Script event triggered: HallOff
2017-02-13 21:04:00.513 Activating Scene/Group: [grp_led]
2017-02-13 21:04:00.514 Activating Scene/Group Device: Xiaomi RGB Gateway (Off)
2017-02-13 21:04:00.665 (Xiaomi_Gw) Lighting Limitless/Applamp (Xiaomi RGB Gateway)
2017-02-13 21:04:50.527 (Xiaomi_Gw) Light/Switch (Xiaomi Motion Sensor)
2017-02-13 21:04:50.546 {"cmd":"report","model":"motion","sid":"158d000127ca18","short_id":54285,"data":"{\"no_motion\":\"300\"}"}


doesn't have the confirmation from the gateway and remained on until I switch it off manually. Any clue what it might be?
I have my rpi connected to via eth cable, and xiaomi connected via wifi to another router but they are in the same network, not sure if it's related with that..

EDIT: I guess these were network issues, I'm now using wifi interface from pi and it is on the same wireless network then gateway and it looks like its working good!

Did anyone check if the Xiaomi gateway 'calls home' to China?
I wonder how secure this gateway is, I could not find anything online about it.

bbqkees wrote:Did anyone check if the Xiaomi gateway 'calls home' to China?
I wonder how secure this gateway is, I could not find anything online about it.

Mine doesn't get internet acces (he set a parental limit, i just those malrvelous chinise radio...function)

@deennoo which site are you blocking?

deennoo wrote:

bbqkees wrote:Did anyone check if the Xiaomi gateway 'calls home' to China?
I wonder how secure this gateway is, I could not find anything online about it.

Mine doesn't get internet acces (he set a parental limit, i just those malrvelous chinise radio...function)

I ordered one this week, if it does not need internet access after setup I can easily block the gateway from accessing the internet in my Edgerouter.

bbqkees wrote:Did anyone check if the Xiaomi gateway 'calls home' to China?
I wonder how secure this gateway is, I could not find anything online about it.

I did some research with a man-in-the-middle setup. It's calling home. So far I discovered the following dns/addresses/ranges:

DNS requests for: ot.io.mi.com,
DNS answer: 42.62.48.114, 58.83.200.2-12, 42.62.48.225, 42.62.48.2, 42.62.48.112, 42.62.48.113
DNS requests for: ott.io.mi.com
DNS answer: 58.83.160.36,58.83.160.14,42.62.94.185

Sniffing Results:
UDP: 58.83.200.0/24, 42.62.48.114
TCP: 58.83.160.36

Its sending some TCP requests during startup (maybe update requests?) and recurring UDP requests (heartbeat?). Additionally it sends UDP packages for every action (Movement, Button. etc). Unfortunately i'm not able to decode the send data.

I've blocked these connections ... until now its trying hard to reach only these endpoints but maybe there are more.

BTW: @corbin: thanks for your plugin! for me its working like a charm and hopefully it will be soon in the release path. I tried to get the heartbeat/battery level but in 24h (sniffing) i didnt received a single message with these information, maybe its in an earlier release. This page https://louiszl.gitbooks.io/lumi-gateway-local-api/ (use translator) is up to date and reports that there where changes related to battery measurement maybe a new update is available (dont know because everything is blocked ) deliviering new features.

mschreier65 wrote:
I did some research with a man-in-the-middle setup. It's calling home. So far I discovered the following dns/addresses/ranges:

Its sending some TCP requests during startup (maybe update requests?) and recurring UDP requests (heartbeat?). Additionally it sends UDP packages for every action (Movement, Button. etc). Unfortunately i'm not able to decode the send data.

If it calls home for apparently everything that is happening in your home, blocking is thus highly recommended!

bbqkees wrote: If it calls home for apparently everything that is happening in your home, blocking is thus highly recommended!

Sure, but i looks like the gateway is not accessible from phone if outbound connections are blocked....doing some more test

Some sporadic bug detected:
I have 3 Xiaomi Door/Window sensors. Very often (but not every time) after upgrade to latest beta, 2 of 3 sensors changed state to "Open" (but door/windows remains closed). In MiHome apps i see correct state (closed).

I have to open/close door to set status of device to right state.

pavelbor wrote:Some sporadic bug detected:
I have 3 Xiaomi Door/Window sensors. Very often (but not every time) after upgrade to latest beta, 2 of 3 sensors changed state to "Open" (but door/windows remains closed). In MiHome apps i see correct state (closed).

I have to open/close door to set status of device to right state.

same issue

After last update to v3.6729 Xiaomi Gateway stopped working with domoticz. Anybody else experience same problems?

pavelbor wrote:Some sporadic bug detected:
I have 3 Xiaomi Door/Window sensors. Very often (but not every time) after upgrade to latest beta, 2 of 3 sensors changed state to "Open" (but door/windows remains closed). In MiHome apps i see correct state (closed).

I have to open/close door to set status of device to right state.

Same thing but reversed some Time door is open, mi Home says open but Domoticz stay close.

Placed an order for the complete set at gearbest earlier this week. Got a reply that they a cant deliver at the moment. Further questioning got me the following replies:

We are sorry to inform you that this item is unavailable and won't be restocked in short time.
Yes, the supplier can not provided the item in short time as the item need to update.

Wondering what this new update might include