Closed trvrcr closed 1 year ago
Please enable logging (see readme) and attach the log.
It looks you have a custom schedule, when I look under temperatureControl all settings have settable=false which means we can't set the values, have you tried to disable your custom schedule.
Please attach screenshots of HA and the Onecta app to compare.
It worked with the schedule before, So is the update a regression of functionality? Might be that it is necessary but then I know what i need to adapt to change it.
Please enable logging (see the readme.md) and attach the log file you got. Does maybe the entity id changed, go to settings/devices and click the device link under the altherma integration, what do you see there? Under controls do you see the thermostat there?
For the logs is it only adding the following lines in the configuration.yaml file and then resload the file?
logger:
logs:
custom_components.daikin_residential_altherma.climate: debug
I cannot see any new entries in the log of Home Assistant Core.
Yes, enable logging, see https://github.com/speleolontra/daikin_residential_altherma#setting-the-log-level. You do see energy values, strange.
It worked with the schedule before, So is the update a regression of functionality? Might be that it is necessary but then I know what i need to adapt to change it.
I had the same experience +/- 1 week ago. No change in version of the integration, and the problem "disappeared" as mysterious as it came. I wasn't able to do extra "research" or "debug" at the time... but there were HA updates at the same time and maybe an update in the Daikin app also. I'm not sure ... but maybe an "external cause" other than this integration?
Just rebooted the whole of Home assistant again to check and issue has been resolved. Seems like @TomNoLimit has it right.
After the update the thermostate shows unavailable. Value of the room sensor is available in the diagnostics as shown below.
Can i revert back to previous version?