Closed pshirshov closed 6 months ago
Hello @pshirshov,
In order to correctly decode the actual device payloads I would need a 'complete' trace collected with these instructions
We have 2 orders of problems to solve through tracing:
After enabling the tracing feature then, you have 10 minutes (by default) to 'operate' the device with HA (and the app if you're still using that) in order to collect all the data/messages exchanged with the device.
beside these steps you could also enable the 'create diagnostic entities'. You should then see in the device panel in HA a whole new set of diagnostic sensors reporting the raw device data and you could check which values are reported for the different operating modes. If you like, you could try change the device operating mode (physically or with the app) and post here any mapping you can figure out. These values (namely, the 'Mode' sensor should map to each one of the 7 working modes) should change and reflect the inner device state.
If you're in for this deeper data collection/testing I suggest you to read #356 where support for mts960 was initially requested/implemented so that you have more insights (most of them were just speculations) about the device.
Version of the custom_component
5.0.3
Describe the bug
I have an MTS960 which is set to cooling mode with set temp 25 degrees. The measured temperature is 18 degrees.
For some reason the component reports the stat as being in heating mode and when I try to change the set temperature I'm getting " list index out of range" messages.
When I try to switch to cooling from HA, I'm getting
Debug log