Hi sjee,
with all due respect, my observation gave me different result.
When I put deliberately wrong key - I could NOT control lights, no matter how I tried.
Below is the log with correct key and incorrect key:
GOOD:
#
U 192.168.1.10:50870 -> 192.168.102.21:9898
{“cmd”: “write”, “sid”: “7c49ebb180a3”, “data”: {“rgb”: 1694498815, “key”: “06a82f04d7edef301aa226951be11454”}}
#
U 192.168.102.21:9898 -> 192.168.1.10:50870
{“cmd”:“write_ack”,“sid”:“7c49ebb180a3”,“data”:"{“error”:“Invalid key”}"}
#
U 192.168.1.10:36891 -> 192.168.102.21:9898
{“cmd” : “get_id_list”}
#
U 192.168.102.21:9898 -> 192.168.1.10:36891
{“cmd”:“get_id_list_ack”,“sid”:“7c49ebb180a3”,“token”:“rpQfQ7HjpI42MYqa”,“data”:"[“158d0002389f79”,“158d00029a9e01”]"}
#
U 192.168.1.10:51967 -> 192.168.102.21:9898
{“cmd”: “write”, “sid”: “7c49ebb180a3”, “data”: {“rgb”: 1694498815, “key”: “371b8a6cdd977a4650fa6a7a264e1411”}}
#
U 192.168.102.21:9898 -> 192.168.1.10:51967
{“cmd”:“write_ack”,“model”:“gateway”,“sid”:“7c49ebb180a3”,“short_id”:0,“data”:"{“rgb”:1694498815,“illumination”:1292,“proto_version”:
“1.1.2”}"}
#
U 192.168.1.10:35880 -> 192.168.102.21:9898
{"cmd": "write", "sid": "7c49ebb180a3", "data": {"rgb": 0, "key": "371b8a6cdd977a4650fa6a7a264e1411"}}
#
U 192.168.102.21:9898 -> 192.168.1.10:35880
{"cmd":"write_ack","model":"gateway","sid":"7c49ebb180a3","short_id":0,"data":"{\"rgb\":0,\"illumination\":1292,\"proto_version\":\"1.1.2\"
}"}
Below is a log with WRONG key - you can easily see the difference:
BAD:
#
U 192.168.1.10:34736 -> 192.168.102.21:9898
{“cmd”: “write”, “sid”: “7c49ebb180a3”, “data”: {“rgb”: 1694498815, “key”: “7af615582021f0f1190baf3e4272bd17”}}
#
U 192.168.102.21:9898 -> 192.168.1.10:34736
{“cmd”:“write_ack”,“sid”:“7c49ebb180a3”,“data”:"{“error”:“Invalid key”}"}
#
U 192.168.1.10:45790 -> 192.168.102.21:9898
{“cmd” : “get_id_list”}
#
U 192.168.102.21:9898 -> 192.168.1.10:45790
{“cmd”:“get_id_list_ack”,“sid”:“7c49ebb180a3”,“token”:“fQAHHoorwDlbad0U”,“data”:"[“158d0002389f79”,“158d00029a9e01”]"}
#
U 192.168.1.10:41994 -> 192.168.102.21:9898
{“cmd”: “write”, “sid”: “7c49ebb180a3”, “data”: {“rgb”: 1694498815, “key”: “698cde88db61675774b00179435b6133”}}
#
U 192.168.102.21:9898 -> 192.168.1.10:41994
{“cmd”:“write_ack”,“sid”:“7c49ebb180a3”,“data”:"{“error”:“Invalid key”}"}
#
U 192.168.1.10:54829 -> 192.168.102.21:9898
{“cmd”: “write”, “sid”: “7c49ebb180a3”, “data”: {“rgb”: 1694498815, “key”: “698cde88db61675774b00179435b6133”}}
#
U 192.168.102.21:9898 -> 192.168.1.10:54829
{“cmd”:“write_ack”,“sid”:“7c49ebb180a3”,“data”:"{“error”:“Invalid key”}"}
#
U 192.168.1.10:55482 -> 192.168.102.21:9898
{“cmd” : “get_id_list”}
#
U 192.168.102.21:9898 -> 192.168.1.10:55482
{“cmd”:“get_id_list_ack”,“sid”:“7c49ebb180a3”,“token”:“b8iF0rUb0GMIOFhY”,“data”:"[“158d0002389f79”,“158d00029a9e01”]"}
#
U 192.168.1.10:49520 -> 192.168.102.21:9898
{“cmd”: “write”, “sid”: “7c49ebb180a3”, “data”: {“rgb”: 1694498815, “key”: “3eb11f90127b05e70be57e2252399fae”}}
#
U 192.168.102.21:9898 -> 192.168.1.10:49520
{“cmd”:“write_ack”,“sid”:“7c49ebb180a3”,“data”:"{“error”:“Invalid key”}"}
192.168.102.21 is a Xiaomi GW,
192.168.1.10 - my Linux server with HA running in docker.
I did use --net=host key:
docker run -d --name=“home-assistant” -v /srv/homeassistant:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant
P.S. Well, my GW is still in different subnet but according to the HA manual, this is why “host” is here - in that case multicast mode is disabled and unicast is used. Am I wrong here?
My config:
xiaomi_aqara:
discovery_retry: 10
# interface: ‘192.168.1.10’
gateways:
- mac: 7c49ebb180a3
key: zx46e6tez9qwi4tz
host: 192.168.102.21