search

AlexxIT / XiaomiGateway3

Home Assistant custom component for control Xiaomi Multimode Gateway (aka Gateway 3), Xiaomi Multimode Gateway 2, Aqara Hub E1 on default firmwares over LAN
https://github.com/AlexxIT/Blog
MIT License
2.47k stars 347 forks source link

Fix receiving values from LYWSD03MMC after ~6-8 hours #972

Closed monsterflo closed 1 year ago

monsterflo commented 1 year ago

Hello, on Home Assistant 2023.2.2 with v3.1.0 of the integration Home Assistant constantly loses contact to the LYWSD03MMC (Temp/Humidity) sensors after approx. 6 to 8 hours. Restarting Home Assistant solves the issue for another 6-8 hours. Logs are empty.

Any solution is appreciated.

REgards Florian

AlexxIT commented 1 year ago

You need to collect component debug logs

monsterflo commented 1 year ago

Good evening. Here is everything linked to the xiaomi3 addon:

2023-02-06 15:17:18.793 DEBUG (MainThread) [custom_components.xiaomi_gateway3] Loaded from cache 17 devices
2023-02-06 15:17:29.399 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] Timeout while requesting MIoT api /v2/home/device_list_page
2023-02-06 15:17:29.402 DEBUG (MainThread) [custom_components.xiaomi_gateway3] Login to MiCloud for xxx@xxx.de
2023-02-06 15:17:29.627 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] MiCloud step1
2023-02-06 15:17:29.769 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] MiCloud step2
2023-02-06 15:17:30.057 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] MiCloud step3
2023-02-06 15:17:31.505 DEBUG (MainThread) [custom_components.xiaomi_gateway3] Loaded from MiCloud 17 devices

2023-02-06 19:27:36.647 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.0.44 | Can't prepare gateway
Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway/__init__.py", line 177, in prepare_gateway
async with shell.Session(self.host) as sh:
File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 29, in __aenter__
await self.connect()
File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 36, in connect
self.reader, self.writer = await asyncio.wait_for(self.coro, 5)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
transport, _ = await loop.create_connection(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1064, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
return await fut
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 535, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.0.44', 23)

The hub and all linked sensors are reachable from the Xiaomi Android-App

Regards Florian

AlexxIT commented 1 year ago

Looks like your hub not reachable from Home Assistant

tothak commented 1 year ago

Hi,

I have the same issue.

Regards, Ákos

vmannoor commented 1 year ago

I've the same issue. I face the same connectivity issues with xiaomi LYWSD03MMC sensors as well as qingping sensors (door, motion & light sensors)

TischenkoArseny commented 1 year ago

I have the same issue, rollback to 3.0.1 resolve problem.

AlexxIT commented 1 year ago

Still nothing useful from you to solve the problem

TischenkoArseny commented 1 year ago

What information can I provide to solve the problem?

vmannoor commented 1 year ago

I have the same issue, rollback to 3.0.1 resolve problem.

I also rolled back to 3.0.1, seems like it solved the issue. It's only been 3 hours, so I'll keep monitoring.

dth97410 commented 1 year ago

I have the same problem for a few days...the data from the sensors do not go back to the home assistant "unavailable" when I reload or restart the integration it works again for a few hours then nothing.

vmannoor commented 1 year ago

Still nothing useful from you to solve the problem

I updated again to 3.1.0, trying to help you so that you can help us). This is what I got from the log file. 

2023-02-08 15:43:08.148 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.kitchen_illuminance has device class illuminance, state class measurement and unit lx thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:43:08.154 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.kitchen_motion_battery has device class battery, state class measurement and unit % thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:43:08.157 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.582d34605599_idle_time has device class None, state class measurement and unit s thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:39.467 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.toilet_illuminance has device class illuminance, state class measurement and unit lx thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:39.475 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.toilet_motion_battery has device class battery, state class measurement and unit % thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:51.198 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.bedroom_illuminance has device class illuminance, state class measurement and unit lx thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:51.202 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.bedroom_motion_battery has device class battery, state class measurement and unit % thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:51.206 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.bedroom_motion_idle_time has device class None, state class measurement and unit s thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

I enabled debug logs in the integration configuration. logs below:

2023-02-08 15:39:53 [D] SysInfo: {'installation_type': 'Home Assistant Supervised', 'version': '2023.2.3', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.10.7', 'docker': True, 'arch': 'x86_64', 'timezone': 'Europe/Kiev', 'os_name': 'Linux', 'os_version': '5.10.0-21-amd64', 'user': 'root', 'supervisor': '2023.01.1', 'host_os': 'Debian GNU/Linux 11 (bullseye)', 'docker_version': '23.0.0', 'chassis': 'desktop', 'xiaomi_gateway3_version': '3.1.0 (c33660c)'}
2023-02-08 15:39:53 [D] Loaded from cache 44 devices
2023-02-08 15:39:53 [D] 192.168.1.3 [BASE] Start main loop
2023-02-08 15:39:55 [D] 192.168.1.3 [BASE] Prepare gateway mgw with fw 1.5.4_0090
2023-02-08 15:39:56 [D] 192.168.1.3 [BASE] openmiio_agent: The latest version is launched
2023-02-08 15:39:56 [D] 192.168.1.3 [BASE] 54ef4423834d (lumi.gateway.mgl03) setup gateway ZNDMWG03LM: alarm, command, data, cloud_link, led, gateway
2023-02-08 15:39:56 [D] 192.168.1.3 [MIOT] 54ef4423834d (lumi.gateway.mgl03) read {'mi_spec': [{'siid': 3, 'piid': 1}, {'siid': 3, 'piid': 22}]}
2023-02-08 15:39:56 [D] Loaded from MiCloud 44 devices
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c138164cf1 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c138b08886 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c138301293 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c138a7496a (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34604fad (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 54ef44e394f3 (2147) setup ble SJWS01LM: water_leak, battery, action, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 54ef44e3893e (2147) setup ble SJWS01LM: water_leak, battery, action, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 50ec50d10968 (2038) setup ble MJYD02YL-A: battery, light, motion, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] b87c6fa91290 (1116) setup ble V-SK152: power, temperature, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34603db4 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c138694dd8 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c1380e0d52 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34605599 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34604eb8 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d346023e3 (982) setup ble CGH1: action, battery, contact, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34600a7f (982) setup ble CGH1: action, battery, contact, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34603f97 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d34600986 (982) setup ble CGH1: action, battery, contact, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d3460257d (982) setup ble CGH1: action, battery, contact, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d3460097a (982) setup ble CGH1: action, battery, contact, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d346054bc (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] a4c13809efa4 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] 582d346023db (982) setup ble CGH1: action, battery, contact, ble
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] Applied 0 patches to daemons
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] MQTT connected
2023-02-08 15:39:57 [D] 192.168.1.3 [BASE] b87c6fa91290 (1116) poll state power
2023-02-08 15:40:27 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:40:57 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:41:27 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:41:57 [D] 192.168.1.3 [BASE] 582d34600a7f (982) set device offline
2023-02-08 15:41:57 [D] 192.168.1.3 [BASE] 582d346023db (982) set device offline
2023-02-08 15:41:57 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:42:16 [D] 192.168.1.3 [BLEE] a4c138a7496a (1371) recv {'battery': 100}
2023-02-08 15:42:28 [D] 192.168.1.3 [BASE] a4c138694dd8 (1371) set device offline
2023-02-08 15:42:28 [D] 192.168.1.3 [BASE] 582d3460097a (982) set device offline
2023-02-08 15:42:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:42:31 [D] 192.168.1.3 [BLEE] 50ec50d10968 (2038) recv {'light': False}
2023-02-08 15:42:32 [D] 192.168.1.3 [BASE] Gateway time offset: -0.35645341873168945
2023-02-08 15:42:53 [D] 192.168.1.3 [BLEE] 50ec50d10968 (2038) recv {'battery': 2}
2023-02-08 15:42:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:43:08 [D] 192.168.1.3 [BLEE] 582d34605599 (2691) recv
2023-02-08 15:43:09 [D] 192.168.1.3 [BLEE] 582d34605599 (2691) recv {'illuminance': 25}
2023-02-08 15:43:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:43:39 [D] 192.168.1.3 [BLEE] a4c138b08886 (1371) recv {'humidity': 43}
2023-02-08 15:43:53 [D] 192.168.1.3 [BLEE] 582d346023e3 (982) recv {'battery': 16}
2023-02-08 15:43:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:44:21 [D] 192.168.1.3 [BLEE] 582d34605599 (2691) recv {'light': False}
2023-02-08 15:44:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:44:39 [D] 192.168.1.3 [BLEE] 582d34604eb8 (2691) recv
2023-02-08 15:44:40 [D] 192.168.1.3 [BLEE] 582d34604eb8 (2691) recv {'illuminance': 0}
2023-02-08 15:44:51 [D] 192.168.1.3 [BLEE] 582d346054bc (2691) recv
2023-02-08 15:44:52 [D] 192.168.1.3 [BLEE] 582d346054bc (2691) recv {'illuminance': 52}
2023-02-08 15:44:53 [D] 192.168.1.3 [BLEE] a4c138694dd8 (1371) recv {'battery': 50}
2023-02-08 15:44:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:45:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:45:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:46:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:46:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:47:09 [D] 192.168.1.3 [BLEE] a4c1380e0d52 (1371) recv {'humidity': 38}
2023-02-08 15:47:23 [D] 192.168.1.3 [BLEE] 582d34603f97 (2691) recv
2023-02-08 15:47:24 [D] 192.168.1.3 [BLEE] 582d34603f97 (2691) recv {'illuminance': 5}
2023-02-08 15:47:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:47:33 [D] 192.168.1.3 [BASE] Gateway time offset: -0.5963811874389648
2023-02-08 15:47:52 [D] 192.168.1.3 [BLEE] a4c138694dd8 (1371) recv {'humidity': 43}
2023-02-08 15:47:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:48:28 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-02-08 15:48:58 [D] 192.168.1.3 [BASE] b87c6fa91290 (1116) poll state power
2023-02-08 15:48:58 [D] 192.168.1.3 [BASE] Run zigbee parent scan process
tothak commented 1 year ago

Well, I downgraded to 3.0.1 6 hours ago, and now it went offline again, so maybe it's not the integration, but something else....

TischenkoArseny commented 1 year ago

I also update back to 3.1.0, enable debug for component and wait for problem. Now all my ble sensors became unvailable, but no any information at this time in log, only this part in 2 hours after update component

2023-02-08 14:26:34.920 WARNING (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.10.157 | Can't update gateway stats
Traceback (most recent call last):
  File "/config/custom_components/xiaomi_gateway3/core/gateway/gate_mgw.py", line 111, in gw3_update_serial_stats
    async with shell.Session(self.host) as sh:
  File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 30, in __aenter__
    return await self.login()
  File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 44, in login
    resp: bytes = await asyncio.wait_for(coro, 3)
  File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.10/asyncio/streams.py", line 614, in readuntil
    raise exceptions.IncompleteReadError(chunk, None)
asyncio.exceptions.IncompleteReadError: 12 bytes read on a total of undefined expected bytes
vmannoor commented 1 year ago

my log has similar error warning from another open issue: https://github.com/AlexxIT/XiaomiGateway3/issues/971#issue-1571396490.

Sensor sensor.0x54ef4410005a71d4_smoke_density has device class None, state class measurement and unit % obs/ft thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

sensor.bedroom_motion_idle_time has device class None, state class measurement and unit s thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

vmannoor commented 1 year ago

I rolled back to 3.0.0, stable for the last 20+ hours.

AlexxIT commented 1 year ago

@vmannoor thanks for logs. All this BLE devices unavailable?

it has the non-numeric value: unavailable fixed in master version. You can check if it helps you.

vmannoor commented 1 year ago

@vmannoor thanks for logs. All this BLE devices unavailable?

it has the non-numeric value: unavailable fixed in master version. You can check if it helps you.

Yes, all the sensors go unavailable. But now I'm on 3.0.0 for the last 2 days and everything works perfectly.

monsterflo commented 1 year ago

Hello, i rolled back to 3.0.0 but the "error" remains. No values from the sensors after a few hours. The hub is reachable in the Xiaomi app.

Here is my log:


2023-02-11 22:19:38.493 WARNING (MainThread) [custom_components.xiaomi_gateway3.core.mini_miio] 192.168.0.44 | Device offline
2023-02-11 22:20:08.932 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.0.44 | Can't prepare gateway
Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway/__init__.py", line 177, in prepare_gateway
async with shell.Session(self.host) as sh:
File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 29, in __aenter__
await self.connect()
File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 36, in connect
self.reader, self.writer = await asyncio.wait_for(self.coro, 5)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
transport, _ = await loop.create_connection(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1064, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
return await fut
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 535, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.0.44', 23)
2023-02-11 22:49:30.303 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 334, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"

Regards Florian

dth97410 commented 1 year ago

Hello, still no solution found for this bug? I have all my sensors unavailable.

AlexxIT commented 1 year ago

@monsterflo I hope problem will be resolved in next release

AlexxIT commented 1 year ago

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v3.2.0

vmannoor commented 1 year ago

@AlexxIT, unfortunately the issue is not resolved. I updated to the latest version and all my sensors went to 'unavailable' after a few hours and I can't fix the issue even after restart of both gateway and HA. log below:

2023-05-08 10:29:58.235 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] Prepare gateway mgw with fw 1.5.4_0090
2023-05-08 10:29:58.468 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] openmiio_agent: The latest version is launched
2023-05-08 10:29:58.613 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 54ef4423834d (lumi.gateway.mgl03) setup gateway ZNDMWG03LM: alarm, command, data, cloud_link, led, gateway
2023-05-08 10:29:58.614 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] Init Zigbee in memory storage
2023-05-08 10:29:58.617 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [MIOT] 54ef4423834d (lumi.gateway.mgl03) read {'mi_spec': [{'siid': 3, 'piid': 1}, {'siid': 3, 'piid': 22}]}
2023-05-08 10:29:59.031 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 54ef44e394f3 (2147) setup ble SJWS01LM: water_leak, battery, action, ble
2023-05-08 10:29:59.034 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 54ef44e3893e (2147) setup ble SJWS01LM: water_leak, battery, action, ble
2023-05-08 10:29:59.035 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 50ec50d10968 (2038) setup ble MJYD02YL-A: battery, light, motion, idle_time, ble
2023-05-08 10:29:59.036 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] b87c6fa91290 (1116) setup ble V-SK152: power, temperature, ble
2023-05-08 10:29:59.037 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c138301293 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.038 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d346023e3 (982) setup ble CGH1: action, battery, contact, ble
2023-05-08 10:29:59.039 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c138a7496a (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.040 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c138164cf1 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.041 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34604eb8 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.041 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c138b08886 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.042 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34600986 (982) setup ble CGH1: action, battery, contact, ble
2023-05-08 10:29:59.043 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d346113ef (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.044 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34604fad (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.045 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34603f97 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.046 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34603db4 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.047 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d3460097a (982) setup ble CGH1: action, battery, contact, ble
2023-05-08 10:29:59.047 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c138694dd8 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.048 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34605599 (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.049 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c13809efa4 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.049 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d3460257d (982) setup ble CGH1: action, battery, contact, ble
2023-05-08 10:29:59.049 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d346054bc (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.050 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d34600a7f (982) setup ble CGH1: action, battery, contact, ble
2023-05-08 10:29:59.050 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d346023db (982) setup ble CGH1: action, battery, contact, ble
2023-05-08 10:29:59.051 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] 582d3461151a (2691) setup ble CGPR1: motion, light, illuminance, battery, idle_time, ble
2023-05-08 10:29:59.051 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] a4c1380e0d52 (1371) setup ble LYWSD03MMC: temperature, humidity, battery, ble
2023-05-08 10:29:59.051 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] Init Bluetooth in memory storage
2023-05-08 10:29:59.450 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] Applied 3 patches to daemons
2023-05-08 10:29:59.463 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] MQTT connected
2023-05-08 10:30:18.702 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [LUMI] 54ef4423834d (lumi.gateway.mgl03) recv {'cloud_link': True}
2023-05-08 10:30:29.826 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] Run zigbee parent scan process
2023-05-08 10:30:59.829 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.gateway] 192.168.1.3 [BASE] Run zigbee parent scan process
ADMiNZ commented 1 year ago

Same problem. Status is always Unknown (zigbee JTYJ-GD-01LM/BW (lumi.sensor_smoke) Honeywell)