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
Hey there @chemelli74, @epenet, mind taking a look at this issue as it has been labeled with an integration (samsungtv) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of samsungtv 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 samsungtv 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
Is this a VLAN issue?
Can my QN55S90DAFXZA not connect to Home Assistant across VLANs?
Additionally, the device connection first time request does not appear on the TV, and the IP Remote feature is enabled in TV network settings.
I have other devices on a different VLAN that can screen / audio share, no issues.
Any help is appreciated!
URL
https://www.home-assistant.io/integrations/samsungtv/
Version:
core-2025.1.4
Additional information
Truenas Scale ElectricEel-24.10.1
Thanks
What version of Home Assistant Core has the issue?
core-2025.1.4
What was the last working version of Home Assistant Core?
core-2025.1.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Samsung Smart TV
Link to integration documentation on our website
https://www.home-assistant.io/integrations/samsungtv
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: