ich habe nun noch mal ein wenig ausprobiert:
Den NanoeMode kann man immer ein und aus schalten, bei jeder Betriebsart. Eine eigene Betriebsart nur für Nanoe gibt es nicht.
Die Betriebsart Lüften allerdings, macht nur mit Nanoe-Modus=an sinn und ist in der App auch nur so möglich.
Daher würde ich das so ändern:
- Wenn NanoeX verfügbar, dann auch Lüften erlauben (nanoeStandAlone=1)
- Wenn OperationMode Lüften gesetzt wird, dann immer NanoeX mit einschalten.
- Nanoe darf beim Lüften nicht mehr geschaltet werden.
Eine zweite Kleinigkeit habe ich noch gefunden:
Bei der vertikalen Ausrichtung gibt es noch den Wert 5 für ständige Lamellenbewegung hoch/runter. Im Gegensatz zu Automatik werden die Teile hier dauerhaft bewegt.
Für beides maile ich dir einen Patch zu.
What a wonderfull module! My Panasconic WH-MDC05J3E5 heatpump is easily recognized, device type is actually unknown - can I help to add this heatpump in the types?
domoticz example for heat pumps Heatpump/air conditioner as a Domoticz device - Page 2 - Domoticz
only a little bit information is different:
Pump flow rate [L/min]
Compressor frequency [hz]
Inlet water temperature
Outlet water temperature
Operation power [on/off]
Quite mode [off/1/2/3]
Pump flowrate Max duty [100/110/120/130/140/150]
Water temperature [target]
I have no information on how to connect these devices. The link provided refers to a completely different type of communication.
In this respect, the most we can do is „play“ a bit:
Please open the IO instance from the Panasonic module, open the debug and set the limitation to large enough (> 2000 lines).
Then open the configurator instance. Some things should have happened in the debug of the IO instance. Please save this debug and send it to me via PN or mail (email@example.com).
I can have a look at it, if I can see anything here, so that it is worth to investigate further.
Hi, very cool offer!
I just send you the debug, now after some research I found that the heatpumps are not completely accessable by this API - Panasonic is using a little bit different API like here: homebridge-panasonic-heat-pump/panasonicApi.ts at master · Hernas/homebridge-panasonic-heat-pump · GitHub
this is a completely different cloud, even if it says Panasonic on it, it’s called „Aquarera Smart Cloud“ and not „Panasonic Comfort Cloud“.
On the other hand, the device can be seen in the overview, but it causes problems when retrieving the status (GetDeviceStatus()). - HTTP 403(FORBIDDEN).
Can you see / control the device via the Panasonic Comfort Cloud app?
I seem to remember that when I logged in the air conditioners in the Panasonic Cloud, I had to somehow „enable“ them for control … but it’s been a while.
Is there anything in the device documentation
Hi, this is enabled indeed. The Panasonic Comfort Cloud app is working perfect (I can see all data and control the device)
I have spent the last few hours on this topic and have exhausted my options for the time being.
Is the connection of Heishamon, that seems to be a hardware solution (based on ESP), which is connected directly to the data bus of the system. I didn’t pursue that either, because yes, that would require some tinkering.
which is apparently the attempt to connect to the
Aquarell Smart website (aquarea-smart.panasonic.com)
to read out data, i.e. to parse the web page.
About the „Panasonic comfort cloud“:
Here is the problem that the first data retrieval of Geräetdaten is already rejected as „FORBIDDEN“.
This can be a small thing, what is missing in the data in the API, but can also be that the API call for the heat pumps is completely different.
It could of course also be some setting (in the app/Papasonic cloud) that restricts access to the device - but is rather unlikely, because the API is also used by the mobile app …
On the Internet I have not found any information on how to address a heat pump via Panasonic cloud - probably no one with the appropriate ambition has yet analyzed the data; heat pumps are not yet so extremely widespread, otherwise there would certainly be someone.
The problem with the Panasonic cloud API is that it is not public and therefore there are no documents. And since this is encrypted accordingly, it is not so easy to eavesdrop on the data traffic (which would require that the person who reverse enegeneered both the device and access to the account).
Basically, you have to intercept and analyze the still unencrypted traffic on the hand where the app is running. This is easier to do on an Android, an iPhone needs to be jailbroken to be able to do this; both techniques I am not familiar with and have never used.
The only vague hope would be that if I had access to your account, I could try to play around a bit; would be more of a fluke though.
I have no better news unfortunately