New module: DaikinAC

roelb · 26 März 2020, 19:16:24

ZitatUPDATE 2023/2024: This module will not work with the latest generation of Daikin built-in Wifi modules, revision C or later. Those modules will only support cloud-based control as Daikin has removed the local API altogether. There is a solution though. If you have an indoor unit with this latest version of the Wifi module, you can get a compatible Daikin A or B revision wifi adapter and connect this to the S21 or X50 connector on the PCB of your indoor unit. Another option is to get the third-party "Faikin" module (sold om Amazon UK for GBP30) that also connects to this same connector. Either option will give you back the local API.

ZitatUPDATE: As of 21 april 2020, this module is part of the base FHEM distribution and documented in the command reference.

I've written a new module to control Daikin airconditioning units. The HTTPMOD based solution that has been going around on the forum for a few years now was only partially working and it's impossible to get it right using HTTPMOD.

The module I've written is fully functional on all units I've tested it on and allows to set all settings that can be set remotely, including power, operation mode (auto/cool/heat/dehumidify/vent), fan speed, airflow direction (none/vertical/horizontal/3D), as well as setpoint temperature, humidify, special modes such as powerful and streamer mode.

I've also made a Tablet UI template to control the units and a few extra SVG icons.

While I am working on getting this into the base FHEM distribution, you can find the current version attached to this post, as well as a tablet UI template and a couple of icons used in that template (which you'll need to put into your own custom font).

The documentation for the module is included in the .pm file and is part of the command reference

TabletUI

You can use the template that is attached to this post, as follows:

- Copy template_DaikinAC.html into your fhem/www/tablet folder
- Copy daikinac.css and daikinac.woff into your fhem/www/tablet/fonts folder
- Copy widget_scale.js into your fhem/www/tablet/js folder
- Add the following code into the <head> section of your own HTML file:

[tt] <link rel="stylesheet" href="fonts/daikinac.css" />[/tt]

- Add the following code into your HTML file whereever you want to place your control:

[tt]<div data-template="template_DaikinAC.html" data-parameter = '{ "p01": "your_device_name_here" }'></div>
[/tt]

You'll need about 350x160 pixels for this control, so scale the <li> in which you place it accordingly. The updated widget_scale.js is required as I've added a couple of extra parameters to it.

rudolfkoenig · 26 März 2020, 20:11:35

ZitatSo how do I proceed to get this into the base FHEM distribution?

#1. publish your code in the Forum => Done
#2. wait for at least two FHEM-Users for positive feedback
#3. somebody with longer FHEM module-writing experience must take a look at your code. I can take over this part if nobody else is volunteering, and #2 is done.
#4. if #1,#2 and #3 ist done, get an SVN write access, and check in your code. See http://svn.fhem.de for details. The .svg files should be submitted to the icon Maintainer.

roelb · 26 März 2020, 22:55:33

Oke. So I'll suggest the module (and this topic) to the folks that have been active in the other Daikin topics and wait for their feedback. I've renamed it to 58_HVAC_DaikinAC and it is attached to this post.

hugomckinley · 27 März 2020, 14:39:05

Hi,
very nice! I will test it.
Give me e few days.

Hugo

hugomckinley · 31 März 2020, 20:06:47

Hi roelb,
tested it some days with my ACs.
Works well. (I tried all functions excepting streamer and set hum, I don't own an Ururu, I've got an Emura)

Here is my feedback:

slider for values (like interval) -> should be a textfield
powerfull on works, powerfull off doesn't work
state is "Timeout: process terminated" at 4 of 4 ACs after 48 hours (set works, but state doesn't change even; no polling any longer), Daikin App works too
after changing some things (stateFormat and devStateIcon) state changed back to initialized

And my featurerequests:

reading compfreq (polled from get_sensor_info)
reading name (url encoded, as I remember) (at creation, or with update, like the other "static" values, polled from /common/basic_info)
get update button below the set list
readings for the used energy (hour/day/week/year), don't remember what is logged in the indoor units
"set reboot" to reboot the WiFi Adapter, has never been used, but who knows

Question: Should I translate the commandref entry to german?

Here are some log entries:

Code Auswählen

2020.03.28 19:28:55 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 19:29:02 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.

2020.03.28 20:46:12 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at (eval 64298) line 1.

2020.03.28 21:05:13 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:05:54 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:06:13 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:06:45 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:07:12 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:07:30 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:07:38 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:08:15 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:08:40 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:09:21 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:09:43 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:10:18 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:10:29 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:10:47 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:11:29 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:12:00 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:12:15 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:12:28 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:12:40 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:12:52 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:13:00 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:13:31 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:13:40 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:13:54 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.
2020.03.28 21:14:18 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:15:20 1: PERL WARNING: Use of uninitialized value $adv in split at ./FHEM/58_HVAC_DaikinAC.pm line 209.
2020.03.28 21:15:37 1: PERL WARNING: Use of uninitialized value $adv in sprintf at ./FHEM/58_HVAC_DaikinAC.pm line 220.

- next day:(no interaction)

2020.03.29 09:40:54 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/58_HVAC_DaikinAC.pm line 659.
2020.03.29 09:40:54 2: AC_SZ_DG HVAC_DaikinAC_Poll(): failed () - Timeout: process terminated
2020.03.29 09:43:32 2: AC_KZ_OG HVAC_DaikinAC_Poll(): failed () - Timeout: process terminated
2020.03.29 09:45:49 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/58_HVAC_DaikinAC.pm line 478.
2020.03.29 21:53:59 2: AC_KZ_DG HVAC_DaikinAC_Poll(): failed () - Timeout: process terminated

The next week(s) I will rework my script to use your module control my ACs automatically, before the summer arrives in Austria.

Good work!

Hugo

roelb · 31 März 2020, 22:50:39

Zitat von: hugomckinley am 31 März 2020, 20:06:47
Works well. (I tried all functions excepting streamer and set hum, I don't own an Ururu, I've got an Emura)

I've got one unit that has the streamer function and that works. Haven't got an Urura either, so the humidity functionality is completely untested.

Zitat
slider for values (like interval) -> should be a textfield
powerfull on works, powerfull off doesn't work
state is "Timeout: process terminated" at 4 of 4 ACs after 48 hours (set works, but state doesn't change even; no polling any longer), Daikin App works too

Done and fixed. I've done some sniffing on traffic from the Daikin app to my units here and got powerful mode to work as it should. I've noticed the timeout issue. It seems that my choice of rescheduling the call to my poll() function (using the blocking.pm lib) immediately after the SetBlocking() call is incorrect and can cause a race condition. I've moved the reschedule over to both finish/abort functions and can't get it to fail anymore.

Zitat
And my featurerequests:

reading compfreq (polled from get_sensor_info)
reading name (url encoded, as I remember) (at creation, or with update, like the other "static" values, polled from /common/basic_info)
get update button below the set list
readings for the used energy (hour/day/week/year), don't remember what is logged in the indoor units
"set reboot" to reboot the WiFi Adapter, has never been used, but who knows

"compfreq" is added. Useful indeed, but I didn't know what it represented until I just googled it and found it to be the current compressor frequency. Both "name" and the usage statistics are added as well. The same is true for the reboot option.

As for the "get update" button, I've been looking at how to do that, but unfortunately the documentation on module development is quite lacking on that front

. So any suggestion on how to accomplish that are welcome.

I'm currently looking at parsing the usage statistics into useful readings. I'm not entirely sure (yet) what the ordering in the weekly usage statistics is, as the get_week_power_ex and get_week_power output doesn't match up. So I've gathered todays output and will do that again tomorrow.

For now, an updated version is attached.[/list]

hugomckinley · 01 April 2020, 01:09:51

I can't set anything any longer (power, mode, rate, ...)
Only the readings hhum, htemp and otemp are updated if I set something, but nothing else happens.
I just copied the modul, set the correct rights an restarted fhem.

This is in the log, when I restart FHEM:

Code Auswählen

2020.04.01 00:51:23 1: PERL WARNING: "my" variable $s masks earlier declaration in same scope at ./FHEM/58_HVAC_DaikinAC.pm line 178, <$fh> line 3741.

get update generates an empty popup window with an O.K. button

There is no compfreq reading, but in the polled rawdata there is compfreq

roelb · 01 April 2020, 10:34:24

Sorry.. Late night changes

. I noticed that today. Fixed and attached file has been updated in my previous post.

hugomckinley · 01 April 2020, 11:46:01

Looks good!

but the cmpfreq reading is still not available

Tip for the docu -> a nice state visualisation:

Code Auswählen

attr <device> stateFormat 1:pow
<br>In: htemp °C <br>Out: otemp °C

Code Auswählen

attr <device> devStateIcon 1.0.*:frost@gray 1.1.*:frost@blue
Important: the new line after 1:pow

roelb · 01 April 2020, 11:49:45

- we were typing at the same time, see below -

As for compressor frequency, I just used "compfreq" as stated in your post, but did not check whether that worked. It turns out the actual parameter name is "cmpfreq", without the o. That has now been changed as well.

The "get update" should probably be "set update", as nothing is returned perse, but it does trigger an action. So I've changed that as well.

v1.0.4 is attached with these two changes. I'll have a look at the usage/wattage statistics later today. Any preference on how these should be exposed / parsed into readings?

hugomckinley · 01 April 2020, 13:18:20

Oups, sorry for the typo!

Looks good. Now I recode my controllscript for my ACs to use your module.

Suggestion for the powerconsumption readings:
* 0:00 - 24:00 of the last day and current day
* mo - sun last week and current week
* january - december last year and current year

so we could see the actual (and running/incomplete) values in relation to the last period of the same time range

roelb · 03 April 2020, 17:23:40

I've added the power usage statistics and cleaned up a few other things.

Changelog:

- stateFormat is now automatically generated upon creation, a bit more extensive than your example (different icons for different modes).
- two distinct poll intervals, one when the unit is powered off, another for when the unit is powered on. First interval defaults to 60 seconds, second interval to 10 seconds.
- Added the option to set shum with an offset, just as stemp
- shum must now be a multiple of 5 (the unit won't accept another value, at least not the ones that I've tested it on)
- Bugfix that caused polling to stop if the unit could not be reached or returned invalid values
- Renamed "set update" to "set refresh". "set update" still works though but is no longer documented
- added attribute "pwrconsumption" (0 or 1). If 1, power consumption data is gathered and returned in several new readings, in kWh.
- fixed mompow to be always 0 when the unit is powered off, and divided by 10 to represent kW when turned on
- added cmpfreq_max and mompow_max readings that keep track of maximum value seen for those. Can be used to display a dial or vu-meter representing relative power/frequency.
- added htemp_ifchanged, hhum_ifchanged and otemp_ifchanged readings. Copy of htemp,hhum and otemp, but only updated on change so that they can be used for logging purposes.
- documentation update to reflect above changes.

Please have a look at it and let me know if you notice any issues or see any errors in the log.

hugomckinley · 03 April 2020, 20:23:59

- In my opinion the intervals are much too short (why should I know the values every 10 seconds? Temperature is very sluggish.) I will use 300 sec when on and 600 seconds when off. But I think one interval would be enough.

- I don't understand the _ifchanged readings. Isn't it the same as the event-on-change-reading attribute?

- Note: With my Emura, the htemp reading always seems to be correct.

- No errors in the log entries.

-I don't have the reading mompow. (doesn't matter if the unit is on or off)
I think the reason is, that the model_info says: en_mompow=0 and I think this is enable_mompow, so my unit isn't able to send this value

Here are my raw Values:

basic_info:

Code Auswählen

ret=OK,type=aircon,reg=eu,dst=1,ver=1_2_51,rev=D3A0C9F,pow=0,err=0,location=0,name=%57%6f%68%6e%7a%69%6d%6d%65%72,icon=1,method=home only,port=30050,id=,pw=,lpw_flag=0,adp_kind=3,pv=3.20,cpv=3,cpv_minor=20,led=0,en_setzone=1,mac=DCF5054E1675,adp_mode=run,en_hol=0,grp_name=%4f%47,en_grp=1

control_info:

Code Auswählen

ret=OK,pow=0,mode=3,adv=,stemp=23.0,shum=0,dt1=25.0,dt2=M,dt3=23.0,dt4=25.0,dt5=25.0,dt7=25.0,dh1=AUTO,dh2=50,dh3=0,dh4=0,dh5=0,dh7=AUTO,dhh=50,b_mode=3,b_stemp=23.0,b_shum=0,alert=255,f_rate=A,f_dir=0,b_f_rate=A,b_f_dir=0,dfr1=5,dfr2=5,dfr3=A,dfr4=A,dfr5=A,dfr6=A,dfr7=5,dfrh=5,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0,dmnd_run=0,en_demand=0

model_info:

Code Auswählen

ret=OK,model=0D75,type=N,pv=3.20,cpv=3,cpv_minor=20,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=1,temp=1,temp_rng=0,m_dtct=1,ac_dst=--,disp_dry=0,dmnd=1,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=3,en_ipw_sep=1,en_mompow=0,hmlmt_l=10.0

sensor_info:

Code Auswählen

ret=OK,htemp=25.0,hhum=-,otemp=11.0,err=0,cmpfreq=0

hugomckinley · 04 April 2020, 10:52:06

I defined the AC at about 19:40 and later this flooded may log:

Code Auswählen

2020.04.04 02:00:11 1: PERL WARNING: Exiting subroutine via last at ./FHEM/58_HVAC_DaikinAC.pm line 824.
Label not found for "last PWR" at ./FHEM/58_HVAC_DaikinAC.pm line 824.
2020.04.04 02:00:11 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Process died prematurely)
2020.04.04 02:01:14 1: PERL WARNING: Exiting subroutine via last at ./FHEM/58_HVAC_DaikinAC.pm line 824.
Label not found for "last PWR" at ./FHEM/58_HVAC_DaikinAC.pm line 824.
2020.04.04 02:01:15 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Process died prematurely)
2020.04.04 02:02:18 1: PERL WARNING: Exiting subroutine via last at ./FHEM/58_HVAC_DaikinAC.pm line 824.
Label not found for "last PWR" at ./FHEM/58_HVAC_DaikinAC.pm line 824.
2020.04.04 02:02:22 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Process died prematurely)
2020.04.04 02:03:23 1: PERL WARNING: Exiting subroutine via last at ./FHEM/58_HVAC_DaikinAC.pm line 824.
Label not found for "last PWR" at ./FHEM/58_HVAC_DaikinAC.pm line 824.
2020.04.04 02:03:27 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Process died prematurely)
2020.04.04 02:04:28 1: PERL WARNING: Exiting subroutine via last at ./FHEM/58_HVAC_DaikinAC.pm line 824.
Label not found for "last PWR" at ./FHEM/58_HVAC_DaikinAC.pm line 824.
2020.04.04 02:04:32 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Process died prematurely)

btw: set works, but no polling any longer

roelb · 04 April 2020, 11:13:28

Got it, had the same issue this morning. I initially created the power reading in a perl block, but split that into a function. I changed all the "last" statements into returns, but seem to have forgotten one.

Fixed version is attached. Just reload in place and everything should continue.

As for your remarks:

- seperate htemp and htemp_ifchanged:

There is a use case for both. For logging purposes, you only need changed values. However, if the temperature is to be displayed on an interactive controller / thermostat, you need to know whether the value that you display is current. The module will only update all other readings only if they have changed, so there is no need to force all readings to event-on-change. That way, a front-end can check whether the current temperature is current. If not, it can be grayed out, for example if the unit is offline and can not be polled or if it does no longer return a temperature (my older multisplit only returns otemp if it's turned on for example).

- I'll update the documentation with your findings for the Emura and my findings for the different units I've got here (5 different indoor units in two systems, one multisplit and one singlesplit).

- As for the interval, it all depends on your use case. I'm controlling these units on multiple TabletUI driven wall mounted tablets. But they can also be controlled through their infrared remotes and/or switched on or off with their internal timers. So I need their status to be correctly reflected within an acceptable timeframe, so that the status in FHEM corresponds to what the unit is actually doing. A minute is a reasonable interval whenever FHEM thinks the unit is off. That means that I'll still have pretty accurate temperature readings, and FHEM will know if a unit has been turned through timer or remote within a minute of that actually happening. That is acceptable from a user interface perspective. The load on FHEM with a 1-minute interval is very low, the 2 or 3 (with power monitoring) HTTP requests are short and generate very little data.

If the unit is turned on, there are readings that can change often, other than the temperature readings. The cmpfreq and mompow readings reflect the current compressor frequency and power usage. I've been observing those on my units, and they seem to change at most once per 10 seconds, so 10 seconds seems to be the goldylocks timeframe to poll them. And if you are displaying these values on a controller display, you need up-to-date readings, so that the displayed value actually makes sense. 10 seconds is an interval that gives people reasonably intuitive feedback as well, but still does not cause much load. For example, I've integrated a level meter in my TabletUI control that displays the current compressor frequency. But there is no issue in changing these into a larger value if you're use case is different.

Roel.

hugomckinley · 04 April 2020, 13:36:37

Thank you for the new version!

My solution would be the "normal" behavior of other FHEM modules. As I have seen they update the readings at the defined interval unless you specify the event-on-* attributes.
You can also force actual readings with event-min-interval.
If you want to know, if the readings are current, you could introduce a last-successful-poll reading (could also be enabled/disabled with an attribute) or use the timestamp of the readings. And as you have written, otemp should not be used for other things so it doesn't matter if it is not correct. I'm sure you have another thermosensor for the outdoor temperature to visualize

But I'm not a developer, so I think it would be good if a experienced FHEM developer would say a few words, what would be the usual method how to solve this tasks. I think it's not a question of right or wrong, but of what is usual.

I agree with you, that the usecases are very different, but I still think 10sec are not the usual case. If you keep the update strategy of only updateing if values are changed, it would not generate events in the log, but if not that would be too much entries in the filelog/dblog. But if it is documented users can decide their intervals correctly. I am a friend of slim databases and of not doing things that are not necessary

My usecase is: All indoor units are under full control of FHEM. Nobody touch any button. So 5 minutes are enough for me. I dont need to know everything I can

I would suggest to generate the attributes for the intervals when the device is defined, so the user can see the values imediately in the device.

Hugo

roelb · 04 April 2020, 14:17:40

Zitat von: hugomckinley am 04 April 2020, 13:36:37
My solution would be the "normal" behavior of other FHEM modules.

It's up to the module to decide what to do and the API provides functionality to update either a single reading, or all. I would qualify updating readings with the same value each time over, where that has no sensible meaning, to be just bad programming. And that is true the other way around as well.

This module now provides these three readings both ways. Simply use what fits your use case. It's all documented. The "event-on-change" attribute is a workaround that, IMHO, should not be neccessary except for exceptional cases.

ZitatIf you want to know, if the readings are current, you could introduce a last-successful-poll reading

There is already an internal LASTUPDATE var exposed. And every reading has it's own timestamp which serves that purpose perfectly. those timestamps are there for a reason. The three readings that are updated on each poll, even if unchanged, represent spot measurements valid at a single point in time, but are independent from each other, so keeping a single "last updated" state for that would not make sense. For all other readings, updating them unchanged would not make sense either.

Zitat
I agree with you, that the usecases are very different, but I still think 10sec are not the usual case.

The internal timer in the Daikin units for the cmpfreq and mompow values seems to be 10 seconds, so 10 seconds makes perfect sense if you are graphing or displaying those interactively. If not, just increase the interval. I guess most FHEM users use some form of interactive visulization (Tablet UI for most), so a short feedback loop makes sense when the unit is running. The demo tablet-UI control features a scale that visualizes the current compressor frequency - see attachment.

But as mentioned above, if it does not make sense in your use case, just adjust the intervals, it's a simple parameter.

Zitat
it would not generate events in the log, but if not that would be too much entries in the filelog/dblog. But if it is documented users can decide their intervals correctly. I am a friend of slim databases and of not doing things that are not necessary

And that is exactly why, except for three documented spot vars, all others are only updated on change. The documentation provides a section on logging with a clear warning on blanket logging and includes an example FileLog configuration:

Code Auswählen


define <devicename>_LOG FileLog <filename> <devicename>:(pwr.*_last|pwr_year_cur|power|pow|cmpfreq|mompow|stemp|shum|mode|rate|swing|powerful|streamer|econo|.*_ifchanged:.*

Zitat
I would suggest to generate the attributes for the intervals when the device is defined, so the user can see the values imediately in the device.

Sure, that's not an issue. They are visible in the FHEM webinterface though as internals if not overridden by an attribute. But I'll generate those two attributes on default at define time in the next version.

hugomckinley · 04 April 2020, 14:35:44

So we can both agree, that every use case should be covered

I continue testing ...

Hugo

roelb · 04 April 2020, 17:16:17

Yep

. And thanks, if you see anything out of the ordinary, please let me know.

hugomckinley · 04 April 2020, 18:42:24

You should delete all old versions of the module in this thread and attach the latest version to the first post.
So there is no risk of downloading a old release even without reading all answers.

Is there somebody else who is testing this module?

hugomckinley · 05 April 2020, 20:02:37

A minor bug is still there:

Sometimes I get timeouts even with a attr timeout=10

Code Auswählen

2020.04.05 18:18:22 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Timeout: process terminated)

I think the problem is not the value of the timeout, but the unit doesn't answer at all.

Is it possible to make a second try before logging this error?

markusphi · 05 April 2020, 22:44:35

ich habe das Modul Heute getestet und es funktioniert sehr gut!
Danke!

markusphi · 06 April 2020, 13:43:39

PERL WARNING: Argument "interval=180" isn't numeric in int at ./FHEM/58_HVAC_DaikinAC.pm line 110.
2020.04.05 22:39:40 3: AC_s_WZ: internal interval timer stopped

180 <> numeric?

roelb · 06 April 2020, 17:16:33

Zitat von: markusphi am 06 April 2020, 13:43:39
PERL WARNING: Argument "interval=180" isn't numeric in int at ./FHEM/58_HVAC_DaikinAC.pm line 110.
2020.04.05 22:39:40 3: AC_s_WZ: internal interval timer stopped

180 <> numeric?

I think you are specifying the text "interval=180" instead of just 180. That might be a misunderstanding of the usage prompt that you're getting.

Code Auswählen


Syntax: define <name> HVAC_DaikinAC <hostname/ip> [interval=60] [interval_powered=10]

What is meant here is that you can specify two optional parameters, "interval" and "interval_powered", with default values 60 and 10. So if you want to use 300 for the interval when the unit is off, and 120 when the unit is on, you define the device using:

Code Auswählen

define MY_DEVICE_NAME HVAC_DaikinAC 1.2.3.4 300 120

I'll update the usage error and documentation with a couple of examples to clarify this.

roelb · 06 April 2020, 17:21:15

Zitat von: hugomckinley am 05 April 2020, 20:02:37
I think the problem is not the value of the timeout, but the unit doesn't answer at all.

Is it possible to make a second try before logging this error?

Sure, I could add a "retries" parameter for this purpose, default value of 2. I haven't seen this on my units so far, they always respond as long as the network is up. Might be a wifi issue. Anyway, I'll add an automatic retry.

markusphi · 06 April 2020, 17:22:10

Zitat von: roelb am 06 April 2020, 17:16:33
I'll update the usage error and documentation with a couple of examples to clarify this.

ok, thank you! (sorry my english ist not so good)

Slanesh · 10 April 2020, 00:39:19

Just installed the module and it worked in less than 2 minutes. Great job @roelb!

gadget · 11 April 2020, 10:07:35

Just stumbled across this module. Got a Multisplit Daikin Stylish FTXA installed lately. Will try it and report back soon. Thanks for all your effort.

Edit: First quick test looks very promising.

roelb · 11 April 2020, 20:37:23

Thanks guys. I'll start the work on getting this into the base FHEM distribution.

I did fix one minor issue, which causes the monthly and daily power usage statistics to not be updated in time. They are now updated once every hour (if changed), so that the readings always reflect the most up-to-date power usage statistics.

This version (1.0.7) is attached to this post. I have also attached this version to the opening post, as well as the tablet UI template and a copy of the documentation.

hubiuwe · 18 April 2020, 20:31:38

Hallo roleb!
I tested the module with two FTXP20M on multi split.

It work's good for me!
(Stream and shum is not supported)

Gruß Uwe

Kasi13 · 26 April 2020, 09:04:22

Works perfectly with my FTXA, great addition to FHEM, Thank you roelb for your work!

roelb · 27 April 2020, 11:50:18

You're welcome. Module is now part of the base FHEM distribution. Thank you all for testing!

steffen83 · 18 Mai 2020, 08:35:47

Hello, I was a quiet reader, because my Daikin system was still in the ordering and assembly process. I have now installed the module and could not find any errors yet.
I think it's really great how it works. I'm still working on FTUI myself, so the question is whether someone already has a similar overview and control over reading groups etc.?
And is there a way to control the Daikin over my amazon alexa?
BR
Steffen

roelb · 18 Mai 2020, 10:29:10

Thanks for the feedback!

As for TabletUI, I have already created a full template, which has always been included in the opening post to this thread. So no need to figure that our yourself..

I have now updated the original post to include a full manual on how to integrate that control template into your own FTUI design. I've also added a custom icon font for the four SVG's so you do not have to generate that yourself. The HTML template has been modified to use these new icon names, so please download that again if you've already done so in the past.

fhemming · 26 Mai 2020, 12:44:56

Great module, works perfectly with Split FVXM35FV1B (BRP069B41). Big thanks!

Any chance to set up the device to interact with Alexa? I have the Alexa module successfully installed and can control other devices easily just by adding the alexaName attribute. This is not working for for the Daikin AC. I added the alexaName attribute and restarted the alexa module, but the device is not being listed when running:

Code Auswählen

list alexaName=..*

Following the troubleshooting wiki for the Alexa module https://wiki.fhem.de/wiki/FHEM_Connector_f%C3%BCr_Amazon_Alexa it's not clear to me what's exactly missing or needs to be adjusted. Has anyone implemented it and has some guidance to share?

Thanks a ton!

roelb · 26 Mai 2020, 16:19:06

I don't have an Alexa and can not easily test this. A quick scan of the Alexa modules wiki page though seems to indicate that the Alexa module expects a device to have a "set on" and "set off" command. The Daikin module currently has no such commands, you will need to specify the full "set power on" and "set power off" commands to turn it on and off.

You might get away with a simple EventMap to fix this:

attr <your daikin device> eventMap { usr=>{ 'on'=>'power on', 'off'=>'power off'}}

If not, try the patch that I've attached to add these commands to the module. If that works, please let me know and I'll commit those into the main branch.

The wiki page seems to be a work in progress, as there is no information on what the module expects a thermostat or other HVAC type-device to expose in terms of readings and commands to control the setpoint.

The author of the Alexa module might be in a better position to help on that and give pointers as to what must be done to make this fully compatible. I'd be more than happy to add something to make it work out of the box, but I would appreciate some pointers on what we need to make this compatible.

steffen83 · 27 Mai 2020, 11:39:45

Hello roelb,

can you send the complete "58_HVAC_DaikinAC.pm" files?
Then i can replace and test it.

BR
Steffen

fhemming · 28 Mai 2020, 20:02:34

Thanks, roelb!
Adding an EventMap worked perfectly, powering on and off the device with Alexa is now possible

I never tried out the patch you attached, but if you add support to the module I'd be happy to do some testing.

roelb · 28 Mai 2020, 21:45:54

I've just committed version 1.0.9 which contains a shortcut on and off command into the main repository. So if you update FHEM you should have the new version, no more need for an Eventmap

fhemming · 29 Mai 2020, 10:50:28

Confirming that it's working now without an EventMap

Thank you once again for your efforts here, roelb!

steffen83 · 29 Mai 2020, 10:54:31

Hello fhemming,

can you show me via "list" your clima-device with the amazon alexa configuration?

i have the same problem. But i can use it only as an thermostat.

BR
Steffen

fhemming · 29 Mai 2020, 11:16:10

Sure, as everything is default, I guess you're interested in the Attributes section.
I just added the required attribute "alexaName" (no more EventMap) and restarted the alexa module (and if required re-run device discovery within Alexa):

Code Auswählen

Attributes:
   alexaName  Klima
   devStateIcon off.*:control_standby@gray on.*cool:frost@blue on.*heat:sani_heating@red on.*dehumidify:humidity@blue on.*vent:vent_ventilation@green on.*auto:temp_temperature@red
   icon       weather_frost
   interval   60
   interval_powered 10
   stateFormat power/mode
<br>In: htemp &degC <br>Out: otemp &degC

I'm just using Alexa for turning the device on and off. Not sure if any other command is possible yet, I haven't tried.

Is your problem that you cannot even switch the device on/off?

raimundl · 29 Mai 2020, 20:37:32

Thanks for the great module.
Worked immediately and concern.
The AC can be switched on/off via Alexa.

Thank you and best regards

Raimundl

realkev · 30 Mai 2020, 08:54:28

Good morning,

I am using this module with an FTXC-B35 and it works quite good. I seems that cmpfreq cmpfreq_max aren't supported as they are both showing the value 999.
What I noticed is the following log entry:

Code Auswählen

Klima_Schlafzimmer HVAC_DaikinAC_PollDone(): Invalid response on get_control_info: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 391.

It occurs every 30 minutes during operation.

Poll intervals are

Code Auswählen

interval 180
interval_powered 10

Anyone other getting this entry?

Best regards,
Kev

roelb · 30 Mai 2020, 10:36:49

The error message that you are getting seems clear: the airco unit closes the HTTP connection but did not sent any data. So the module got an empty response where it was expecting status data. That is not a big issue, if a failure happens on a poll you'll just miss one interval. For a set, the set will fail and you'll need to retry.

What you're seeing is definitely an issue in the Daikin wifi control unit. I haven't seen that issue. You might try doing a couple of manual requests to the control interface and see if you can replicate that.

I've been thinking about implementing an automatic immediate retry whenever the request to the unit fails. However, that is a bit more complex than it seems due the asynchronous nature of the requests to the unit, using nonblocking IO. So an automatic retry will require some architectural changes in the module. It's on the todo list, so whenever I can find the time to rework this into the module, I will.

wulfmain · 11 Juni 2020, 23:54:57

Works perfect. Thank you so much! I really appreciate your Great work!

realkev · 14 Juni 2020, 11:22:12

Zitat von: roelb am 30 Mai 2020, 10:36:49
The error message that you are getting seems clear: the airco unit closes the HTTP connection but did not sent any data. So the module got an empty response where it was expecting status data. That is not a big issue, if a failure happens on a poll you'll just miss one interval. For a set, the set will fail and you'll need to retry.

What you're seeing is definitely an issue in the Daikin wifi control unit. I haven't seen that issue. You might try doing a couple of manual requests to the control interface and see if you can replicate that.

I've been thinking about implementing an automatic immediate retry whenever the request to the unit fails. However, that is a bit more complex than it seems due the asynchronous nature of the requests to the unit, using nonblocking IO. So an automatic retry will require some architectural changes in the module. It's on the todo list, so whenever I can find the time to rework this into the module, I will.

Hi Roelb,

thanks for your feedback, the empty responses weren't causing a significant issue within my system, nevertheless I am facing some other problems with the module at the moment:

Code Auswählen

2020.06.14 05:48:47 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 8504
2020.06.14 05:48:47 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 8503
2020.06.14 05:48:47 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 8502
2020.06.14 05:25:52 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 7597
2020.06.14 05:25:52 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 7596
2020.06.14 05:25:52 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 7595
2020.06.14 05:02:51 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 6685
2020.06.14 05:02:51 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 6684
2020.06.14 05:02:51 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 6683

Is there any maximum of commands being defined in certain period of time?
I am using a DOIF to regulate the temperature in a room by controlling the AC...

Best regards,
Kevin

roelb · 14 Juni 2020, 11:35:33

This might be a concurrency issue. As my module uses the FHEM nonblocking features for all requests, firing multiple requests at the same time (through some form of automation) will fork any number of processes that in turn perform the actual request to the aircon unit.

Daikin uses a AzureWave AW-CU300 integrated module for their Wifi controllers. This contains a Marvell 88MW300 microprocessor. I don't know what they have implemented in terms of handling concurrent requests. However, I can't get any of their units to fail in my own installation, whatever number of requests I fire at them.

Try adding 100ms of sleep in between your automated requests. If you have multiple Doif's that trigger on the same event, try adding different short delays to each of them so that they don't fire at /exactly/ the same time.

Hippo · 11 Juli 2020, 12:38:23

Hi roelb,

Great work! Thank you very much. It works perfect.
I am using a DOIF to change stemp, mode... I have to set the wait Timer to 1 Second, then it works well with my Daikin Stylish.

The Daikin Stylish have 2 more Options:
The "Intelligent Eye" and "Comfort Airflow"

Are there any readings/settings?

Best regards, Hippo

roelb · 11 Juli 2020, 14:21:31

As far as I know, these can not be set through the Wifi API. Just to make sure: are those functions available in the official Daikin controller app?

Hippo · 11 Juli 2020, 15:02:53

No, only with the IR Remote. $:-\$

shamal2008 · 23 Juli 2020, 17:29:22

Hi,

I just got my Daikin Stylish and tried to implement the Splits - what should I say - it works from the first moment. Now let's make the deep dive!

Thank you for this real great module - I'm happy and glad and can now try out some doif's and so on.

Thanks again,
Thomas from Vienna;

PS: my daikin just upgraded the firmware to 1.2.51 from 1.2.48 - works also!

shamal2008 · 29 September 2020, 21:58:37

Hi Roelb,

do you have any idea how I can integrate the Daikin in gassistant (google-home) ? - It shows in the google-home app, but i can only turn it on or off.

For more details:
https://forum.fhem.de/index.php/topic,114428.0.html

PS: I got email from Daikin, the Daikin Residential App ("the new one") will support the Daikin Stylish in the new version, which should be released this year.

greetings,
Shamal2008

m2th3o · 18 November 2020, 17:56:44

Great Module!!

Since I wanted to have it working with Alexa and there was already some discussion about it I would like to share my solution:

1. step: dummy with very limited attributes

Code Auswählen

Internals:
   CFGFN      
   FUUID      XXX
   NAME       WG_Heizung
   NR         9139
   STATE      off
   TYPE       dummy
   READINGS:
     2020-11-18 17:50:20   pct             24
     2020-11-18 17:51:24   state           off
Attributes:
   alexaName  Heizung
   genericDeviceType light
   readingList pct
   room       Wintergarten
   setList    pct:on,off

2. step: notify which fwds some commands when the dummy changes

Code Auswählen

WG_Heizung {my $Solltemperatur = ReadingsVal("WG_Heizung","pct","--");
if (Value("WG_Heizung") eq "on") {fhem("set WG_Klimaanlage stemp " .$Solltemperatur);}
if ((Value("WG_Heizung") eq "on") && (ReadingsVal("WG_Klimaanlage","state","--") eq "off")) {fhem("set WG_Klimaanlage on");}
else {if (Value("WG_Heizung") eq "off") {fhem("set WG_Klimaanlage off");}}}

For Alexa it behaves like a light with pct. But you can even say "Put Heizung on 24 degree".

Best regards
Markus

erwin · 13 Dezember 2020, 19:52:46

Great Module!

very good job done!!!
one tiny thing is on my whishlist:
from time to time the AC's loose there WLAN conn. for 5 to 30 Mins, but somehow recover ......
During that time, the log shows a number of error entries from LWP/Protocol/... and other modules.

Proposed idea: do a ping on enter of the blocking routine, if that fails, it makes no sense to continue....

Code Auswählen

Invalid response for /common/get_datetime: Can't connect to 192.168.10.14:80

No route to host at /usr/share/perl5/LWP/Protocol/http.pm line 49.

2020.12.03 23:47:10.427 2: AC_Schlafzimmer HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.10.14 (Timeout: pro

Thanks erwin

pdp1173 · 28 Dezember 2020, 12:17:10

Zitat von: m2th3o am 18 November 2020, 17:56:44
....
2. step: notify which fwds some commands when the dummy changes

Code Auswählen Erweitern
WG_Heizung {my $Solltemperatur = ReadingsVal("WG_Heizung","pct","--"); if (Value("WG_Heizung") eq "on") {fhem("set WG_Klimaanlage stemp " .$Solltemperatur);} if ((Value("WG_Heizung") eq "on") && (ReadingsVal("WG_Klimaanlage","state","--") eq "off")) {fhem("set WG_Klimaanlage on");} else {if (Value("WG_Heizung") eq "off") {fhem("set WG_Klimaanlage off");}}}

Hi Markus,

sorry , my first post here.
Can you please give a newcomer a hint, how and where step 2 is to be implemented.
I have defined a device "DaikinStube" with characteristics from step 1. It works!
But my

define DaikinStube notify { <data from Step 2> }

does not work. There is very little examples around how to use Perl Coding
inside a notify statement.

Thank you for your help.
Gino

roelb · 11 Januar 2021, 22:35:11

Zitat von: shamal2008 am 29 September 2020, 21:58:37
Hi Roelb,

do you have any idea how I can integrate the Daikin in gassistant (google-home) ? - It shows in the google-home app, but i can only turn it on or off.

Sorry for the late response. Must have missed the notification, and have been very busy on other work for the last months.

As for your question: no, I have not looked at Google Assistent integration in depth. I do use the current module myself to turn the aircons on and off, but no more. The Google Assistent module documentation unfortunately is almost nonexistant and it's code, both FHEM module and corresponding daemon, is completely undocumented as well. I did have had a peek in there for other integrations about a year ago, but quickly abandonded that due the the lack of documentation and messy code.

If you did manage to get it to work, please share! And if you require any changes in the Daikin module to get the integration to work, just ask.. I'm more than happy to extend the Daikin module with some extra commands or readings if that is neccessary.

MikeR · 18 Mai 2021, 22:13:09

Hello,

a few days ago i got my new Daikin Multisplit System installed. Today i tried this model for fhem and it works like a charm. Perfect.
Congratulations, superb job.

One thing: the two readings "mompow" and "mompow_max" didn't appear in my module. I have the indoor unit Stylish (aka: FTXA) with build in wifi adapter. I have activated the "pwrconsumption" attribute.

Any idea?

Greetings from Germany
Mike

roelb · 18 Mai 2021, 23:10:59

Your unit probably does not provide the data.

You could try a manual request to http://<airco ip>/aircon/get_sensor_info while it's running.

That should return something like "ret=OK,htemp=22.0,hhum=45,otemp=14.0,err=0,cmpfreq=0,mompow=1"

My guess is that for your unit, you won't see the "mompow" attribute. It's probably dependent on the outdoor unit providing the power usage information, but as long as Daikin does not publish anything about their API, we'll never know for sure.

MikeR · 19 Mai 2021, 11:10:50

Ok my result page looks like that:

Code Auswählen

ret=OK,htemp=24.0,hhum=40,otemp=26.0,err=0,cmpfreq=0

as i understand this means "No mompow" available.

Is it right that this url results are general values and the "mompow" is one of them if available?
I ask because such things like the state of the streamer are available in the fhem module. I think these are requested by an other url, right?

I guess readings for actual power are nice to monitor general power situations, but on the other hand no ones live depends on.

I thank you for your fast answer and wish you a nice day
Mike

shamal2008 · 20 Juli 2021, 20:14:25

Hallo zusammen,

musste meine Daikin Stylish Geräte für die Verwendung der "neuen" Daikin Residential Controller App (aus dem Playstore) firmwaremäßig updaten.

Kann berichten, dass das Modul mit Firmware-Version 1_4_28 immer noch perfekt funktioniert!

Danke nochmal für das Modul!

lg Shamal

kroonen · 19 Oktober 2021, 23:21:21

Hi,

Thx for the module. I now have a mode that is unknown? I think its the auto mode (that is what it is in thje Daikin App)

Code Auswählen


fhem> l AircoZolder
Internals:
   DEF        192.168.180.62
   FUUID      60b91aef-f33f-7999-7b15-bebcf341622ed577
   HOST       192.168.180.62
   INITIALIZED 1
   INTERVAL   60
   INTERVAL_PWRD 10
   LASTUPDATE 19.10.2021 / 23:17:57
   NAME       AircoZolder
   NR         100
   STATE      off/unknown
unknown
<br> Desired: 25.0 &degC 
<br>In: 20.0 &degC <br>Out: 17.0 &degC
   TYPE       HVAC_DaikinAC
   VERSION    1.0.9
   HELPER:
     FAULTS     0
   READINGS:
     2021-10-18 08:31:51   cmpfreq         0
     2021-10-18 08:31:51   dh1             50
     2021-10-18 08:31:51   dh3             0
     2021-10-18 08:31:51   dh4             0
     2021-10-18 08:31:51   dt1             25.0
     2021-10-18 08:31:51   dt3             18.0
     2021-10-18 08:31:51   dt4             25.0
     2021-10-18 08:31:51   econo           off
     2021-10-18 08:31:51   f_dir           0
     2021-10-18 08:31:51   f_mode          7
     2021-10-18 08:31:51   f_rate          A
     2021-10-19 23:17:57   hhum            -
     2021-10-18 08:31:51   hhum_ifchanged  -
     2021-10-19 23:17:57   htemp           20.0
     2021-10-19 14:47:03   htemp_ifchanged 20.0
     2021-10-18 08:31:51   mac             00E93A4B4927
     2021-10-18 08:31:51   method          home only
     2021-10-18 08:31:51   mode            unknown
     2021-10-18 08:31:51   model           12FB
     2021-10-18 08:31:51   name            airco zolder
     2021-10-19 23:17:57   otemp           17.0
     2021-10-19 23:16:57   otemp_ifchanged 17.0
     2021-10-18 08:31:51   port            30050
     2021-10-18 22:32:27   pow             0
     2021-10-18 22:32:27   power           off
     2021-10-18 08:31:51   powerful        off
     2021-10-18 08:31:51   rate            auto
     2021-10-18 08:31:51   reg             eu
     2021-10-18 08:31:51   rev             203DE8C
     2021-10-18 08:31:51   shum            50
     2021-10-18 22:32:27   state           off
     2021-10-18 08:31:51   stemp           25.0
     2021-10-18 08:31:51   streamer        off
     2021-10-18 08:31:51   swing           none
     2021-10-18 08:31:51   type            N
     2021-10-18 08:31:51   ver             1_2_54
Attributes:
   devStateIcon off.*:control_standby@gray on.*cool:frost@blue on.*heat:sani_heating@red on.*dehumidify:humidity@blue on.*vent:vent_ventilation@green on.*auto:temp_temperature@red
   group      Klimaat
   interval   60
   interval_powered 10
   room       Zolder
   stateFormat power/mode
mode
<br> Desired: stemp &degC 
<br>In: htemp &degC <br>Out: otemp &degC

pifs · 28 November 2021, 19:36:06

Hello,

I tried this module but got the following error:
Daikin_Studeerkamer HVAC_DaikinAC_PollDone(): Invalid response on get_basic_info: Page Not Found
/common/basic_info

Model: FTXM20R
Firmwareversion: 1_12_51

I assumed this module works with the mentioned model, maybe the firmware is to new or am I doing something wrong. Webpage of the Daikin is accessible.
Any help would be appreciated and if more info is needed let me know.

Regards Paul.

pifs · 12 Dezember 2021, 19:16:26

Zitat von: pifs am 28 November 2021, 19:36:06
Hello,

I tried this module but got the following error:
Daikin_Studeerkamer HVAC_DaikinAC_PollDone(): Invalid response on get_basic_info: Page Not Found
/common/basic_info

Model: FTXM20R
Firmwareversion: 1_12_51

I assumed this module works with the mentioned model, maybe the firmware is to new or am I doing something wrong. Webpage of the Daikin is accessible.
Any help would be appreciated and if more info is needed let me know.

Regards Paul.

My new model contains the C version of the wifi controller and Daikin removed the local API, so local integration is not possible. Very disappointing from Daikin. There seems a solution possible via the cloud control.

Gr. Paul.

kroonen · 15 Januar 2022, 16:08:35

Zitat von: kroonen am 19 Oktober 2021, 23:21:21
Hi,

Thx for the module. I now have a mode that is unknown? I think its the auto mode (that is what it is in thje Daikin App)

Code Auswählen Erweitern
fhem> l AircoZolder Internals: DEF 192.168.180.62 FUUID 60b91aef-f33f-7999-7b15-bebcf341622ed577 HOST 192.168.180.62 INITIALIZED 1 INTERVAL 60 INTERVAL_PWRD 10 LASTUPDATE 19.10.2021 / 23:17:57 NAME AircoZolder NR 100 STATE off/unknown unknown <br> Desired: 25.0 &degC <br>In: 20.0 &degC <br>Out: 17.0 &degC TYPE HVAC_DaikinAC VERSION 1.0.9 HELPER: FAULTS 0 READINGS: 2021-10-18 08:31:51 cmpfreq 0 2021-10-18 08:31:51 dh1 50 2021-10-18 08:31:51 dh3 0 2021-10-18 08:31:51 dh4 0 2021-10-18 08:31:51 dt1 25.0 2021-10-18 08:31:51 dt3 18.0 2021-10-18 08:31:51 dt4 25.0 2021-10-18 08:31:51 econo off 2021-10-18 08:31:51 f_dir 0 2021-10-18 08:31:51 f_mode 7 2021-10-18 08:31:51 f_rate A 2021-10-19 23:17:57 hhum - 2021-10-18 08:31:51 hhum_ifchanged - 2021-10-19 23:17:57 htemp 20.0 2021-10-19 14:47:03 htemp_ifchanged 20.0 2021-10-18 08:31:51 mac 00E93A4B4927 2021-10-18 08:31:51 method home only 2021-10-18 08:31:51 mode unknown 2021-10-18 08:31:51 model 12FB 2021-10-18 08:31:51 name airco zolder 2021-10-19 23:17:57 otemp 17.0 2021-10-19 23:16:57 otemp_ifchanged 17.0 2021-10-18 08:31:51 port 30050 2021-10-18 22:32:27 pow 0 2021-10-18 22:32:27 power off 2021-10-18 08:31:51 powerful off 2021-10-18 08:31:51 rate auto 2021-10-18 08:31:51 reg eu 2021-10-18 08:31:51 rev 203DE8C 2021-10-18 08:31:51 shum 50 2021-10-18 22:32:27 state off 2021-10-18 08:31:51 stemp 25.0 2021-10-18 08:31:51 streamer off 2021-10-18 08:31:51 swing none 2021-10-18 08:31:51 type N 2021-10-18 08:31:51 ver 1_2_54 Attributes: devStateIcon off.*:control_standby@gray on.*cool:frost@blue on.*heat:sani_heating@red on.*dehumidify:humidity@blue on.*vent:vent_ventilation@green on.*auto:temp_temperature@red group Klimaat interval 60 interval_powered 10 room Zolder stateFormat power/mode mode <br> Desired: stemp &degC <br>In: htemp &degC <br>Out: otemp &degC

I found the issue. The mode of my airco for auto = 7 . also found some documentation that de mode is 0,1 en 7.
https://github.com/ael-code/daikin-control

Can it also be changed in the module of fhem? I see only 0-6 and not 7.

eisman · 30 März 2022, 10:39:33

Hi,

Problem:

Code Auswählen


2022.03.30 10:34:21 1: PERL WARNING: Prototype mismatch: sub main::sum: none vs (@) at /usr/lib/x86_64-linux-gnu/perl-base/Exporter.pm line 66, <$fh> line 4742.
2022.03.30 10:34:21 1: stacktrace:
2022.03.30 10:34:21 1:     main::__ANON__                      called by /usr/lib/x86_64-linux-gnu/perl-base/Exporter.pm (66)
2022.03.30 10:34:21 1:     Exporter::import                    called by ./FHEM/58_HVAC_DaikinAC.pm (23)
2022.03.30 10:34:21 1:     main::BEGIN                         called by ./FHEM/58_HVAC_DaikinAC.pm (23)
2022.03.30 10:34:21 1:     (eval)                              called by ./FHEM/58_HVAC_DaikinAC.pm (23)
2022.03.30 10:34:21 1:     (eval)                              called by fhem.pl (2728)
2022.03.30 10:34:21 1:     (eval)                              called by fhem.pl (2727)
2022.03.30 10:34:21 1:     main::CommandReload                 called by fhem.pl (2057)
2022.03.30 10:34:21 1:     main::LoadModule                    called by fhem.pl (2122)
2022.03.30 10:34:21 1:     main::CommandDefine                 called by fhem.pl (1275)
2022.03.30 10:34:21 1:     main::AnalyzeCommand                called by fhem.pl (1126)
2022.03.30 10:34:21 1:     main::AnalyzeCommandChain           called by fhem.pl (1415)
2022.03.30 10:34:21 1:     main::CommandInclude                called by fhem.pl (626)

Device:

Code Auswählen


Internals:
   DEF        192.168.xxx.xxx
   FUUID      6118a7a8-f33f-793a-8010-e618bf1b6b5695fa
   HOST       192.168.xxx.xxx
   INITIALIZED 1
   INTERVAL   60
   INTERVAL_PWRD 10
   LASTUPDATE 30.03.2022 / 10:37:40
   NAME       Daikin
   NR         373
   STATE      off-cool
   TYPE       HVAC_DaikinAC
   VERSION    1.0.9
   HELPER:
     FAULTS     1
   READINGS:
     2022-03-30 10:35:35   basic_info      ret=OK,type=aircon,reg=eu,dst=1,ver=1_2_54,rev=203DE8C,pow=0,err=0,location=0,name=%44%61%69%6b%69%6e%45%53,icon=0,method=home only,port=30050,id=,pw=,lpw_flag=0,adp_kind=3,pv=3.20,cpv=3,cpv_minor=20,led=1,en_setzone=1,mac=DCF5059CB000,adp_mode=run,en_hol=0,ssid1=MABRAP01,radio1=-57,grp_name=,en_grp=0
     2022-01-23 08:43:24   cmpfreq         0
     2022-01-23 08:43:24   control_info    ret=OK,pow=0,mode=3,adv=,stemp=18.0,shum=0,dt1=25.0,dt2=M,dt3=18.0,dt4=25.0,dt5=25.0,dt7=25.0,dh1=AUTO,dh2=50,dh3=0,dh4=0,dh5=0,dh7=AUTO,dhh=50,b_mode=3,b_stemp=18.0,b_shum=0,alert=255,f_rate=A,f_dir=0,b_f_rate=A,b_f_dir=0,dfr1=5,dfr2=5,dfr3=A,dfr4=5,dfr5=5,dfr6=5,dfr7=5,dfrh=5,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0,dmnd_run=0,en_demand=0
     2022-01-23 08:43:24   dh1             AUTO
     2022-01-23 08:43:24   dh3             0
     2022-01-23 08:43:24   dh4             0
     2022-01-23 08:43:24   dt1             25.0
     2022-01-23 08:43:24   dt3             18.0
     2022-01-23 08:43:24   dt4             25.0
     2022-01-23 08:43:24   econo           off
     2022-01-23 08:43:24   f_dir           0
     2022-01-23 08:43:24   f_mode          3
     2022-01-23 08:43:24   f_rate          A
     2022-03-30 10:37:40   hhum            -
     2022-01-23 08:43:24   hhum_ifchanged  -
     2022-03-30 10:37:40   htemp           17.0
     2022-03-30 10:06:28   htemp_ifchanged 17.0
     2022-01-23 08:43:24   mac             DCF5059CB000
     2022-01-23 08:43:24   method          home only
     2022-01-23 08:43:24   mode            cool
     2022-01-23 08:43:24   model           0D75
     2022-01-23 08:43:24   model_info      ret=OK,model=0D75,type=N,pv=3.20,cpv=3,cpv_minor=20,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=1,temp=1,temp_rng=0,m_dtct=1,ac_dst=--,disp_dry=0,dmnd=1,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=3,en_ipw_sep=1,en_mompow=1,hmlmt_l=10.0
     2022-01-23 08:43:24   mompow          0
     2022-01-23 08:43:24   name            DaikinES
     2022-03-30 10:37:40   otemp           8.0
     2022-03-30 09:33:54   otemp_ifchanged 8.0
     2022-01-23 08:43:24   port            30050
     2022-01-23 08:43:24   pow             0
     2022-01-23 08:43:24   power           off
     2022-01-23 08:43:24   powerful        off
     2022-03-28 00:00:26   pwr_day_cur     0
     2022-03-29 00:00:03   pwr_day_last    0
     2022-01-23 08:43:24   pwr_history_daily_dec 0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0.1,0,0,0,0.1,0,0,0
     2022-02-28 06:00:55   pwr_history_daily_feb 0.1,0,0,0,0.1,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,,,
     2022-01-28 11:00:30   pwr_history_daily_jan 0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0
     2022-03-27 06:00:53   pwr_history_daily_mar 0,0,0,0.1,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0.1,0,0,0,0
     2022-03-28 00:00:26   pwr_history_hourly_today 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
     2022-03-29 00:00:03   pwr_history_hourly_yesterday 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
     2022-01-23 08:43:24   pwr_history_monthly_2021 0,0,0,0,0,0,0,0,1.2,0.8,0.8,0.8
     2022-03-27 06:00:53   pwr_history_monthly_2022 0.8,0.8,0.7,0,0,0,0,0,0,0,0,0
     2022-01-23 08:43:24   pwr_hour_cur    0
     2022-03-27 07:00:45   pwr_hour_last   0
     2022-03-27 06:00:53   pwr_month_cur   0.7
     2022-01-23 08:43:24   pwr_month_last  0.8
     2022-03-27 06:00:53   pwr_year_cur    2.3
     2022-01-23 08:43:24   pwr_year_last   3.6
     2022-01-23 08:43:24   rate            auto
     2022-01-23 08:43:24   reg             eu
     2022-01-23 08:43:24   rev             203DE8C
     2022-03-30 10:06:28   sensor_info     ret=OK,htemp=17.0,hhum=-,otemp=8.0,err=0,cmpfreq=0,mompow=1
     2022-01-23 08:43:24   shum            0
     2022-01-23 08:43:24   state           off
     2022-01-23 08:43:24   stemp           18.0
     2022-01-23 08:43:24   streamer        off
     2022-01-23 08:43:24   swing           none
     2022-01-23 08:43:24   type            N
     2022-03-30 10:37:40   unit_date       2022/03/30 10:37:41
     2022-01-23 08:43:24   ver             1_2_54
Attributes:
   alias      Klimaanlage
   comment    xxx
   devStateIcon off.*:control_standby@gray:on
on-cool:frost@blue:off
on-heat:sani_heating@red:off
on-dehumidify:humidity@blue:off
on-vent:vent_ventilation@green:off
on-auto:temp_temperature@red:off
   fp_Floorplan 17,1069,0,Daikin,
   icon       frost@blue
   interval   60
   interval_powered 10
   pwrconsumption 1
   rawdata    1
   room       Heizung,Schlafzimmer
   stateFormat [$name:state]-[$name:mode]
   verbose    0
   widgetOverride stemp:18.0,19.0,20.0,21.0,22.0,23.0,24.0,25.0,26.0,27.0,28.0,29.0,30.0

mfg

roelb · 30 März 2022, 10:52:57

Hey folks. I've been extremely busy lately, so no time for maintenance on this module. I understand that Daikin has changed some things in newer software versions. I will try to have a look at this in the near future.

pifs · 30 März 2022, 13:37:08

Found some useful info to control the Daikin via cloud https://github.com/Apollon77/daikin-controller-cloud

Gr. Paul.

GodVatter · 05 April 2022, 17:26:19

Hi Mike,

do you have any updates or information to that issue that mompow and mompow_max doesn't exist within the FTXA?

BR
GV

Zitat von: MikeR am 18 Mai 2021, 22:13:09
Hello,

a few days ago i got my new Daikin Multisplit System installed. Today i tried this model for fhem and it works like a charm. Perfect.
Congratulations, superb job.

One thing: the two readings "mompow" and "mompow_max" didn't appear in my module. I have the indoor unit Stylish (aka: FTXA) with build in wifi adapter. I have activated the "pwrconsumption" attribute.

Any idea?

Greetings from Germany
Mike

t1me2die · 20 Juli 2022, 17:39:25

Hi, my Daikin have two special extra modes, first: powerfull ("Leistungsstark") and second: economic.

But I can't set these modes via API.

Code Auswählen

http://xxx.xxx.xxx.xx/aircon/get_control_info

Gives me following response:

Code Auswählen


et=OK,pow=1,mode=3,adv=,stemp=19.0,shum=0,dt1=22.0,dt2=M,dt3=19.0,dt4=25.0,dt5=25.0,dt7=22.0,dh1=0,dh2=50,dh3=0,dh4=0,dh5=0,dh7=0,dhh=50,b_mode=3,b_stemp=19.0,b_shum=0,alert=255,f_rate=6,f_dir=3,b_f_rate=6,b_f_dir=3,dfr1=A,dfr2=5,dfr3=6,dfr4=5,dfr5=5,dfr6=5,dfr7=A,dfrh=5,dfd1=2,dfd2=0,dfd3=3,dfd4=0,dfd5=0,dfd6=0,dfd7=2,dfdh=0,dmnd_run=0,en_demand=0

In the special powerfull mode I've got this result:

Code Auswählen


ret=OK,pow=1,mode=3,adv=2,stemp=19.0,shum=0,dt1=22.0,dt2=M,dt3=19.0,dt4=25.0,dt5=25.0,dt7=22.0,dh1=0,dh2=50,dh3=0,dh4=0,dh5=0,dh7=0,dhh=50,b_mode=3,b_stemp=19.0,b_shum=0,alert=255,f_rate=6,f_dir=3,b_f_rate=6,b_f_dir=3,dfr1=A,dfr2=5,dfr3=6,dfr4=5,dfr5=5,dfr6=5,dfr7=A,dfrh=5,dfd1=2,dfd2=0,dfd3=3,dfd4=0,dfd5=0,dfd6=0,dfd7=2,dfdh=0,dmnd_run=0,en_demand=0

Now I try to change the "adv" parameter over the API like:

Code Auswählen


http://xxx.xxx.xxx.xx/aircon/set_control_info?pow=1&mode=3&adv=2&stemp=19&shum=0&f_rate=6&f_dir=3

Got following result:

Code Auswählen

ret=OK,adv=

What's wrong with my statement?

Kind regards
Mathias

t1me2die · 21 Juli 2022, 22:44:46

After many hours of testing and looking by google, I've found the solution.

Code Auswählen


Meaning:
spmode_kind=1 -> powerful
spmode_kind=2 -> economic

http://xxx.xxx.xxx.xx/aircon/set_special_mode?set_spmode=1&spmode_kind=1

Kind regards

Gisbert · 20 August 2022, 12:41:29

Zitat von: pifs am 30 März 2022, 13:37:08
Found some useful info to control the Daikin via cloud https://github.com/Apollon77/daikin-controller-cloud

Gr. Paul.

How does this work in detail? I'm lost.
To which URL do I need to login?

ZitatThe easy mode is to use the login method of the DaikinControllerCloud class and provide the E-Mail and the Password.

An automatic login is tried in this case and the tokens are retrieved.

Regards
Gisbert

chris_kmn · 05 Oktober 2022, 11:46:15

Moin Moin,

ich habe nun auch einige Daikins vom Typ FTXM-R mit dem integrierten WLAN Modul und der Firmware 1_12_84.

Aus den Diskussionen hier habe ich verstanden, dass es keine HTTP-Api mehr gibt, aber eine Cloud-Anbindung. Das DaikinAC Modul scheint auch nicht zu funktionieren.

Gibt es dazu schon FHEM-Lösungen wie man die Geräte ansteuern könnte ? Mit Alexa sind die Gerate verbunden und steuerbar.
Gerne hätte ich das natürlich auch per FHEM im Zugriff.

Gefunden habe ich eine Library die zur Kommunikation mit der Daikin Cloud genutzt werden können soll:
https://github.com/Apollon77/daikin-controller-cloud

Leider kann ich damit nix anfangen

Viele Grüße,

Chris

Hilde25 · 11 November 2022, 17:37:55

Hallo,

bin nicht sicher, aber probiere mal die Angaben der Commandref:

define MYDEVICENAME HVAC_DaikinAC daikin-living.mydomainname 300 60
create a device with name MYDEVICENAME. Unit can be reached through DNS name daikin-living.mydomainname. Set polling intervals to 300 seconds when turned off and 60 seconds when the unit is powered on

https://fhem.de/commandref.html#HVAC_DaikinAC

Gruss

chris_kmn · 11 November 2022, 18:33:37

Vielen Dank. Aber das ist leider die ,,alte" Variante für die die Controller direkt über Port 80 ansprechbar sein müssen. Das haben sie jedoch bei den neuen Versionen nun deaktiviert (was aktuell zu viel Frust bei den Smarthome Nutzern führt).

Ich hoffe Daikin besinnt sich da noch eines Besseren. Mit dieser Cloud-Einbahnstraße erzwingt man sich halt die Kundendaten - oder man kann halt die teuer bezahlte Online-Funktion nicht nutzen. Pech gehabt lieber Kunde

FrankL · 05 Februar 2023, 14:44:31

Ich möchte meine Erfahrung mit euch teilen

Ich habe bei mir Innengeräte vom Typ Daikin Perfera FTXM20R2V1B und FTXM25R2V1B verbaut. Leider sind diese neuen Geräte (erkennbar am R im Namen) mit einem neuen WLAN-Modul BPR069C41verbaut, die keine lokale Anbinbung mehr vorsehen. Die Steuerung ist ausschließlich über die Daikin-Cloud möglich. Daher kann das von FHEM zur Verfügung gestellte Modul HVAC_DaikinAC bei diesen Geräten nicht funktionieren.

Meine aktuelle "Alternativlösung" basiert auf der Cloud-Anmeldung von Apollon77 (https://github.com/Apollon77/daikin-controller-cloud). Zusammen mit einer Node-Red-Installation, den Daikin-Cloud Modulen und einem MQTT-Broker (MQTT2_SERVER reicht vollkommen) lassen sich damit sowohl Anzeige als auch die Steuerung über MQTT2_Device in FHEM realisieren. Es funktioniert, ist aber halt ein wenig umständlich einzureichten. Wer aber bereits MQTT kennt bzw. MQTT auch bei FHEM im Einsatz hat, und sich nicht vor einer zusätzlichen Node-Red-Installation scheut, kann damit zumindest relativ "einfach" eine Anbindung schaffen. Eine ausführliche Anleitung in englisch mit den benötigten Modulen unter Node-Red etc gibts unter:

https://www.domoticz.com/forum/viewtopic.php?p=292586#p292586

Ist zwar für domoticz entwickelt, funktioniert aber wie gesagt auch mit jedem anderen MQTT-Broker.

Solange Daikin daran festhält, ausschließlich die Cloud-Lösung für die neuen WLAN-Module anzubieten, sehe ich keine andere technische Lösung. Allerdings wäre es cool, wenn jemand die Cloudanbindung von Javascript auf Perl umschreiben könnte, damit es als eigenes FHEM-Modul eingesetzt werden könnte. Damit würde man sich die Node-Red-Installation und die etwas aufwändigere Einrichtung sparen. Allerdings übersteigt das meinen Programmierhorizont. Es gibt auch schon eine Variante der Cloudanbindung, die auf Python (https://github.com/rospogrigio/daikin_residential) basiert. Vielleicht hilft das auch schon weiter...

Ich konnte mit der dargestellten Alternativlösung über MQTT zumindest eine zuverlässige Steuerungsmöglichkeit der neuen Innengeräte schaffen und bin mit dem Ergebnis erstmal zufrieden.

eisman · 05 Februar 2023, 14:56:27

Hi,

da bin ich ja froh noch die alte Anlage gekauft habe, da "Klaut" für mich nicht in frage kommt,
solange es Menschen gibt die solche anlagen kaufen, wird sich leider nicht wirklich etwas ändern.

ich hätte sie als fehlerhaft zurück gesendet. Das Habe ich schon mit Sam und HM gemacht....
es wird ja schon im TV für "klaut" geworben, man kann dort seine gesicherten Bilder abholen, peinlich....

gruss

FrankL · 05 Februar 2023, 16:33:40

Als fehlerhaft würde ich die Geräte jetzt nicht ansehen, da Daikin auch keine offene API beworben hat. Ansonsten sind die eigentlichen Funktionen der Geräte (Heizen, Kühlen, Bedienbarkeit mit FB oder App) auch nicht zu beanstanden. Und "zurücksenden" ist wohl bei ordnungsgemäßer Installation durch den Klimatechniker nicht wirklich eine Option. Aber ein bißchen verärgert bin ich schon, dass die neuen Wlan-Module keine lokale API mehr unterstützen. Ob ich mich stattdessen für ein Stylish-Gerät mit altem Wlan-Modul (statt Perfera mit neuem Wlan-Modul) entschieden hätte, kann ich nicht sagen. Rein theoretisch könnte ebenso bei den alten Wlan-Modulen mit einem Firmwareupdate die lokale API Schnittstelle irgendwann entfallen. Genauso hoffe ich natürlich, dass sich Daikin eines besseren besinnt und bei den neuen Wlan-Modulen mit einem Firmwareupdate die lokale API irgendwann doch noch zur Verfügung stellt. Die Hoffnung stirbt zuletzt ...

Und wie beim TV und allen anderen Geräten mit Cloud-Möglichkeit und man natürlich die Wahl, den Internetzugang einzurichten oder eben nicht. Eine IR-Fernbedienung gibt es ja auch noch. Aber das wird jetzt ein bißchen Offtopic. Im Endeffekt wollte ich mit meinem Beitrag nur eine Möglichkeit für Betroffene aufzeigen, die Geräte über die Cloud<>Node-Red<>MQTT<>FHEM einzubinden.

Bei meinen ganzen Recherchen bin ich noch auf zwei interessante Ansätze gestoßen, die allerdings immer mit Hardwarebastelei verbunden sind. Zu einem hat jemand das interne BRP069C41 Wlan-Modul durch einen ESP32 ersetzt und damit eine lokale Anbindung per MQTT realisiert:

https://github.com/revk/ESP32-Daikin

Eine nährere Beschreibung ist auch im Blog des Autors unter https://www.revk.uk/search/label/DAIKIN verfügbar. Allerdings mag ich am Innenleben meiner Klima-Geräte nicht wirklich was verändern. Daher kam diese Lösung erstmal nicht in Betracht.

Zum anderen gäbe es auch die Möglichkeit, mit einem ESP32/ESP8266 und einer IR-Diode eine Fernbedienung zu simulieren und so die Geräte ohne Cloud fernsteuerbar zu machen. Das wäre dann aber eine Einbahnstraße, d.h. nur Befehle senden ohne Feedback oder Status auslesen oder so. Also nicht wirklich smart. Das war für mich auch keine Option.

Von daher blieb für mich nur die Lösung über die Cloud.

Gisbert · 05 Februar 2023, 22:10:33

Hallo FrankL,

ZitatZu einem hat jemand das interne BRP069C41 Wlan-Modul durch einen ESP32 ersetzt und damit eine lokale Anbindung per MQTT realisiert:

https://github.com/revk/ESP32-Daikin

Eine nähere Beschreibung ist auch im Blog des Autors unter https://www.revk.uk/search/label/DAIKIN verfügbar.

Ich finde es großartig, dass du neue Möglichkeiten zur Anbindung Daikin-Klimageräten an Fhem anzubinden, gefunden hast. Die oben zitierte Lösung scheint für mich am interessantesten zu sein, allerdings sehe ich noch keine einfache Realisierung, aber immerhin.

Herzlichen Dank für deine Beiträge.
Gisbert

FrankL · 05 April 2023, 21:00:16

I wrote a new module (58_DaikinCloud.pm) to control Daikin units connected to Daikin cloud. This was necessary for me because the new devices (with the WLAN module BRP069C4x) no longer have a local API access. I presented the module here:

https://forum.fhem.de/index.php?topic=133044.0

Greetings Frank