-
Notifications
You must be signed in to change notification settings - Fork 10
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
Confirm the new connection dialog does not show up on my MU65 Sammlung TV #6
Comments
From @C4b4nossi on May 13, 2018 20:52 I have the same problem: the Dialog to confirm the new connection does NOT show up on the TV (UE55H6470SS) - is this related to the protocol or the TV itself? TV is connected with WLAN; I have only 2 Devices in the connection lists of the TV and deleted all other old connections |
Same issue at my installation. Samsung JS9090 from 2015 and it's connected with cable LAN |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. |
From @tippmam on February 18, 2018 5:50
Hey, installed your Adapter within my ioBroker Installation which is running on a Synology NAS via Docker. After the Installation the Adapter discovered my TV's IP and i can see the TV's Objects. I'm not able to send any command to my TV or get any "live" Information. I think this is, because the "confirm dialog" did not come up on my TV like it should, after I installed the Adapter.
Kind Regards,
Michael
Copied from original issue: soef/ioBroker.samsung#17
The text was updated successfully, but these errors were encountered: