Feature request

[tola2000]

Hi,
Thanks to this component I was able to create a very nice card in home assistant to control my Pellet Stove. It works so much better than the original app!

The feature I'm still looking for is to be able to control the profile. I don't want to operate the stove in manual mode. But just control the set temperature and switch between the different profiles ( Active, Comfort, Silent, Boost ).

The current commands don't allow me to switch the profile. When I use the silend mode command the stove automatically switches to the manual profile, while I want to actually switch to the silend profile.

A command to control the profile is needed to be able to control the stove in "automatic" mode.

Cheers,
Tom

[Chibald]

Hi! That looks very nice indeed!

I think there are small difference between the types of stove from mcz.
My stove (a musa hydro) doesn't have profiles like "boost", "manual", etcetera.
It has a silent options, but it seems your stove works a bit differently.

I guess your stove needs to be controlled using the "Adaptive_Mode" Command.
Maybe you could try this one, 0 for manual, 1 for automatic?

Maestro/Command/Adaptive_Mode, 1

If this works i can try to make a new version for you, it should then support the following modes:

11 dynamic adaptive
12 adaptive at night
13 adaptive comfort
14 power 110% adaptive
0 manual non-adaptive
1 dynamic non-adaptive
2 overnight non-adaptive
3 comfort non-adaptive
4 power 110% non-adaptive

do you recognize any of these modes?

[tola2000]

Hi, Yes. I attached a screenshot of my app. I think I have the latest app, it's a brand new MCZ cute stove. [image: IMG_9041.PNG] When I control it with the app I get the following profiles back in the /profile topic: 10 manual 11 dynamic 12 night 13 comfort 14 power Besides the manual mode that seems the same as you suggested. I don't know why with my stove you have manual value 10 and in your list it's 0. COMFORT Ideal for all situations requiring maximum comfort. In this mode the stove allows an optimized consumption of the fuel to guarantee a good heating capacity and the best possible silent operation. Once this mode is activated, the user only has to choose the desired temperature and the appliance will independently manage the flame and ventilation power to ensure maximum comfort. In fact, in this mode it is not possible to change the power and ventilation, managed intelligently by the MAESTRO system. DYNAMIC If you prefer traditional automatic operation with the option of setting the temperature and ventilation. OVERNIGHTGuarantees the maximum silence possible (noise reduced up to 4 times) allowing the maintenance of the room temperature. This mode is designed, in fact, for night-time operation or temperature conservation in an already pre-heated room ensuring the lowest possible acoustic impact. In Overnight mode consumption and ventilation are managed intelligently by the MAESTRO system and for this reason it is not possible to change its values. MANUAL For those who prefer to use the product in the traditional manner without any temperature control. In this mode the user can freely choose the mix of flame power and ventilation regardless of consumption or silence. POWER Operation at maximum power expressed by the product for a limited time (20 min) in order to allow rapid heating of a cold room. For the expected performance and consumption in this mode, this function can be reactivated only once every hour. I don't know how you can set this. But it would be logical if there was a topic /command/profile to select one of the upper profiles. If you can implement that I'm happy to document how to use this setting in combination with control_mode and active_mode. Currently it's not fully clear yet what the last two exactly do on my stove. The dynamic icon on my stove has also an A ( of Active? ) . So I'm not sure what the active_mode exactly does. My guess is that the active_mode/control_mode/silent_mode are the legacy way of implementing the way the stove functions and that now they use "profiles". I hope this helps, Tom

…

On Fri, Jan 14, 2022 at 1:56 PM Chibald ***@***.***> wrote: Hi! That looks very nice indeed! I think there are small difference between the types of stove from mcz. My stove (a musa hydro) doesn't have profiles like "boost", "manual", etcetera. It has a silent options, but it seems your stove works a bit differently. I guess your stove needs to be controlled using the "Adaptive_Mode" Command. Maybe you could try this one, 0 for manual, 1 for automatic? Maestro/Command/Adaptive_Mode, 1 If this works i can try to make a new version for you, it should then support the following modes: 11 dynamic adaptive 12 adaptive at night 13 adaptive comfort 14 power 110% adaptive 0 manual non-adaptive 1 dynamic non-adaptive 2 overnight non-adaptive 3 comfort non-adaptive 4 power 110% non-adaptive do you recognize any of these modes? — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAZ6DLY26MNWFJW2PT6K7LUWAMPFANCNFSM5L6MHM5A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Chibald]

Probably i missed one status.

So the list is:

10 manual non-adaptive
11 dynamic adaptive
12 adaptive at night
13 adaptive comfort
14 power 110% adaptive

0 manual non-adaptive
1 dynamic non-adaptive
2 overnight non-adaptive
3 comfort non-adaptive
4 power 110% non-adaptive

My guess is that if you set your app to "Adaptive" that it wil concatenate a "1" in front of the 4 profiles.

New MQTT topic:

Maestro/Command/Profile, 10
Maestro/Command/Profile, 11
Maestro/Command/Profile, 12
Maestro/Command/Profile, 13
Maestro/Command/Profile, 14 

If you do a git fetch you can use this new commands. It is not in the docker image yet. Are you using the docker image?

[tola2000]

Thanks, looks what I need. Yes I use the docker image. I’ll give it a try. Op za 15 jan. 2022 om 10:06 schreef Chibald ***@***.***>

…

Probably i missed one status. So the list is: 10 manual non-adaptive 11 dynamic adaptive 12 adaptive at night 13 adaptive comfort 14 power 110% adaptive 0 manual non-adaptive 1 dynamic non-adaptive 2 overnight non-adaptive 3 comfort non-adaptive 4 power 110% non-adaptive My guess is that if you set your app to "Adaptive" that it wil concatenate a "1" in front of the 4 profiles. New MQTT topic: Maestro/Command/Profile, 10 Maestro/Command/Profile, 11 Maestro/Command/Profile, 12 Maestro/Command/Profile, 13 Maestro/Command/Profile, 14 If you do a git fetch you can use this new commands. It is not in the docker image yet. Are you using the docker image? — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAZ6DITIEE55CMETVOE4CLUWE2KVANCNFSM5L6MHM5A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Chibald]

Ok, i'll have to update update the docker image first then.

[Chibald]

docker image is updated.

[tola2000]

Wow , I’ll give it try this evening Op za 15 jan. 2022 om 10:31 schreef Chibald ***@***.***>

…

docker image is updated. — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAZ6DJV5F3YCSYQBU5C6TLUWE5GFANCNFSM5L6MHM5A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tola2000]

For some reason i get error standard_init_linux.go:228: exec user process caused: exec format error when starting the new container. Which is strange as I run as root. I'll try to figure it out. Tom

…

On Sat, Jan 15, 2022 at 2:35 PM Tom Lambrechts ***@***.***> wrote: Wow , I’ll give it try this evening Op za 15 jan. 2022 om 10:31 schreef Chibald ***@***.***> > docker image is updated. > > — > Reply to this email directly, view it on GitHub > <#41 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGAZ6DJV5F3YCSYQBU5C6TLUWE5GFANCNFSM5L6MHM5A> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[tola2000]

The good news is that when I pull the code and create my own image the new command works like a charm. I can now control the different profiles. Well done! Cheers, Tom

…

On Sat, Jan 15, 2022 at 6:21 PM Tom Lambrechts ***@***.***> wrote: For some reason i get error standard_init_linux.go:228: exec user process caused: exec format error when starting the new container. Which is strange as I run as root. I'll try to figure it out. Tom On Sat, Jan 15, 2022 at 2:35 PM Tom Lambrechts ***@***.***> wrote: > Wow , I’ll give it try this evening > > Op za 15 jan. 2022 om 10:31 schreef Chibald ***@***.***> > >> docker image is updated. >> >> — >> Reply to this email directly, view it on GitHub >> <#41 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AGAZ6DJV5F3YCSYQBU5C6TLUWE5GFANCNFSM5L6MHM5A> >> . >> Triage notifications on the go with GitHub Mobile for iOS >> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> >> or Android >> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >> >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[tola2000]

Voila, the new version of my app: Simple interface. In normal modus the pelletstove just works with the internal schedule in either silent profile or comfort ( that you can control with the silent toggle which you can do for all modes ) when you change temperature it will switch to manual mode and the timer starts. After the timer ends the stove goes back to auto mode. Boost is the same but this sets the temperature to 21 degrees ( I don't use the power mode because my house is well insulated so I rather have it burning a bit longer which is cozy ). If you want you can extend the timer or set the remaining time with the Timer button and sliders. A simple and foolproof solution. It works quite nice. I choose to not control it too much but to rely on the stove as much as possible. This works extremely stable. I replace the status of the termostat ( heat or off ) by the real maestro status and use an external select for the preset modes. Thanks for the swift response in adding the command. If there is a way to give you some credit let me know! PS: One thing which is quite messy is that the chronostat mode turns off when you switch profile. For me that is a bug in the stove because why wouldn't I be able to go from comfort to silent to dynamic while remaining on the schedule. Anyway I programmed my way around that... Op za 15 jan. 2022 om 18:43 schreef Tom Lambrechts ***@***.***>

…

The good news is that when I pull the code and create my own image the new command works like a charm. I can now control the different profiles. Well done! Cheers, Tom On Sat, Jan 15, 2022 at 6:21 PM Tom Lambrechts ***@***.***> wrote: > For some reason i get error standard_init_linux.go:228: exec user > process caused: exec format error when starting the new container. Which is > strange as I run as root. I'll try to figure it out. > Tom > > On Sat, Jan 15, 2022 at 2:35 PM Tom Lambrechts ***@***.***> > wrote: > >> Wow , I’ll give it try this evening >> >> Op za 15 jan. 2022 om 10:31 schreef Chibald ***@***.***> >> >>> docker image is updated. >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#41 (comment)>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/AGAZ6DJV5F3YCSYQBU5C6TLUWE5GFANCNFSM5L6MHM5A> >>> . >>> Triage notifications on the go with GitHub Mobile for iOS >>> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> >>> or Android >>> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >>> >>> You are receiving this because you authored the thread.Message ID: >>> ***@***.***> >>> >>

[jbtrystram]

@tola2000 would you mind sharing the code of that applet ? I'm using the same setup as you do :)