You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I use the ioBroker iot skill to set the target temperature of a heating thermostat and choose a non-integer value (e.g., 20.5°C), the target temperature is correctly set. However, the voice feedback from Alexa says "Automatischer Modus ist auf 21 Grad gestellt" instead of providing the expected temperature value 20.5. The value is rounded.
To Reproduce
Steps to reproduce the behavior:
Use a state with role level.temperature to create an Alexa device in the iot adapter with type THERMOSTAT and include it into the group of an Echo device
Say "Alexa, setze die Temperatur auf 20,5 Grad" to this Echo device
Temperature is set to 20,5 degrees, but voice feedback ist "Automatischer Modus ist auf 21 Grad gestellt."
Expected behavior
Voice feedback should be "Automatischer Modus ist auf 20,5 Grad gestellt."
Additional context @foxriver76
I might be wrong, but the logs seem to suggest that the issue originates from the Alexa Skill. The adapter's debug log shows the correct value everywhere, and the voice feedback appears to come directly from the Skill.
The text was updated successfully, but these errors were encountered:
Describe the bug
When I use the ioBroker iot skill to set the target temperature of a heating thermostat and choose a non-integer value (e.g., 20.5°C), the target temperature is correctly set. However, the voice feedback from Alexa says "Automatischer Modus ist auf 21 Grad gestellt" instead of providing the expected temperature value 20.5. The value is rounded.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Voice feedback should be "Automatischer Modus ist auf 20,5 Grad gestellt."
Screenshots & Logfiles
Logfile:
state:
iot Alexa device:
Versions:
Additional context
@foxriver76
I might be wrong, but the logs seem to suggest that the issue originates from the Alexa Skill. The adapter's debug log shows the correct value everywhere, and the voice feedback appears to come directly from the Skill.
The text was updated successfully, but these errors were encountered: