Add support for pellet level sensor

[Robbe-B]

There was suggested a while ago that there are stoves with a pellet level sensor on it.
The goal is to detect the setting for the probe.
Depending on the value of this setting we will generate a entity for the pellet level sensor.
=> #38 (comment)

[Robbe-B]

@RickType,
Once this is implemented, would you be able to test this for me ?
The reason I'm asking you is because I don't have a sensor myself.

Optional: it would be helpful for me to get your diagnostics file when the hopper is empty VS your diagnostics file when the hopper is full.

Kind regards,
Robbe

[RickType]

Hi Robbe,Sure, I'm currently traveling and will be back on 3rd oder April.Waiting for your go!RgdsRickAm 25.03.2024 10:00 schrieb Robbe-B ***@***.***>: @RickType, Once this is implemented, would you be able to test this for me ? The reason I'm asking you is because I don't have a sensor myself. Optional: it would be helpful for me to get your diagnostics file when the hopper is empty VS your diagnostics file when the hopper is full. Kind regards, Robbe —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[Robbe-B]

@RickType,
How are you doing ?
Would it be possible to give me your diagnostics file when the hopper is empty VS your diagnostics file when the hopper is full.
If I have both states I can figure out how the pellet level sensor is working 😄

Kind regards,
Robbe

[RickType]

Hey,I’m good, thanks.Just came back from Easter holiday and now on a business trip.Will provide you the data by end of this week.Thanks for your effort to improve it further.CheersHotteVon meinem iPad gesendetAm 09.04.2024 um 07:52 schrieb Robbe-B ***@***.***>: @RickType, How are you doing ? Would it be possible to give me your diagnostics file when the hopper is empty VS your diagnostics file when the hopper is full. If I have bought states I can figure out how the pellet level sensor is working 😄 Kind regards, Robbe —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[RickType]

Here u go.

Be aware that MCZ haven't managed to properly introduce the state in the App. No matter how full the hopper is, there is always a alarm when I open the app.
Nevertheless, when the hopper is getting empty, the alarm will go off. From the stove, as well on the app. So I attached to files, the one with the empty hopper is marked.
I can't find a difference, but I only had 2 Min to check it. Let me know if you need further informations.

config_entry-maestro_mcz-9e621916f330ef9b684ebb1bca29a701.json
config_entry-maestro_mcz-9e621916f330ef9b684ebb1bca29a701-3_empty.json

[Robbe-B]

I don't see a difference either.
I think this will be retrieved via the firebase subscription mentioned by @Crisicus in #99 (comment)
This would be a pity for easy implementation of course.

[RickType]

At the end of the day they are good in buidling stoves, but there are not IT experts... ;-)
I would pay them 200 bugs if they would introduce an MQTT interface....

BUT: As I said, there is currently a bug in the MCZ software (besides many more). In the app I ALWAYS get a notification that the hopper is empty, see attached screenshot. My assumption is that you can see this in the attached logs.
My guess is that the stove is not synchronising the hopper fill state with the cloud, therefore this massage always appears.

If the sensors is not covered with pellets an extra alarms goes off. The stove itself fires a warning tone and I get an extra notification in the app. See 2nd screenshot.

I need to find some time to look this app. But it seems there are two different ways how notify when the hopper is empty....

[Crisicus]

Yeah those screenshots are part of the firebase subscriptions

[Robbe-B]

Yeah those screenshots are part of the firebase subscriptions

@Crisicus Can we easily implement that one ?

[RickType]

Would be great. If I would get an event in HA, I would trigger the central gas heating as a backup.

[Robbe-B]

I'll look into it, at this point I have no clue if this will be an easy task 😄

[RickType]

Thx m8! Highly appreciated. Not pressuring. Hopefully I can switch the stove off from next week... :-)

[RickType]

Have you seen this error message in the HASS log file?

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:190
First occurred: 1:15:35 PM (2 occurrences)
Last logged: 1:15:49 PM

Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues

[Robbe-B]

@RickType,

This is an issue for HACS itself => see hacs/integration#3534

Kind regards,
Robbe

[THuebner29]

I am now the proud owner of an MCZ Tecla Air 6 M1.
Are there plans to support the pellet sensor in the future? I would like to use it in HA too.

[Robbe-B]

@THuebner29,

First of all, congrats with your new stove !

I'm planning on looking into this feature in the future.

But it is not that easy for a couple of reasons.

First of all my stove doesn't has this feature so I can't debug this pretty well.

Second it seems to be a firebase subscription instead of the regular state update system we use for all other sensors.

As soon as I get access to such stove model, I'll look into it 🤞

Also, if you like the work we do, consider leaving a star ⭐ on this repository.

Kind Regards,
Robbe