SamsungTV integration re discover TV any time after reboot #64465
Comments
|
Hey there @escoand, @chemelli74, mind taking a look at this issue as it has been labeled with an integration ( samsungtv documentation |
|
We can check what happens in debug logs; add the following to logger:
default: warning
logs:
homeassistant.components.samsungtv: debug
samsungtvws: debug
samsungctl: debugNote: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub. Simone |
|
Ok. Should i have suppress integration before ? |
|
I think it's good like this ! |
|
Man, you have a log full of errors of any kind ;-) About Samsung, remove the custom component:
I would also remove all configured and ignored SamsungTv, delete the auth in the TV menu, restart HA so to start from a clean situation:
Simone |
|
Yes I know. But I don’t know how 😭 especially for some like this: I take your comment. And repost here. |
|
Ok so, i'm like this : |
|
Quite strange the translation error, but yes try to add the integration confirming the configure Simone |
|
Yes, we talk about this here : So, I add the integration, confirmed in the tv and restart. Seems not discovered anymore 👍 |
|
Selected language is ?
Nice! |
French |
|
Ok, after some day, i have this appear on my notif panel 👍
Did you know if it's a bug ? |
If you try to configure, what happens ? Simone |
|
Desapear 🤨 |
humm, can you share the log ? |
|
Same issue, also the tv keeps asking for approval. This happens on 3 of my samsung screens
(this wil stop ofcourse when you click deny (weiger)) |
|
@landaisbenj , @djansen1987 do you mind updating to 2022.2.0b5 and then
Thx, Simone |
|
Ok so i'm in now : Have this : This log : And i think, this is diagnostics ? |
|
I don't see that option to download the logs |
|
Maybe because you are not in 2022.2.0b5 |
Seems the token is not saved here for some reason. Simone |
|
That is what i am seeing as behaviour
|
Missed the part on asking me to update, i am on: |
I can change volume with ha on the TV. So tv work fine with ha. Maybe it’s because it’s an old model ? (2015). But if if reboot ha, I don’t have a discovery for the moment. |
@djansen1987, there is not a official release to update to. Simone |
Your diagnostics says it's using the new websocket method: which is token based. Simone |
|
Still have the issue {
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2022.2.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.9.7",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Amsterdam",
"os_name": "Linux",
"os_version": "5.10.91",
"supervisor": "2022.01.1",
"host_os": "Home Assistant OS 7.2",
"docker_version": "20.10.9",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"saj_esolar": {
"version": "1.2.9",
"requirements": []
},
"toon_climate": {
"version": "1.0.12",
"requirements": []
},
"afvalbeheer": {
"version": "4.9.2",
"requirements": [
"rsa",
"pycryptodome"
]
},
"toon_boilerstatus": {
"version": "1.0.11",
"requirements": []
},
"custom_component_analytics": {
"version": "0.0.1",
"requirements": []
},
"nodered": {
"version": "1.0.6",
"requirements": []
},
"philips_airpurifier": {
"version": "0.4.0",
"requirements": [
"aioairctrl @ git+https://github.com/betaboon/aioairctrl@v0.2.1"
]
},
"philips_airpurifier_coap": {
"version": "0.7.0",
"requirements": [
"aioairctrl @ git+https://github.com/betaboon/aioairctrl@v0.2.1"
]
},
"hacs": {
"version": "1.21.0",
"requirements": [
"aiogithubapi>=21.11.0"
]
},
"toon_smartmeter": {
"version": "1.0.18",
"requirements": []
}
},
"integration_manifest": {
"domain": "samsungtv",
"name": "Samsung Smart TV",
"documentation": "https://www.home-assistant.io/integrations/samsungtv",
"requirements": [
"getmac==0.8.2",
"samsungctl[websocket]==0.7.1",
"samsungtvws==1.6.0",
"wakeonlan==2.0.1"
],
"ssdp": [
{
"st": "urn:samsung.com:device:RemoteControlReceiver:1"
}
],
"zeroconf": [
{
"type": "_airplay._tcp.local.",
"properties": {
"manufacturer": "samsung*"
}
}
],
"dhcp": [
{
"hostname": "tizen*"
},
{
"macaddress": "8CC8CD*"
},
{
"macaddress": "606BBD*"
},
{
"macaddress": "F47B5E*"
},
{
"macaddress": "4844F7*"
}
],
"codeowners": [
"@escoand",
"@chemelli74"
],
"config_flow": true,
"iot_class": "local_polling",
"is_built_in": true
},
"data": {
"entry": {
"entry_id": "xxxxxx",
"version": 2,
"domain": "samsungtv",
"title": "samsungwktv (QE65Q80TALXXN)",
"data": {
"host": "192.168.xx.xx",
"mac": "70:b1:3d:xx:xx:xx",
"manufacturer": "Samsung",
"method": "websocket",
"model": "QE65Q80TALXXN",
"name": "samsungwktv",
"port": 8002,
"token": "**REDACTED**"
},
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"unique_id": "xxxx",
"disabled_by": null
}
}
} |
@bdraco I compared the UDN in discovery logs to the unique_id in the storage ( |
|
@bdraco I have investigated the UDN issue some more, and I have discovered that (at least on my television) the udn returned by the REST-API (
I think maybe SSDP should be adjusted to use the UDN from the REST-API? |
|
Separate PR created for the UDN mismatch: #67811 |
|
The dev branch has been updated again today. Can you please test again?
{
"domain": "samsungtv",
"name": "Samsung Smart TV",
"version": "2022.4.0-20220308",
"documentation": "https://www.home-assistant.io/integrations/samsungtv",
"...",
}
logger:
default: warning
logs:
homeassistant.components.samsungtv: debug
custom_components.samsungtv: debug
samsungtvws: debug
samsungctl: debug
|
|
I just do your stuf, and don't remove official integration. In log, i have this, but no longueur have 3 integrations.
And now, samsung entity work again : |
|
If the TV is offline, then this is correct behaviour (TimeoutError after 5 seconds) |
|
yes TV is offline, i'm on work. |
|
So for information, after start by HA i have this : logand this appear : |
|
Can you please download the full log, and attach it please (don't copy paste as it is harder to read) |
|
Can you please also attach the latest diagnostics (they contain more information since 2022.3)? |
|
I have created PR #67859. You can test it before it is merged by replacing the |
|
Ok seems to work 😊 all work and discover disappear |
|
For reference can you post log here? |
|
i'm too slow ^^ |
|
it is resolve only re dicover case i confirm re-authentication everydays TV power off, log is "TimeoutError" flug in, do something and require re-authentication i attatch dev log i erase DHCP line because it has macaddress in dev log |
|
when flug out and in, re-authentication is solved change point
attatch log file |
|
This one will be solved when xchwarze/samsung-tv-ws-api#72 is merged and the library is updated inside HA: For this one, I think it is only temporary. Maybe it happens because the TV is turning on (accepting connection, but not yet fully responding): |
|
Issue is still not resolved for me. Still i get an access pop-up every time i turn on the TV |
|
Check the settings on the TV: Device Connection Manager |
This has solved it for me. Thank you! |
The problem
HA discover my samsungtv (i just have one), and so i could add the integration.
But after every restart, HA want to add my tv every time.. (with translation error).
I can ignore, but why this...
[EDIT] After adding twice, i have this after rebooting:
What version of Home Assistant Core has the issue?
core-2021.12.10
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
samsungtv
Link to integration documentation on our website
https://www.home-assistant.io/integrations/samsungtv
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: