2021.11: Icon picker, device links and entity categories

The current update 2021.11.5 is not suggested to me. Last update I got was 2021.11.4 and supervisor tells me, that this is the current version. In the logs I can only find this entry:

21-11-22 02:25:31 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json

If I curl this url I get an valid output.

What could be the reason, that the update is not suggested to me?

Supervisor only checks for updates once a day. If you reload the Supervisor it should see the update I believe.

As I can see in the logs, the supervisor checks every 2 hours for updates.
The check runs without errors and the URL (https://version.home-assistant.io/stable.json) can be queried via curl from the host.
Not only did I restart the supervisor, but the entire HA system and later the entire host as well.
However, I am not offered the update and now I do not know what else to do. No errors can be seen.

fyi: I deleted file updater.json and reloaded supervisor, then I was able to updateā€¦

Hello, may someone get an example for this feature:

Thanks to @ludeeus, the Supervisor integration now has binary sensors that can tell you which add-on is running or not.

Go to Configuration / Integrations and add the Supervisor integration if it is not already listed.

The entities of this integration include binary sensors for each addon that reflect the running state. They may be disabled and you will have to enable them if you want to use them. Do this from the Supervisor integration entities list.

After the last update in HA Core in November , the state of Tuya/Smartlife devices do not update on change of state. I have to reload the Tuya Integration and are back to the correct state. I have about 18 devices in Smartlife , about 5 to 6 behave erratically after the November update. Any one faceinfg this problem ?

Yes:

https://community.home-assistant.io/t/tuya-lights-switches-delay-in-updating-states-is-it-only-me/357889/18

https://community.home-assistant.io/t/tuya-v2-does-not-refresh-states-of-entities/341991

https://github.com/home-assistant/core/issues/59874

https://github.com/home-assistant/core/issues/59911

If you have any additional information, you could add it to the open issues on GitHub. Otherwise, just add a thumbs up to the report. There doesnā€™t yet appear to be a response from the Tuya side on this, which is where most of us suspect the problem lies.

11.5 Broke all Smartthings devices. They all show offline/unavailable

11.5 Also seems to break the Tibber integration. All the entities appear as Unavailable.

The following 3 errors are displayed in the logs:

I considered deleting the integration, and re-add it under a newly generated token, but I really want to avoid doing so as I have some template entities based on attributes from the integration.

Any tips?

Have you reloaded the integration again?
If so, does rolling back to 11.4 get it working again?

Rolling back did not fix it. Others have tried to remove/setup with no luck.

I just deleted the integration and re-added the integration again creating a new token from ST. It is working now. Thanks!

for how long?

Until itā€™s reviewed, the branch went stale and got a new tag 4 days ago, so it should have eyes on it now. Itā€™s a large change though, so it may still be a while depending on how the next review goes.

1 Like

Do you have any two channel dimmers?

Will there be any progress on getting the two channel dimmers working on the Tuya v2 integration? @frenck Is there something I am not doing correctly to get both channels visible.

Hi,

I have lost my Tuya blinds for long time now and kinda lost hope. Iā€™m now trying to get this integration back as it is very useful to me.

Here is the info:

Device Information
Product Name
RJ-Curtain switch
Device ID
45240513ecfabc98f05b
Product Category
qt
Device Status
Online
Activated At
2019-03-25 18:47:09

Device Debugging > JSON Editor:

[
{
ā€œcodeā€: ā€œcontrolā€,
ā€œvalueā€: ā€œopenā€
}
]

Let me know if there is anything more I can do.

You missed the part where I said to open an issue on Github :grinning:

Your device seems to not be supported currently and you are not alone:

You should add your information to that issue

1 Like

Thanks makai, I really did miss that part :wink:

1 Like