Daikin Cloud Controller - BRP069C4

[S10NL]

Thanks for all the work done!

Is there a way to migrate from manual install to the github repository install.
So that i can update the code to the newest commit without manual editing everything?

[eals]

Dear forum

Started with great enthusiasm, linking the perfera air conditioners to Domoticz
All described steps up to "getting the flow to work", point 3, have been successfully completed!

However, I can't start the deploy because 1 node, may be the most important one, is unknown :
"Daikin cloud controller: type unknown to your installation of Node-RED".

How can I solve this?

Kind regards,

Eric

[eals]

problem solved!

[yomano]

Good evening.

I installed Node-red Daikin Cloud controller a few weeks ago. It worked for 2 weeks.

Now I got the error:

node: Daikin Cloud msg : error "HTTPError: Response code 400 (Bad Request)" in the Daikin Cloud node

I did a fresh install with again the same error.

I have no problems with the Onecta app. I use the correct login and password.

Is this a new common problem or am I the only one?

[mgugu]

Good evening.

I installed Node-red Daikin Cloud controller a few weeks ago. It worked for 2 weeks.

Now I got the error:

node: Daikin Cloud msg : error "HTTPError: Response code 400 (Bad Request)" in the Daikin Cloud node

I did a fresh install with again the same error.

I have no problems with the Onecta app. I use the correct login and password.

Is this a new common problem or am I the only one?

This is a common issue, check https://github.com/DrHauss/node-red-con ... /issues/19

[yomano]

Thank you mgugu.

But it didn't work.

[mgugu]

Thank you mgugu.

But it didn't work.

I get this problem about every 2 month (without apparent reason). Removing the token (if any), and restarting Nodered solves the issue for 2 month.
Sometimes I need to repeat this operation.
I also tried to generate a token with a proxy as described at the node developper site but same effect. An update would be great if the problem is not at Daikin side.

[yomano]

Goodmorning.

I fixed the node: Daikin Cloud msg : error "HTTPError: Response code 400 (Bad Request)" error.
I did a new Node-Red install.

But i have 2 new errors:
On Node read devices: Error:_Invalid property expression_ unexpected ' ' at position 36
On Node read kWh: Error: Invalid property expression: unexpected ' ' at position 10

I need a little bit of help.

Thank you

[JustDude]

Hi,

I got the Node-red setup working, the devices show up. So all good. Thanks for the hard work!

But I presume my firewall blocks communication to and from the cloud. Does anyone know which port(s) they use?
Otherwise, I need to spoof my network and check for blocked requests... And that is ok when nobody knows the answer right away.

On Node read devices: Error:_Invalid property expression_ unexpected ' ' at position 36
On Node read kWh: Error: Invalid property expression: unexpected ' ' at position 10

No such errors on my side.... maybe a fresh load of the node script from github will do wonders?

[yomano]

No such errors on my side.... maybe a fresh load of the node script from github will do wonders?

Those errors are gone. How?? I dont know.

[Syndomo]

@ksacca: many many thanks for setting this up and sharing it with the rest of the world !!

1)
@visvier had the following error, and so do I:
node: Read Devices function : (error) "TypeError: Cannot read properties of undefined (reading 'value')"

I was able to boil it down to the ECONO and LED attributes (both) for my DAIKIN STYLISH units - not for my Perfera unit. When I commented out the lines 117 to 160 in the Read Devices node the error disappeared (and of course the variables aren't updated).
I notice in the Onecta app that Econo mode cannot be controlled for Stylish units, so that could be the culprit. Same for the led attribute.

However don't take my analysis for granted as I only discovered this topic - including node red itself - today
So unfortunately I'm not (yet) able to propose a decent solution either.

2)
As for the spaces in the names of the units: I also have that. I suggest one extra change in the node Create Devices.
By adding a variable "displayname" it is possible to have the unit created in Domoticz with spaces, whilst keeping all other name usage with underscores.

Code: Select all

var switchmsg = {}
for (let i = 0; i < msg.payload.length; i++) {
    var ssid = msg.payload[i].managementPoints.gateway.ssid.value
    var displayname = msg.payload[i].managementPoints.climateControl.name.value
    // displayname is the name that the unit will get in Domoticz
    var name = displayname.split(' ').join('_')
    // name is the same but with spaces replaced by underscores, for coding purposes
    var id = msg.payload[i].desc._id
    switchmsg.retain = true

    //Power ON/OFF
    if (flow.get("CreatePower") == true) {
        switchmsg.topic = flow.get("AutoDiscoveryPrefix") + '/switch/power/' + name + '/config'
        // differentiate between displayname and name
        switchmsg.payload = '{"name": "Daikin ' + displayname + ' Power", "command_topic": "' + flow.get("StateSetPrefix") + '/switch/power/' + name + '/set", "state_topic": "' + flow.get("StateSetPrefix") + '/switch/power/' + name + '/state", "unique_id": "' + id + '_power"}'
        node.send(switchmsg);
    
    ===> AND SIMILAR IN THE REST OF THE CODE OF THE NODE

Looking forward for any feedback - thanks in advance for any reactions !

[Syndomo]

I do have one other issue.

Besides the Daikin units in my own house, I can also see/control the unit in my son's house through Onecta. We granted permission to each other.
As a consequence, the node red flow also retrieves his unit from the Daikin cloud.

One option would be to adapt the flow to only capture the units belonging to a particular house.
But I presume that another option would simply be not to create a device for my son's unit in Domoticz. Is that correct ?
I don't want to cool his house when my solar panels produce too much energy

[Edit] I've been digging in the payload coming in from Daikin and I don't see where/how it contains a "house" identification. I wonder how Onecta makes the difference. Or am I overlooking something ?

[Xavier82]

Does this message has impact on the Domoticz Daikin hardware?
Daikin stops with current API and starts platform for developers.....
Sorry in Dutch:
https://tweakers.net/nieuws/218654/daik ... -stop.html

[Syndomo]

Hmm... thanks for the info ! Let's see what that brings us.

I just finished a project to run my Daikin units in a full automatic mode through the LAN API. They automatically switch to heating/cooling depending on the season, they switch on/off depending on indoor and outdoor temperatures, setpoints get adapted overnight and when nobody is home. Setpoints are also adapted to increase heating or cooling when I have a production excess from my solar panels (trying to reduce the electricity I give away to the electricity company for very few money...). All programming is done in Domoticz dsVents, running on a Raspberry Pi.

I have 7 Stylish units for which that is possible. I also have one Perfera unit that already has no local LAN API anymore - but fortunately I don't have any need to steer that one automatically.

I have already been experimenting with the Daikin integration via the Onecta-platform, but decided not to persue that route for two reasons. First reason is that this creates a dependency with the internet (no internet = no control). For this reason alone I don't like it at all that Daikin discards local API control... Secondly I found no way to retrieve the outdoor unit frequency (which I need to control the units depending on solar power production).
Reading the information on GitHub, I see a third limitation: their new interface will only allow for 150 calls/day... Quite understandable for Daikin to keep control over the global load on their systems. But my automatic system keeps track of indoor temperatures every minute - that would be 1000+ calls/day..... Though indoor temperature is quite stable as Daikin writes, solar radiation isn't... I'd need to reduce that to about every 10 minutes during daylight and every 15 minutes overnight. At daytime that is too slow...
The forum discussion shows that I'm not the only one with that concern.

As long as you don't update the firmware in the units (which is done via Onecta - and only if you accept it) the control via the local API should remain possible. I've always been very careful about that in former firmware updates and intend to postpone further updates as long as possible, or block them completely, to keep local API access.

[mgugu]

Depending if Daikin will remove the actual cloud API, it seems to be an interresting alternative: FAIKIN (https://github.com/revk/ESP32-Faikin).
This is a very low cost WIfi controller based on an ESP32.
Advantages are local LAN access and MQTT support.

[dorenberg]

Today, a new daikin Comfora was installed at our home. First I thought let's see for a Faikin module, however our new FTXP-N no longer has a S21 port. But with this node-red flow, everything seems to work too. Thanks for that. Took a while to get it up and running, but all good now. Especially the part where to install the additional nodes in Node-red was quite confusing for me.

[yomano]

Does this message has impact on the Domoticz Daikin hardware?
Daikin stops with current API and starts platform for developers.....
Sorry in Dutch:
https://tweakers.net/nieuws/218654/daik ... -stop.html

The node-red doesn't work anymore..

"Error: Communication failed 403"

I've tried to get the Apollon77 library working with the new API. I fowolled the read.me, but with no result.

[mgugu]

Apollon77 library is pure nodejs, did you incorporate it in a node-red module ?

[Ericmarius]

Where can I download the new node-red module, that communicate with the Daikin developer portal?

[mgugu]

https://github.com/DrHauss/node-red-contrib_BRP069C4
But it has not been updated yet with the new api