-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Multiple errors happening while updating the device status #22
Comments
Please provide the HomeAssistant version, what type of Soundbar you own and whether all of the features implemented in this integration are also supported in your SmartThings App. |
Do all of the settings you can adjust in the Homeassistant device work for you? |
Okay so the volume does not reflect the real value because you probably have a "max Volume" set. This setting is not "capping" the volume but readjusting the slider of the Can you go through your SmartThings App and exactly list every feature you can adjust there? I'm thinking about adding a service to display the raw json for the update process to make debugging a bit easier, but lets see :) |
And do you have the latest firmware for your Soundbar? |
I don't remember setting it, but now I checked and can't reconfigure the integration to modify it.
I can set what you see in this screenshot: volume, music services, input, equalizer, woofer level, sleep timer.
Seems like a good idea. the API doesn't provide a discovery function to list the available functionality? If not, a JSON structure you can parse to check the available functionality?
Yes, I'm always on latest. But it's been a while since they upgraded it. Last time was the introduction of the eARC functionality for both the soundbar and the QE65Q90R tv. It was a big updated we waited for a long time. Thanks for the help. |
Okay so you're missing the Soundmode feature also in the SmartThings app.
Nope to both. Some things I could probably infer, like if the list for soundmodes is empty, then its likely that there is no soundmode. But others will be difficult, especially since I can't just try it out, as my soundbar supports all of these things. I am thinking about adding a checklist to the configuration, where you can select which features are supported. But I dunno, let's see. |
Really bad API design for Samsung. :(
Yes, it would be a good idea, so we can disable functionalities that aren't available. |
@samuelspagl I have the same errors and some more. I´m using HA 2024.3.1, my soundbar isHW-Q995B with F/W HW-Q995BWWB-1010.0. I can set almost everything that I can set in the app. And i often get the following message:
And this errors:
The following warning has been appearing more frequently recently:
|
Hi @Headkillah, But do the controls generally work for you? (Despite what the log is saying?) Which version of the integration are you using? Because this should be fixed in the latest master release (0.3.0) |
Hey @samuelspagl Yeah, generally the controls are working :) I had version 0.2.0 installed and did not see (no notification from HA) that version 0.3.0 was released. Now I have the new version and will see if the errors continue to occur. I will post an update if something happens... :) |
With 0.3.0 i'm getting this errors:
|
Same here, my soundbar is the HW-Q990C running the latest firmware (1004.034): Logger: homeassistant.components.media_player Updating samsung_soundbar media_player took longer than the scheduled update interval 0:00:10
|
Certain features may be enabled, disabled, or have varying options depending on the current sound mode. Does your integration refresh the list of available modes periodically, or is it only updated once when the soundbar is added? EDIT: Just realized that the woofer level setting is just gone from the Smartthings app, they must have removed that in the latest firmware update EDIT2: Sorry, the Woofer level setting is still present, but it can only be adjusted when the soundbar is turned on. When the soundbar is off, this setting is not visible in the app. That could be the reason it fails to update. |
That could certainly be true. I'll try to take a closer look at it as soon as possible, still I have quite a few things on my plate currently :) |
Hi there, So some things changes on Samsungs side (still in need to confirm whether it is a bug or a feature), and therefore the update process of the custom capabilities is broken. This happened probably on the 26th of march. At the current timing, your issue is probably linked to #26. The current plan is to enhance the configuration settings quite a bit, so that you can maybe even, let the entities be created but can disable just the update process, or to add services for those custom capabilities (like eq, soundmodes etc.). |
Same issue here with a lot of counter errors. |
@thearchitectuk Yeah this is common 😅, please take a look at #26 and install the latest alpha version of this integration. This version features a new settings workflow, where you can enable / disable the entities (and therefore the update process) for the custom capabilities. I also added service calls for the custom capabilities to still enable setting the values. I still wait for a response from Samsung 😅, but until that time, I can't do much about it. |
Thanks! I'm a bit naive with all this, how do I update 0.3.0 to an Alpha version please? Sorry, I can't work out how.
Cheers Samuel 🙂
…________________________________
From: Samuel Spagl ***@***.***>
Sent: 22 April 2024 2:24 PM
To: samuelspagl/ha_samsung_soundbar ***@***.***>
Cc: Arko ***@***.***>; Mention ***@***.***>
Subject: Re: [samuelspagl/ha_samsung_soundbar] Multiple errors happening while updating the device status (Issue #22)
@thearchitectuk<https://github.com/thearchitectuk> Yeah this is common 😅, please take a look at #26<#26> and install the latest alpha version of this integration.
This version features a new settings workflow, where you can enable / disable the entities (and therefore the update process) for the custom capabilities. I also added service calls for the custom capabilities to still enable setting the values.
I still wait for a response from Samsung 😅, but until that time, I can't do much about it.
—
Reply to this email directly, view it on GitHub<#22 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AISUGWUYRN73IWDILIB3GVTY6UFPLAVCNFSM6AAAAABESHUAWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRZGQYTMMBUGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Don't worry :) Here's the link to the HACS documentation: https://hacs.xyz/docs/faq/select_version/ |
Thanks Samuel! I have updated, however, it only works if all 4 entities are disabled. I thought you only had to disable one to fix the logging issue? If I just have 2 enabled, I get this error at the top right (behind the popped up box). Did I miss something? :) Thanks bud. |
I will close this with the merge of #28. Feel free to reopen if something is still left. |
Description
This is an issue @alexdelprete mentioned in another issue.
I installed this a couple of days ago, and the log has become unreadable (too many errors) ever since. I have a LOT of errors/warnings, and don't know if it's normal having all these. Maybe they sould not be errors, but I didn't look at the code yet to be sure about that:
Originally posted by @alexdelprete in #20 (comment)
The text was updated successfully, but these errors were encountered: