Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data not populating after updating to Core 2024.3.0 #236

Open
pax0707 opened this issue Mar 7, 2024 · 12 comments
Open

Data not populating after updating to Core 2024.3.0 #236

pax0707 opened this issue Mar 7, 2024 · 12 comments

Comments

@pax0707
Copy link

pax0707 commented Mar 7, 2024

On 0.2.0, updated to 0.2.2

Name: Camera-Hub-G2H-2
Model: lumi.camera.gwagl02
Hostname: Camera-Hub-G2H-2.local

ConnectionResetError: Cannot write to closing transport
2024-03-07 14:23:03.155 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-03-07 17:48:06.508 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'aqara_gateway' at custom_components/aqara_gateway/core/shell.py, line 88: time.sleep(.5), please create a bug report at https://github.com/niceboygithub/AqaraGateway/issues
2024-03-07 17:48:37.040 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'aqara_gateway' at custom_components/aqara_gateway/core/shell.py, line 90: time.sleep(.5), please create a bug report at https://github.com/niceboygithub/AqaraGateway/issues
2024-03-07 17:49:20.512 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'aqara_gateway' at custom_components/aqara_gateway/core/shell.py, line 88: time.sleep(.5), please create a bug report at https://github.com/niceboygithub/AqaraGateway/issues
2024-03-07 17:49:51.045 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'aqara_gateway' at custom_components/aqara_gateway/core/shell.py, line 90: time.sleep(.5), please create a bug report at https://github.com/niceboygithub/AqaraGateway/issues
2024-03-07 17:49:51.568 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
@niceboygithub
Copy link
Owner

it is just warning and not blcok issue now.
Will fix it in the future.

@pax0707
Copy link
Author

pax0707 commented Mar 8, 2024

All entities for all devices report as unknown.

Got this from debug log:

 2024-03-07 18:01:38  DEBUG  main  SysInfo: {'installation_type': 'Home Assistant OS', 'version': '2024.3.0', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.12.2', 'docker': True, 'arch': 'x86_64', 'os_name': 'Linux', 'os_version': '6.6.16-haos', 'user': 'root', 'supervisor': '2024.02.1', 'host_os': 'Home Assistant OS 12.0', 'docker_version': '24.0.7', 'chassis': 'vm'}
 2024-03-07 18:01:49  DEBUG  gateway  172.16.3.45: mosquitto is not running as public!
 2024-03-07 18:03:02  DEBUG  gateway  172.16.3.45: mosquitto is not running as public!
 2024-03-07 18:04:14  DEBUG  gateway  172.16.3.45: mosquitto is not running as public!

Need to do some googling.

@almirus
Copy link

almirus commented Mar 8, 2024

@pax0707 I experienced this immediately after updating to version 2024.3.0 (the plugin remained at version 0.2.0), then I updated to 0.2.2 and completely rebooted my machine with HA, and everything started working.

@pax0707
Copy link
Author

pax0707 commented Mar 8, 2024

@pax0707 I experienced this immediately after updating to version 2024.3.0 (the plugin remained at version 0.2.0), then I updated to 0.2.2 and completely rebooted my machine with HA, and everything started working.

Restarted HASS, and restarted the VM it's running on, didn't help.

@almirus
Copy link

almirus commented Mar 8, 2024

Did you restart the camera?

@pax0707
Copy link
Author

pax0707 commented Mar 8, 2024

A few times while testing.

@pax0707
Copy link
Author

pax0707 commented Mar 9, 2024

I have reverted the VM to a backup with 2024.2.5 and everything is working.
2024.3.0 broke something.

@almirus
Copy link

almirus commented Mar 9, 2024

@pax0707 I also see in the log that mosquitto is "not responding", but if I trigger the event directly on the zigbee lock (connected via g2h), everything works.

2024-03-09 16:16:15  DEBUG  main  SysInfo: {'installation_type': 'Home Assistant OS', 'version': '2024.3.0', 'dev': False, 'hassio': True, 'virtualenv': False, 'python_version': '3.12.2', 'docker': True, 'arch': 'x86_64', 'os_name': 'Linux', 'os_version': '6.6.16-haos', 'user': 'root', 'supervisor': '2024.02.1', 'host_os': 'Home Assistant OS 12.0', 'docker_version': '24.0.7', 'chassis': 'vm'}
 2024-03-09 16:16:28  DEBUG  gateway  192.168.0.34: mosquitto is not running as public!
 2024-03-09 16:16:43  DEBUG  gateway  192.168.0.34: mosquitto is not running as public!
 2024-03-09 16:17:23  DEBUG  gateway  192.168.0.34: lumi.54ef44100053bb2c aqara.lock.bzacn4 <= {'door': 5, 'timestamp': 1709990241} [1709990243.248671]
 2024-03-09 16:17:23  DEBUG  gateway  192.168.0.34: lumi.54ef44100053bb2c aqara.lock.bzacn4 <= {'latch_state': 1, 'timestamp': 1709990241} [1709990243.3412132]
 2024-03-09 16:17:26  DEBUG  gateway  192.168.0.34: lumi.54ef44100053bb2c aqara.lock.bzacn4 <= {'door': 3, 'timestamp': 1709990244} [1709990246.2171092]
 2024-03-09 16:17:26  DEBUG  gateway  192.168.0.34: lumi.54ef44100053bb2c aqara.lock.bzacn4 <= {'latch_state': 0, 'timestamp': 1709990244} [1709990246.3110874]

@pax0707
Copy link
Author

pax0707 commented Mar 15, 2024

Also #239

@pax0707
Copy link
Author

pax0707 commented Apr 1, 2024

Did anyone try if any of these updates fix the issue?

image

@peros550
Copy link

peros550 commented Apr 9, 2024

same issue with latest updates

@pax0707
Copy link
Author

pax0707 commented Apr 15, 2024

I have 2 G2H cameras. One is configured, and one is not (original untoughed).
What happens is that the IP of the configured camera gets replaced by the IP of the unconfigured camera.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants