The burner cleaning cycle does not end, and the pellet boiler does not burn

[Edgarun]

Is there an existing issue for this?

• I have searched the existing issues

I'm having the following issue:

Hello, after turning on the integration, the boiler fan works at 100 percent, and the burner cleaning cycle does not end, and the pellet boiler does not burn

I have following devices connected:

• ecoMAX 3xx series
• ecoMAX 8xx series
• ecoMAX 9xx series
• Expansion module B
• Expansion module C
• ecoSTER 200/ecoSTER Touch
• ecoLAMBDA
• ecoNET 300

I'm connecting to my devices using:

USB to RS-485 adapter

I'm seeing following log messages:

No response

My diagnostics data:

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[denpamusic]

Hi, thank you for the feedback!

This is not good. If protocol isn't getting mangled somehow by RS-485 adapter, it means that your device uses different protocol and is not compatible with the PyPlumIO library and by extension this integration.

Could you please provide full device name (e. g. ecoMAX 920P1-O) or, if possible, diagnostics data.

Thank you!

[Edgarun]

Thanks for the reply, ecomax 920P1 TOUCH, the burner works, until the cleaning of the burner starts and the cycle does not end, I changed the rs485 to a new

[Edgarun]

Diagnostics data , https://drive.google.com/file/d/13IhDB9rTfUfxc_5HNnRCn_qwDI9uAgxE/view?usp=share_link

[denpamusic]

Sorry, I've incorrectly assumed that integration never worked in the first place.

Then it is definitely a bug.

It's probably occurring when PyPlumIO processes frame versions. Those are requests that are being sent periodically, once version for corresponding frame in frame version table changes.

From the diagnostics that you provided, I can see following version table. Frames that are not implemented, are automatically ignored, so that leaves us with less suspects. From what I can see, I think that frame 61, which is FrameType.REQUEST_ALARMS in most boilers I've encountered to this point, means something different for the EM920, since it's failing to produce a list of alarms in the device data.

"frame_versions": {
    "26": 27222,  # FrameType.REQUEST_CONFIG_SCHEMA (NotImplemented)
    "85": 32966,  # FrameType.REQUEST_DATA_SCHEMA
    "84": 24260,  # FrameType.REQUEST_CURRENT_PARAMETERS (NotImplemented)
    "86": 27796,  # FrameType.REQUEST_REMOTE_MENU (NotImplemented)
    "54": 1,      # FrameType.REQUEST_SCHEDULES
    "56": 2,      # FrameType.REQUEST_SETTINGS (NotImplemented)
    "57": 2,      # FrameType.REQUEST_UID
    "61": 51685,  # FrameType.REQUEST_ALARMS
    "92": 2206,   # FrameType.REQUEST_THERMOSTAT_PARAMETERS
    "94": 0,      # FrameType.REQUEST_THERMOSTAT_CONFIG (NotImplemented)
    "95": 2,      # FrameType.REQUEST_THERMOSTAT_DATA_SCHEMA (NotImplemented)
    "88": 25027,  # FrameType.REQUEST_THERMOSTAT_SCHEDULES (NotImplemented)
    "62": 56014   # FrameType.REQUEST_NAMES (NotImplemented)
},

I think we can fix this, by implementing a list of failed requests during device handler load.
If request is failed, it should then be excluded from the version table as unsupported.
Other than that, I don't see what can cause such an issue.

I'll try to implement required changes to PyPlumIO library until next weekend and release a new integration version.
Hopefully it will resolve this issue.

[Edgarun]

thank you very much, I will wait for the new version

[Edgarun]

Hello, nothing has changed after installing the latest version, the cycle still crashes
diagnostik
https://drive.google.com/file/d/1e3iEyCckbMfCyBbhR9kEugcYOpJHK86d/view?usp=share_link

[denpamusic]

Hi,

I'm really sorry to hear it.
FYI the link above returns "Access denied". Maybe you forgot to set access to Public.

That being said, I have no idea on why this happens, unless your specific firmware has a weird bug in it.

I don't have EM920 and no one else, that has it, reported this issue, so there's sadly isn't much that can be done. I'll still keep this issue open just in case, but the possibility of fixing it without the affected device is pretty low. Sorry...

[Edgarun]

sori
https://drive.google.com/file/d/1e3iEyCckbMfCyBbhR9kEugcYOpJHK86d/view?usp=share_link

[denpamusic]

Thanks. Now it opens fine. I'm still not seeing any problems in the diagnostics though. Does HASS log contain any error messages, when boiler is getting stuck? Maybe that can tell us a least something about the problem.

[Edgarun]

the boiler is constantly in the cleaning mode, and does not complete this process. There is a linear motor, it interrupts and does not complete the process, neither the hame assistant nor the controller throws any error. everything else works fine, but when you need to turn off the boiler, it does not complete the cleaning process