[Question] Communication over Rest API like legacy Daikin Wifi module #579
Comments
|
Pretty much all of the simple legacy http Daikin functions work, so generally legacy integrations still work. |
|
First of all: many many thanks for this Faikin module. I have 8 indoor units (on 2 multisplit outdoor units) - one of them had no LAN API. After installing a Faikin module the integration with Domoticz (based on the HTTP LAN interface - not via MQTT) was dead easy and works like a charm. Now my whole system is fully automated at any time of the year. There's one thing that I really miss: the Domoticz devices created to collect heating and cooling power consumption remain at zero. That is probably due to the /aircon/get_day_power_ex not being implemented in Faikin. |
|
That sounds like something we would have to collect and store rather that something we can simply extract from the aircon. Not out of the question but very much not the way the Faikin works at present. So I'll have to ponder this one. |
|
It didn't occur to me before but indeed the Faikin unit only manages "current" settings. I wonder how this is managed in the Daikin LAN module - it must store some history about power consumption, roughly about 130 values:
|
|
Indeed, it would not be impossible to store such values. I try and avoid using the flash unnecessarily, and storing in RAM would lose data on a restart - but that may be reasonably OK as these do not normally get reset often (occasional s/w updates). It would probably be simpler to collect using HA as that will happily store and graph the values over time I believe. |
Keep only 96 values in RAM ?My guess is that Domoticz only uses /get_day_power_ex. ... or only 48 ??I'm not even sure if Domoticz uses the values of yesterday, so an option would be to include those in the HTTP response but hardcoded at zero. That way there would only be 48 values (24 heat and 24 cool) to keep. A real HTTP response captured today at 15:30 is (though I overwrote prev_1day_heat values with zero): And this is the response at 16:10. Now the consumption of the 16th hour of the day is also filled in (value 6 = 600kWh). ... or maybe even only one ???Maybe Domoticz only picks the value of the "current minus one" hour and adds it to the domoticz.db to keep history. That way there would only be one value to be stored in RAM (or 2: one for heat and one for cool). The HTTP response for the 16th hour today in heating mode could then be I'm always willing to beta-test a few bits and ends if you decide to give it a go :-) With a bit of luck the "only one" option is enough ! |
|
That is probably lot too hard. |
|
I did some more reading in the discussion topics and found one on "Domoticz Daikin backwards compatibility integration": #236. Then maybe let's start from the beginning: is there any way at all to get any power usage information over the S21 interface ? BTW thanks again for your responsiveness and all your Good Work to keep us automation enthousiasts out of the Dark Daikin Cloud... |
|
Yes it reports it. We already do that. I think it's a cumulative counter so could easily be partitioned on the hour. Ah, sorry, kWh only. But for hourly stats that is all you need. Accumulating stats over a day is unlikely to be any issue really, and I think I currently target s/w updates for the morning so not much lost when you do. |
|
Academic precision isn't required, so losing the stats for a couple of hours isn't a showstopper at all. In the github documentation I only found something about energy in the S21.md manual: GM | Hex, Wh total energy usage.
|
|
At present MQTT (which reports using MQTT to HA) as far as I am aware. And yes, a grand total energy! So if we logged this every hour to a table we could provide per hour usage total. |
|
Just to add a little value to this topic of the Daikin Energy Counter from my observation only... |
|
@MuzzaMcD : at first the 0.1kWh increments confused me a bit too, For units that are turned off I typically see one increment per day. It's the power usage of the WiFi module + other circuit board. I never witnessed a decrease (yet). The Daikin HTTP /aircon/get_day|week|year_power_ex responses differentiate between heating and cooling. I wonder how that is done if the S21 port only provides a single grand total value... @revk How does it currently work ? Do you publish one MQTT message per hour with total power usage ? |
|
We include the kWh value from S21 in the data reported on status, simple as that. It is more often than hourly and I don't think we do any heat/cool counting. |
|
I set up an MQTT broker and connected the Faikin. Didn't connect to Domoticz yet, I first want to observe a bit. Under the Faikin header I found the actual data - being updated every 60 seconds. There's effectively an energy value, labeled Wh.
This leads me to believe that the reported energy usage represents the combined Lifetime energy of all units connected to the multisplit.
That would imply that the Faikin module cannot supply the power usage of an individual indoor unit - unless it is a single split system. ==================================================
|
|
These are my regular stats reports - you can change the format - but normally its is one value if only that value for period, or three (min, ave,max) if it changed during the period. It may be better to set live status updates to see more clearly. |
|
After further observation today I'm convinced that the reported Wh accounts for the whole multisplit system - i.e. all indoor units combined.
There's a difference with what Daikin reports (through HTTP into Domoticz). The Faikin total is roughly 10% lower (observed today as well as for the whole lifetime). I'm not looking for academic precision so either will do for me. Though I have more trust in the Faikin value :-) |
|
@Raspdomo I am not running any multi splits so I can't help with that. However, I do have a Shelly Power Meter attached to one of my Faikin controlled units. |
|
I come to the same conclusions. |
Hi,
I'm aware that this Faikin-module can communicate over MQTT.
However I would like to address this question:
Is communication over Rest API like legacy Daikin Wifi module working, too?
THX
The text was updated successfully, but these errors were encountered: