After Update 2023.11.0 about rtetempo

[Binifada1956]

Hello and thank you for the quick response! French unfortunately not better than English, I am German 🤷‍♂️ I use an automation and a script that switches the respective tariffs blue, white, red etc.. I think it's the device ID. This will probably be changed by the update. This behaviour has also been noted in the release discussions. See https://community.home-assistant.io/t/2023-11-to-do-add-release-title/634647/33 Cdt RolfAm 02.11.2023 um 12:38 schrieb Edouard Hur ***@***.***>: Hello, What do you mean by "no Function" ? Have they stopped working ? Which sensors are you using as triggers ? PS: I always answer in the language of the question but we can do this in french ;) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Binifada1956]

ok, I'll adjust my automation and the script. I'll know more the next time I switch between HP and HC. Many thanks Cdt Rolf

[hekmon]

Hello,

What do you mean by "no Function" ? Have they stopped working ? Which sensors are you using as triggers ?

PS: I always answer in the language of the question but we can do this in french ;)

[hekmon]

What is bothering me is that I do not have a single error log that would point to a specific problem and so a specific solution.

IDs have not been changed by the extension so if HA has changed the way is generate its IDs, I am afraid that I can not do much to get the old ones back.

I need to dig this issue to better understand what is going on.

[hekmon]

I did the upgrade to 2023.11 but it seems that my entities did not changed IDs (or I would not have history for them) :

And my automatisations seems fine too :

I am gonna need more information / logs / screenshots in order to help you, from what I see on my side everything seems fine (yet).

[Binifada1956]

For the RTE integration, the client ID and the secret are returned via the API. The ID was then also used in the automations and in the script. See attachment. After the update, I can neither call up, view or edit the automations nor the script.Am 02.11.2023 um 14:40 schrieb Edouard Hur ***@***.***>: I did the upgrade to 2023.11 but it seems that my entities did not changed IDs (or I would not have history for them) : And my automatisations seems fine too : I am gonna need more information / logs / screenshots in order to help you, from what I see on my side everything seems fine (yet). —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[hekmon]

Unfortunately the attachment did not make it thru github with reply by email function. Please upload it directly within the github interface.

[Binifada1956]

For the RTE integration, the client ID and the secret are returned via the API.
The ID was then also used in the automations and in the script. See attachment.

After the update, I can neither call up, view or edit the automations nor the script.

[Binifada1956]

👍 did it, paste the attachments

…

Am 02.11.2023 um 15:17 schrieb Rolf Hoefel ***@***.***>: For the RTE integration, the client ID and the secret are returned via the API. The ID was then also used in the automations and in the script. See attachment. After the update, I can neither call up, view or edit the automations nor the script.

[Binifada1956]

any Idea?

[hekmon]

This is weird :

• The ID you have in your first screenshot is the application ID you created from RTE tu use the API
• The device_id of the Home Assistant device is something entirely different, internal of HA

Both should not match in any way.

For example, if I setup an automation with the same trigger as yours:

This translates to the following YAML:

Which no way near my RTE API Application ID:

So I am not sure how you ended up in this situation but I would recommend to edit your automation and recreate the trigger with the UI to get the correct HA device_id.

[Binifada1956]

Good morning,

Everything works, even after the 2023.11.x update.
Without your help I would certainly not have solved the problem so quickly. Many thanks for that.

Greetings
Rolf alias Binifada

[hekmon]

Thanks for letting me know that everything is in order 👍