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

BT-Proxy doesn't work from another network #117574

Closed
perpaul opened this issue May 16, 2024 · 6 comments
Closed

BT-Proxy doesn't work from another network #117574

perpaul opened this issue May 16, 2024 · 6 comments

Comments

@perpaul
Copy link

perpaul commented May 16, 2024

The problem

I have 2 networks connected via a Wireguard VPN. HA is in network A, BT-proxy in network B. BT-proxy can be reached from network A: updates, logs, etc... However, BT-proxy does not recognize any BT-devices in its area.
If I connect the BT-proxy directly to network A, BT- devices are recognized.

What version of Home Assistant Core has the issue?

2024.5.3

What was the last working version of Home Assistant Core?

Never

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ESPHome

Link to integration documentation on our website

https://www.home-assistant.io/integrations/esphome/

Diagnostics information

home-assistant_esphome_2024-05-16T15-19-07.753Z.zip

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @OttoWinter, @jesserockz, @kbx81, @bdraco, mind taking a look at this issue as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of esphome can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign esphome Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


esphome documentation
esphome source
(message by IssueLinks)

@bdraco
Copy link
Member

bdraco commented May 16, 2024

2024-05-12 01:39:01.565 ERROR (SyncWorker_37) [homeassistant.util.logging] Exception in _handle_event when dispatching 'alexa_media_p**********o@c******': ({'queue_state': {'dopplerId': {'deviceSerialNumber': 'G2A0V7049425020F', 'deviceType': 'A18O6U1UQFJ0XK'}, 'changeType': 'STATUS_CHANGED', 'playBackOrder': 'NORMAL', 'loopMode': 'LOOP_QUEUE', 'trackOrderChanged': False, 'destinationUserId': 'A3446RI8ARAR5Y'}},)
Traceback (most recent call last):
  File "/config/custom_components/alexa_media/switch.py", line 217, in _handle_event
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1008, in async_write_ha_state
    self.hass.verify_event_loop_thread("async_write_ha_state")
  File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread
    frame.report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report
    _report_integration(what, integration_frame, level, error_if_integration)
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration
    raise RuntimeError(
RuntimeError: Detected that custom integration 'alexa_media' calls async_write_ha_state from a thread at custom_components/alexa_media/switch.py, line 217: self.async_write_ha_state(). Please report it to the author of the 'alexa_media' custom integration.

@bdraco
Copy link
Member

bdraco commented May 16, 2024

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/roborock/api.py", line 283, in on_message_received
    listener(status)
  File "/config/custom_components/roborock/device.py", line 129, in _update_from_listener
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1008, in async_write_ha_state
    self.hass.verify_event_loop_thread("async_write_ha_state")
  File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread
    frame.report(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report
    _report_integration(what, integration_frame, level, error_if_integration)
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration
    raise RuntimeError(
RuntimeError: Detected that custom integration 'roborock' calls async_write_ha_state from a thread at custom_components/roborock/device.py, line 129: self.async_write_ha_state(). Please report it to the author of the 'roborock' custom integration.

@bdraco
Copy link
Member

bdraco commented May 16, 2024

It looks like you have quite a few integrations doing non thread-safe operations. I would advise getting those reported and worked out first as your log is so busy its nearly impossible to figure out what is going on or if the problem is because the system is unstable.

Please follow the guide here: https://community.home-assistant.io/t/2024-5-tracking-down-instability-issues-caused-by-integrations/724441

The specific sections:

  • Using Home Assistant's built-in debug mode in 2024.5.x or later (preferred)
  • Enabling asyncio debug mode at run time (preferred)

@perpaul
Copy link
Author

perpaul commented May 16, 2024

Thank you for the hints. I will forward them accordingly

@perpaul
Copy link
Author

perpaul commented May 20, 2024

I installed a new HA instance with minimal add-ons. In this constellation, the BT proxy works between the two networks.

@perpaul perpaul closed this as completed May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants