Temperature sensors broken in 5.0.12: Alexa responds "I don't know what went wrong" after 3 days

[Bjoern-W]

Describe the bug
Since updating ioBroker.iot from 5.0.7 to 5.0.12, Alexa no longer reads my temperature sensors correctly. Instead of announcing the temperature value, Alexa says: “I don't know what went wrong.”
This did not happen with version 5.0.7. The issue also did not appear immediately after the update, but only after about 3 days.

To Reproduce
Steps to reproduce the behavior:

1. Use ioBroker.iot version 5.0.12.
2. Expose a temperature datapoint to Alexa.
3. Ask Alexa for the temperature of the sensor.
4. See error: Alexa responds with “I don't know what went wrong.”

Expected behavior
Alexa should announce the current temperature value correctly, as it did with version 5.0.7.

Versions:

• Adapter version: 5.0.12
• JS-Controller version: <js-controller-version>
• Node version: <node-version>
• Operating system: Raspberry Pi OS on Raspberry Pi 5

Additional context

• The issue started only after updating from 5.0.7 to 5.0.12.
• It did not happen right away, but first appeared after about 3 days.
• I did not change the configuration of the temperature datapoints.
• The datapoints are configured correctly as:
  • common.type: number
  • common.role: value.temperature
  • common.unit: °C
• Example datapoint: 0_userdata.0.Temperaturen.Badezimmer.Temperatur
• I already tried deleting the devices in the Alexa app, removing them from ioBroker.iot, and rediscovering them, but the problem still persists.

[Diginix]

It's broken with all ver. after 5.0.7. See #1092

[Bambo84]

Hi together,

same bug on my side. With all version.
Also with the new one v6.0.1

Downgrade to 5.0.6 it works

[dagr1709]

Same here. I had installed 5.0.12 and it doesnt work anymore.
Go back to 5.0.6 works for me, thanks @Bambo84

[BramTown]

1st I thougt it was fixed with v6.0.1 but here also, after a few days, temperatures were no longer accessible.
Back to v5.0.7 works fine for me (using only HomeMatic non-IP thermostat.