home-assistant-matter-hub: [Bug] 3.0.0-alpha.19 broke Thermostat
Climate thermostats commands are broken since 3.0.0-alpa.19
Here are the catched errors when trying to poweron or change a temperature from Google Home:
[ 2024-11-07T10:32:14.561Z ] [ ERROR ] [ matter.js / Transaction ]: Error post-commit of 8f7ba291df5149adb82cb5badf1bf9f6.aggregator.climate_jeedom_thermostat_salon_thermostat_salon.thermostat.state: Referencing 8f7ba291df5149adb82cb5badf1bf9f6.aggregator.climate_jeedom_thermostat_salon_thermostat_salon.homeAssistant.state: This value is no longer available because its context has exited (1)
at get value [as value] (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/Datasource.js:122:15)
at descriptor.get [as entity] (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/values/StructManager.js:150:49)
at _HeatingThermostatServer.targetTemperatureChanged (file:///usr/local/lib/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2208:42)
at emitNext (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:70:20)
at BasicObservable.emit (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:109:12)
at emitChanged (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/Datasource.js:332:30)
at Object.postCommit (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/Datasource.js:338:12)
at file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/transaction/Tx.js:465:39
at MaybePromise.then (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Promises.js:100:17)
at postCommitNextParticipant (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/transaction/Tx.js:464:27)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 47 (41 by maintainers)
Commits related to this issue
- fix(climate): map all neccessary properties from climate to thermostat related to #73 — committed to t0bst4r/home-assistant-matter-hub by t0bst4r 2 years ago
- fix(climate): map all neccessary properties from climate to thermostat related to #73 — committed to t0bst4r/home-assistant-matter-hub by t0bst4r 2 years ago
- fix(climate): use entity state value as fallback for all status reports related to #73 — committed to t0bst4r/home-assistant-matter-hub by t0bst4r 2 years ago
- fix(climate): use entity state value as fallback for all status reports related to #73 — committed to t0bst4r/home-assistant-matter-hub by t0bst4r 2 years ago
- fix(climate): use entity state value as fallback for all status reports related to #73 — committed to t0bst4r/home-assistant-matter-hub by t0bst4r 2 years ago
I have seen that bug with lights, but not with climates. Doesn’t really make sense, but anyway I am currently refactoring the thermostat server, which will lead to some more stability.
-273 C=0 K= absolute minimumbut of course it should be set instead of defaulting to the limits. Can you please create another issue for that including the attributes of the climate again to have all details for that in one place.
I had a chat with one of the developers of matter.js and it doesn’t seem to be a bug on matter side, but on Google and Alexa side. It seems that we are doing the mapping of system mode, running mode and running state correctly, but they just don’t use it. One more question to that: does google home indicate the running mode correctly, when system mode is auto?
I’ve now added these, too.
For now i have added a fallback to occupied heating setpoint (20°C). Doesn’t really make sense, but let’s try it out. Could be a matter of milliseconds.
I’ve also added a “show details” checkbox in the UI when hovering values. Maybe this helps debugging.
Just found this in home assistant core code of the climate entity:
so seems to be the same
state possible values are the same as hvac_modes
no it should be ok as it won’t be used anyway… I’m testing now. Thanks
okay thank you. i already released it, can you please test 🙂
i’ll have a look at those three properties later. is it problem to set them like i did?
Maybe someone can explain climate devices to me again 😀
Having those attributes from Home Assistant:
In matter i have the following required properties:
Initially i thought i need to set min/max setpoint limits equally to min_temp and max_temp from HA. Now i found the following explanation for
minSetpointDeadBand:Can someone please explain in detail HOW the HA attributes shall be mapped to the named matter properties?
As a quick fix i’ll try to set the minSetpointDeadBand to
0, but i assume that’s not right.i’ll have a look