You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The integration appears active as it can be seen under the device filter selection, but no devices are being show. It also, does not appear in the Devices and Services Tab as would be expected.
I have NMAP, Netgear and Google WiFi Integrations alredy in place, so I can see all devices on the network, but as the ISPs router I would like to identify which devices are connected to which AP/Router at any given moment.
What version of Home Assistant Core has the issue?
core-2024.7.0
What was the last working version of Home Assistant Core?
2024-07-04 20:04:57.869 INFO (SyncWorker_52) [homeassistant.components.bt_smarthub.device_tracker] Scanning
2024-07-04 20:04:57.995 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:57.997 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:58.022 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:58.041 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:58.048 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:58.055 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:58.058 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
2024-07-04 20:04:58.061 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.xx_xx_xx_xx_xx_xx
Additional information
No response
The text was updated successfully, but these errors were encountered:
Hey there @typhoon2099, mind taking a look at this issue as it has been labeled with an integration (bt_smarthub) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of bt_smarthub 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 bt_smarthub 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.
The problem
The integration appears active as it can be seen under the device filter selection, but no devices are being show. It also, does not appear in the Devices and Services Tab as would be expected.
I have NMAP, Netgear and Google WiFi Integrations alredy in place, so I can see all devices on the network, but as the ISPs router I would like to identify which devices are connected to which AP/Router at any given moment.
What version of Home Assistant Core has the issue?
core-2024.7.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
BT Smart Hub
Link to integration documentation on our website
https://www.home-assistant.io/integrations/bt_smarthub
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: