The lights always get "Became unavailable" error

[chrislcf]

I am using the philips.light.bceiling1 (飞利浦智睿吸顶灯 简约版 卧室40W). Unfortunately, the lights always get "Became unavailable" error many times in a day. But it reconnect very soon.

I checked the full logs and here is the logs at 22/10 1:43PM

2022-10-22 13:43:24.175 WARNING (SyncWorker_5) [custom_components.xiaomi_miot.core.xiaomi_cloud] Request xiaomi api: miotspec/prop/get {'params': [{'did': 'blt.3.1b2b8abjgec00', 'siid': 2, 'piid': 1}, {'did': 'blt.3.1b2b8abjgec00', 'siid': 2, 'piid': 2}, {'did': 'blt.3.1b2b8abjgec00', 'siid': 3, 'piid': 1}]} failed, response: None
2022-10-22 13:43:27.177 WARNING (SyncWorker_1) [custom_components.xiaomi_miot.core.xiaomi_cloud] Request xiaomi api: v2/message/v2/typelist {} failed, response: None
2022-10-22 13:43:27.179 WARNING (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 10483206 failed: {}
2022-10-22 13:43:54.404 WARNING (SyncWorker_1) [custom_components.xiaomi_miot.core.xiaomi_cloud] Request xiaomi api: miotspec/prop/get {'params': [{'did': '360850374', 'siid': 2, 'piid': 1}, {'did': '360850374', 'siid': 2, 'piid': 2}, {'did': '360850374', 'siid': 2, 'piid': 3}, {'did': '360850374', 'siid': 2, 'piid': 4}]} failed, response: None
2022-10-22 13:44:24.130 WARNING (SyncWorker_2) [custom_components.xiaomi_miot.core.xiaomi_cloud] Request xiaomi api: miotspec/prop/get {'params': [{'did': 'blt.3.1b2b8abjgec00', 'siid': 2, 'piid': 1}, {'did': 'blt.3.1b2b8abjgec00', 'siid': 2, 'piid': 2}, {'did': 'blt.3.1b2b8abjgec00', 'siid': 3, 'piid': 1}]} failed, response: None
2022-10-22 13:44:24.423 WARNING (SyncWorker_1) [custom_components.xiaomi_miot.core.xiaomi_cloud] Request xiaomi api: miotspec/prop/get {'params': [{'did': '360850374', 'siid': 2, 'piid': 1}, {'did': '360850374', 'siid': 2, 'piid': 2}, {'did': '360850374', 'siid': 2, 'piid': 3}, {'did': '360850374', 'siid': 2, 'piid': 4}]} failed, response: None

[al-one]

response: None means that your HA may not be able to access Xiaomi Cloud API, please check your network environment or DNS configuration.
The latest commit has added support for local integration for this device, please update to the master branch and try again.

[al-one]

Does it work ?