Skip to content

Some communication error sets target temperature to 16 °C #154

@leoshusar

Description

@leoshusar

Hi! I'm having this very rare issue. It happens only like once in 1-5 months, so I can't even catch it in debug log.

When some communication(?) error happens, this component sets the target temperature to 16 °C and it's also successfully sent to the AC. When this happened in summer twice, I had to make an automation to immediately return it back or I would freeze lol.

The only data I have are these:

  • [15:25:48] Error Code reads 172
  • [15:25:48] Target temperature set to 16 °C
  • [15:25:48] Current temperature reads 10 °C
  • [15:25:49] My automation returns the target temp back to a healthy value
  • [15:26:48] Error Code reads 0
  • [15:26:48] Current temperature reads 22.5 °C

No other entities were changed, only current temp, target temp and error code.

I can't tell what the root of the issue is, if the AC sends wrong values with a correct checksum (but this never happened with only the original WiFi module), or if those values are received wrong and somehow the checksum is still valid.

I think the solution might be as easy as just ignoring the received message data when error code is not 0, plus possibly triggering a new message request (if possible, or just waiting for a new message).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions