core: Incorrect translation of insteon thermostat properties from core-2023.3.6 to 2023.4.2
The problem
My insteon thermostats are being misreported now by HA.
The are working normally in and reflecting the correct values and setting in the insteon hub app.
They are actually in heat mode, on, in fan auto, and heating ~ 66 degress.
You can see HA shows them at 34 degrees and set to heat but indicates its currently cooling.
The timeline where is all changes (screenshot) is when I installed this update.
What version of Home Assistant Core has the issue?
core-2023.4.2
What was the last working version of Home Assistant Core?
core-2023.3.6
What type of installation are you running?
Home Assistant Core
Integration causing the issue
insteon
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
## System Information
version | core-2023.4.2
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.10
os_name | Linux
os_version | 5.15.84-v8
arch | aarch64
timezone | America/Los_Angeles
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4922
Installed Version | 1.30.1
Stage | running
Available Repositories | 1332
Downloaded Repositories | 11
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | October 3, 2023 at 5:00 PM
relayer_connected | true
relayer_region | us-east-1
remote_enabled | true
remote_connected | true
alexa_enabled | true
google_enabled | false
remote_server | us-east-1-9.ui.nabu.casa
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 9.5
-- | --
update_channel | stable
supervisor_version | supervisor-2023.04.0
agent_version | 1.4.1
docker_version | 20.10.22
disk_total | 13.6 GB
disk_used | 5.2 GB
healthy | true
supported | true
board | rpi4-64
supervisor_api | ok
version_api | ok
installed_addons | Terminal & SSH (9.6.1), File editor (5.5.0), Node-RED (14.1.3)
</details>
<details><summary>Dashboards</summary>
dashboards | 8
-- | --
resources | 4
views | 8
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | April 11, 2023 at 3:59 PM
-- | --
current_recorder_run | April 12, 2023 at 4:26 PM
estimated_db_size | 508.74 MiB
database_engine | sqlite
database_version | 3.38.5
</details>
<details><summary>Sonoff</summary>
version | 3.4.0 (5406fa7)
-- | --
cloud_online | 4 / 4
local_online | 4 / 4
</details>
Additional information
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 17 (3 by maintainers)
That is correct. It can take a few days between a fix being implemented and being released. The fix was merged today and is tagged for release 2023.4.6. There is no specified date for that release, however.
I am working on a solution for this. Here is what is happening:
It will take me a few more days to develop and test this and then it will take a few days to get this into an HA release.
So the “fix”, if I can call it that, is after any restart of the system, force a change in the set point and wait for the temp to change in order to get it to the right values (you could also hit the thermostat with a hair dryer to for a change I suppose). Alternatively, roll back to 2023.3.
Just adding that I’m having the same issues as the others that have reported.