I have the same issue and face the same lag with ssensors connected to ha via a xiaomi gateway configured to Chinese server (only option). Have you solved the lag issue?
So this gateway is like a hacked version of Alexx Gateway 3 and can integrate all devices into home assistant? Like BLE devices and other xiaomi stuff?
No unfortunately not. You can only control yeelight devices not the xiaomi aquara stuff
1 Like
Hi,
Is it possible to retrieve rssi values from the BLE like on the zigbee ?
hi, two simple question, is ZNDMWG03LM works with the newest version of ha? its works with zigbee 2 and 3 versions?
Hello,
I have a strange warning every 30 seconds in the logs but everything seams to work great.
WARNING (SyncWorker_1) [custom_components.xiaomi_gateway3.core.mini_miio] Can't send get_properties [{'did': '374250432', 'siid': 3, 'piid': 1}]
Probably it’s about alarm but I don’t use any alarm on my gateway
'lumi.gateway.mgl03', 'mac': 'xxxxxxxxxxxxxxxxx', 'type': 'gateway', 'init': {'firmware lock': True, 'alarm_did': '374250432'}}
Any Idea how to get rid of it?
Hi …
First: a lot of respect and admiration for @AlexxIT for all the work he has done on this device! Wow!
But … I can’t seem to get the ZHA integration to work with my gateway (zndmwg03lm).
I flashed it with the custom firmware (1.4.6_0012 #20210127) and added it to my HA setup.
All well so far … the device is found an added and so are the entities.
Now I switch it into ZHA mode (via options -> mode -> ZHA ==> Success!) and add the ZHA integration.
After switching I’ve got the following notification:
I use these values to set up the ZHA integration, but every time I click submit I almost instantly get:
(notice: I did enter 115200 as the port speed, but it jumps back to 57600 when the error is shown)
What am I missing here?
Running Core version: 2021.3.0 / Supervisor 2021.03.3 / HA OS 5.12 on a RPi2 by the way
Same problem here:
I have 1.4.6_0043 firmware and ZNDMWG03LM
I entered Gateway IP address and Mi Home Token but no divices apear
Do i have to make any comands to open telnet previuos?
2021-03-11 19:26:28 DEBUG gateway3 192.168.50.247 | Can’t read devices: telnet connection closed
Here are same problems with 1.4.6_0043.
When I try make telnet connection on putty I can’t login with “admin” or “app” user, because account have password!
Hi Everyone.
I think I’m on the same boat, I’m using the version 1.4.6_0043, I added the gateway without issues but none of my zigbee ou bluetooth devices appear.
I followed the the documentation and added :
{"method":"set_ip_info","params":{"ssid":"\"\"","pswd":"123123 ; passwd -d admin ; echo enable > /sys/class/tty/tty/enable; telnetd"}}
and no change happen, turned on the debug and saw:
Can’t read devices: telnet connection closed
the Mi home app shows me that theres a new firmware update to the my gateway, to version 1.4.7_0160 which is on the list on supported firmware on the documentation.
Should I update to new one and risk it? or is there a way to make this work with the current version that I have?
Thanks
problem solved
Has anyone tweaked with the power of the gateway?
The docs say
Attention: I don’t know if it’s safe to change the channel and power of the gateway. Use at your own risk.
Change Zigbee TX power
command: power 7 # I saw values: 0, 7, 30
However, I cant find any references online where people have changed the power.
Look forward to hearing anyones experience?
Have a look at the official document carefully. I missed out some important details earlier. https://github.com/AlexxIT/XiaomiGateway3
-
Firmware v1.4.6_0043 wont work - you need to enter the open telnet command. See https://gist.github.com/zvldz/1bd6b21539f84339c218f9427e022709
-
After that, I went to HACS and did a reinstall to master version, then changed the Gateway3 firmware to v1.4.6_0030 . See https://github.com/zvldz/mgl03_fw/tree/main/firmware
-
All the zigbee devices for the gateway were visible after the gateway firmware change. Lock the firmware so that it doesnt get upgraded to an unsupported firmware.
I recently bought myself a Gateway 3 to get BLE messages from an Aqara N100 lock, and I’m not using it for anything else(ZHA).
Using factory default FW 1.4.6_0043 and soft hack telnet as described in the documentation I only had entities _BLE and _battery before updating to latest version from Alexxit which also gave me the entity _action.
Now I’m experiencing a unstable connection to the gateway, where it won’t come back after a restart of my HA server. I have tried several hard restarts of the gateway but to no avail(I’m aware that it takes an amount of time to get it back up).
Is there something obvious that I have missed here?
The gateway is blocked from WAN(trust issues). Is this a problem for the BLE functionality of the gateway?
Logger: custom_components.xiaomi_gateway3.core.mini_miio
Source: custom_components/xiaomi_gateway3/core/mini_miio.py:157
Integration: Xiaomi Gateway 3 (documentation, issues)
First occurred: 10:57:29 AM (4 occurrences)
Last logged: 12:09:03 PM
192.168.1.228 | Device offline
192.168.1.228 | Can't send set_ip_info {'ssid': '""', 'pswd': '123123 ; passwd -d admin ; echo enable > /sys/class/tty/tty/enable; telnetd'}
Enabled logging on the gateway also. I can see that ‘dev; false’ is mentioned. Shouldn’t this be enabled? There is problems with the ‘get_properties’ also. This is mentioned as a known problem at GitHub repository.
2021-03-31 12:47:45 DEBUG main SysInfo: {'installation_type': 'Home Assistant OS', 'version': '2021.3.4', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.8.7', 'docker': True, 'arch': 'aarch64', 'os_name': 'Linux', 'os_version': '5.4.83-v8', 'supervisor': '2021.03.6', 'host_os': 'Home Assistant OS 5.12', 'docker_version': '19.03.13', 'chassis': 'embedded'}
2021-03-31 12:47:45 DEBUG gateway3 192.168.1.228 | Start main thread
2021-03-31 12:47:45 DEBUG gateway3 192.168.1.228 | Gateway time offset: -1617185306.6159544
2021-03-31 12:47:45 DEBUG gateway3 192.168.1.228 | Prepare Gateway
2021-03-31 12:47:45 DEBUG gateway3 192.168.1.228 | Version: 1.4.6_0043
2021-03-31 12:47:46 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-31 12:47:46 DEBUG gateway3 192.168.1.228 | Download fixed BT
2021-03-31 12:48:16 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-31 12:48:47 DEBUG mini_miio 192.168.1.228 | timeout 1
2021-03-31 12:48:49 DEBUG mini_miio 192.168.1.228 | timeout 1
2021-03-31 12:48:50 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.1 sec and 2 try
2021-03-31 12:48:50 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.1 sec and 3 try
2021-03-31 12:49:18 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 2.2 sec and 1 try
2021-03-31 12:49:45 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-31 12:49:46 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-31 12:49:53 DEBUG gateway3 192.168.1.228 | MQTT connected
2021-03-31 12:49:53 DEBUG gateway3 192.168.1.228 | gateway <= True
2021-03-31 12:50:16 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.0 sec and 1 try
2021-03-31 12:50:36 DEBUG gateway3 192.168.1.228 | gateway <= {'networkUp': True, 'networkPanId': '0xC282', 'radioTxPower': 7, 'radioChannel': 15}
2021-03-31 12:50:46 DEBUG mini_miio 192.168.1.228 | Send get_properties 128B, recv 128B in 0.0 sec and 1 try
Edit; Installed custom v1.4.6_0012 via Putty, reinstalled everything as well as updated to new version from Alexxit. Still get “Gateway 3 device offline” in log sometimes, but everything seems to work now. Anyone that knows if there are good reasons so use the newer v1.4.7_0160?
Thank you for your post.
please can u show the code how it calculate the checksum for mtd1, mtd5(kernel) mtd6(rootfs)?
i’ve tried crc16_ccitt, crc16_ccitt_false, crc16_modbus and crc16_xmodem, all the crc16 value are not match the one in mtd1.