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

G3 not adding to HA, and causing HA (maybe frontend) to reboot. #308

Open
tidegu opened this issue Oct 19, 2024 · 0 comments
Open

G3 not adding to HA, and causing HA (maybe frontend) to reboot. #308

tidegu opened this issue Oct 19, 2024 · 0 comments

Comments

@tidegu
Copy link

tidegu commented Oct 19, 2024

HAOS running on ESXi machine:
Core 2024.10.2
Supervisor 2024.10.2
Operating System 13.2
Frontend 20241002.3

(This issues persisted since many versions back, at least 2014.8.x, and kept HAOS updated did not resolve)

For HAOS, I have two virtual NICs connected to different VLANs - one for home network, the other for IoT devices' network.

G3 is running on modified fw / latest version (4.1.8).

I can telnet to G3 and stream rtsp with no problem, so I believe the G3's setup seems to be fine.

However, whenever I wanna add it to AqaraGateway integration in HA, the HA stops responding and soon after shows a disconnected warnning, which I believe something is restart, maybe the frontend.

I couldn't obtain any logs for identifing the issues, even by enable debug logging for the integration, it doesn't seems to have any logs for this issue.

To reproduce, go HA -> Settings -> Devices & Services -> Aqara Gateway -> Add Entry:

image

After hitting Submit button, error occurs:

image

The camera seems still working fine as I don't see any interruption in the rtsp streaming, telnet to camera from my PC still works fine.

After HA's connection get back, the Add Entry dialog simply gives a "Unknown error" without any further information:

image

I have checked logs for HA Core, Supervisor, Host, and all other possible places that I can find on the front end, and also the debug logging (tried to turn it on before adding the device), non of these places having any trace of the error.

Any further help for identifying the issue or, best of all, how to solve this issue?

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

1 participant