Two stoves?

[VoetenK]

I have two stoves from MCZ. I have been able to use my first stove in Home Assistant for a while now. I'm using here for a docker container.

Now I would like to use my second stove in Home Assistant as well.
That's where I'm having problems. One way to do this is to use an extra USB WiFi dongle. Problem is I can't find a dongle that works in Debian Bullseye on a Raspberry Pi.
I installed Home Assistant Supervised on a Raspberry Pi 4b 8gb.

Another solution would be that the IP address 192.168.120.1:81 is not used but on my home WiFi network. The MCZ app also works via that network.

What solutions are possible to be able to use both of my stoves in Home Assistant?

[Chibald]

The stove is hardcoded to use 192.168.120.1 on it's internal wifi network.
So it will be problematic to use two maestrogaway scripts on one raspberry.

Couple of solutions:

1. get another raspberry and put another script there. Because the stove built-in wifi is not so strong, the pi needs to be really close to the stove anyway so maybe this is not a bad idea.

2. use a different 'gateway' script that does not use the stove internal wifi, but get the communication from the mcz servers.
   The downside (my opinion) is that the communication is without ANY security. Not a great idea on a device that uses fire...

3. bride the networks using a router. I myself use GL.iNet GL-AR300M16 Mini Router to bridge my networks because of poor network connectivity of my Pi to the stove.
   Setup:
   Pi, wired to lan
   Router, wired to lan, connected as bridge to stove via wifi.

Then you'll need to use Network Address Transalation (NAT) to map the IP of the 2nd stove to a free IP address on your Lan.
This option is maybe too complicated (?)

good luck!

[VoetenK]

Network Address Translation (NAT) to map the IP of the 2nd stove to a free IP address on my Lan is complicated for me.
Can you describe the procedure to do that?
I have the same router as you for the stove.
For my network in my home I use the RT-AC85P from Asus.

My first doubt is about the choice of network mode. Here I find the following options: router, access point, extender or WDS. I'm not sure if I should use it as a router or as an extender. Can you confirm which one I should take?

Then I go to advanced and use the default web interface of OpenWrt, Luci. At network/firewal I find NAT rules.
No matter what I try, it doesn't work.

Am I on the right track or am I forgetting some steps, if so, what and how should I fix it?

[Kam1ni]

I helped @VoetenK with setting up his router and after some experimentation we found out that NAT was not the way to go. But portforwarding did the trick.
So in the end the network looked something like this:

Raspberry pi was directly connected over wifi to stove 1
Router was connected over wifi to stove 2 and over a seperate network to the pi
By portforwarding port 81 on the router to stove 2 the pi could access stove 2 by connecting to the router with port 81
And stove 1 could still be accessed directly from the pi

In the future it's possible to add more stoves to the router if desired by adding another port forward rule to a different outbound network (where the 3th router would be) over a different incomming port.

So this issue can be marked as resolved.

[VoetenK]

Dag Kamil Om één of andere reden veranderd de kachel in de veranda regelmatig van IP-adres. 192.168.120.1 naar 192.168.244.1 en weer terug. Waarom dat gebeurt kan ik niet achterhalen. Ik heb daarom een tweede regel toegevoegd aan de router. Probleem is dat ik steeds een keuze moet maken tussen één van de twee als het IP-adres weer veranderd. Is er een manier om de beide regels te laten werken ongeacht welk adres er actief is? Vriendelijke groeten Koen Van: Kamil Krzysztof Kulach ***@***.***> Verzonden: zaterdag 12 november 2022 15:55 Aan: Chibald/maestrogateway ***@***.***> CC: Voeten Koen ***@***.***>; Mention ***@***.***> Onderwerp: Re: [Chibald/maestrogateway] Two stoves? (Issue #47) I helped @VoetenK <https://github.com/VoetenK> with setting up his router and after some experimentation we found out that NAT was not the way to go. But portforwarding did the trick. So in the end the network looked something like this: Raspberry pi was directly connected over wifi to stove 1 Router was connected over wifi to stove 2 and over a seperate network to the pi By portforwarding port 81 on the router to stove 2 the pi could access stove 2 by connecting to the router with port 81 And stove 1 could still be accessed directly from the pi In the future it's possible to add more stoves to the router if desired by adding another port forward rule to a different outbound network (where the 3th router would be) over a different incomming port. � Reply to this email directly, view it on GitHub <#47 (comment)

, or unsubscribe

<https://github.com/notifications/unsubscribe-auth/AGOMNI6IV4UP6CQCRGETTT3WH 6VTJANCNFSM6AAAAAARHHKJHY> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AGOMNI4PJM7NYEAXM2AXDI3WH6VTJA5CNFS M6AAAAAARHHKJH2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS OHMTUE.gif> Message ID: ***@***.*** ***@***.***> >

[Kam1ni]

Dag meneer voeten Dit is helaas niet mogelijk. Dit kan alleen als je de packet zouw dupliceren en dat kan niet met een normale router. Dit zouw eigenlijk volledig behandeld moeten worden door de kachel. Dus eigenlijk zouw ik dan eerder met MCZ contacteren waarom dat dat verandert.

…

On Fri, 16 Jun 2023 at 10:19, Voeten Koen ***@***.***> wrote: Dag Kamil Om één of andere reden veranderd de kachel in de veranda regelmatig van IP-adres. 192.168.120.1 naar 192.168.244.1 en weer terug. Waarom dat gebeurt kan ik niet achterhalen. Ik heb daarom een tweede regel toegevoegd aan de router. Probleem is dat ik steeds een keuze moet maken tussen één van de twee als het IP-adres weer veranderd. Is er een manier om de beide regels te laten werken ongeacht welk adres er actief is? Vriendelijke groeten Koen Van: Kamil Krzysztof Kulach ***@***.***> Verzonden: zaterdag 12 november 2022 15:55 Aan: Chibald/maestrogateway ***@***.***> CC: Voeten Koen ***@***.***>; Mention ***@***.***> Onderwerp: Re: [Chibald/maestrogateway] Two stoves? (Issue #47) I helped @VoetenK <https://github.com/VoetenK> with setting up his router and after some experimentation we found out that NAT was not the way to go. But portforwarding did the trick. So in the end the network looked something like this: Raspberry pi was directly connected over wifi to stove 1 Router was connected over wifi to stove 2 and over a seperate network to the pi By portforwarding port 81 on the router to stove 2 the pi could access stove 2 by connecting to the router with port 81 And stove 1 could still be accessed directly from the pi In the future it's possible to add more stoves to the router if desired by adding another port forward rule to a different outbound network (where the 3th router would be) over a different incomming port. — Reply to this email directly, view it on GitHub < #47 (comment) > , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AGOMNI6IV4UP6CQCRGETTT3WH 6VTJANCNFSM6AAAAAARHHKJHY> . You are receiving this because you were mentioned. < https://github.com/notifications/beacon/AGOMNI4PJM7NYEAXM2AXDI3WH6VTJA5CNFS M6AAAAAARHHKJH2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS OHMTUE.gif> Message ID: ***@***.*** ***@***.***> > — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEOLMLZK6OWBKPB7HS5HA3TXLQJIJANCNFSM6AAAAAARHHKJHY> . You are receiving this because you commented.Message ID: ***@***.***>