Daikin Hardware

For heating/cooling related questions in Domoticz

Moderator: leecollings

User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: Daikin Hardware

Post by waltervl »

What I see in the code it will setup a connection to the website

Code: Select all

	{
		szURL << "http://" << m_Username << ":" << m_Password << "@" << m_szIPAddress << ":" << m_usIPPort;
	}

	szURL << "/common/basic_info";
So translated: http://UserName:Password@DaikinIP:Port/common/basic_info
If Username, password is left empty it will connect to: http://DaikinIP:Port/common/basic_info


So to test you could manualy put this URL with your DaikinIP and Port and if needed Username and Password in a browser and it will gave some text back.
If succeeded please respond so I can update the wiki wit further instructions.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

I get the following text if I leave out the /common/basic_info part:

This software is included following open source software.

The FreeRTOS kernel is released under the MIT open source license, the text of
which is provided below.

This license covers the FreeRTOS kernel source files, which are located in the
/FreeRTOS/Source directory of the official FreeRTOS kernel download.  It also
covers most of the source files in the demo application projects, which are
located in the /FreeRTOS/Demo directory of the official FreeRTOS download.  The
demo projects may also include third party software that is not part of FreeRTOS
and is licensed separately to FreeRTOS.  Examples of third party software
includes header files provided by chip or tools vendors, linker scripts,
peripheral drivers, etc.  All the software in subdirectories of the /FreeRTOS
directory is either open source or distributed with permission, and is free for
use.  For the avoidance of doubt, refer to the comments at the top of each
source file.


License text:
-------------

Copyright (C) 2017 Amazon.com, Inc. or its affiliates.  All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

lwIP is licenced under the BSD licence:

Copyright (c) 2001-2004 Swedish Institute of Computer Science.
All rights reserved.

Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products
derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.

mbed TLS

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!)  The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

JSMN is licenced under the MIT licence:
Copyright (c) 2010 Serge A. Zaitsev
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Eclipse Paho MQTT C/C++ client for Embedded platforms

Eclipse Distribution License - v 1.0
Copyright (c) 2007, Eclipse Foundation, Inc. and its licensors.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Eclipse Foundation, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

wpa_supplicant and hostapd
--------------------------

Copyright (c) 2002-2019, Jouni Malinen <[email protected]> and contributors
All Rights Reserved.

These programs are licensed under the BSD license (the one with
advertisement clause removed).

If you are submitting changes to the project, please see CONTRIBUTIONS
file for more instructions.


This package may include either wpa_supplicant, hostapd, or both. See
README file respective subdirectories (wpa_supplicant/README or
hostapd/README) for more details.

Source code files were moved around in v0.6.x releases and compared to
earlier releases, the programs are now built by first going to a
subdirectory (wpa_supplicant or hostapd) and creating build
configuration (.config) and running 'make' there (for Linux/BSD/cygwin
builds).


License
-------

This software may be distributed, used, and modified under the terms of
BSD license:

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

3. Neither the name(s) of the above-listed copyright holder(s) nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: Daikin Hardware

Post by waltervl »

Yes, but the common/basic_info part is far more important!!
So please tell what you get. There should be some info about your air-conditioning unit.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

waltervl wrote: Wednesday 02 June 2021 19:37 Yes, but the common/basic_info part is far more important!!
So please tell what you get. There should be some info about your air-conditioning unit.
I don't get any info from the air conditioner. I just get a Page not found error.
Daikin.jpg
Daikin.jpg (33.92 KiB) Viewed 4542 times
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: Daikin Hardware

Post by waltervl »

Alain wrote: Thursday 03 June 2021 7:22
waltervl wrote: Wednesday 02 June 2021 19:37 Yes, but the common/basic_info part is far more important!!
So please tell what you get. There should be some info about your air-conditioning unit.
I don't get any info from the air conditioner. I just get a Page not found error.
Then you have the wrong IP address or your Daikin is not compatible with this Domoticz hardware gateway.

Do you have to fill in an account when using the Daikin App?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

I've been looking around on internet (github etc.) and see someone disclaiming that their script/library won't work with airco's that use the Daikin Residential Controller app. I think that's where my problem is. My units use that app and have a manufacture date of april/2021. I hope someone can get this to work on newer units soon.

@waltervl Yes, I have to fill in an account in the app.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: Daikin Hardware

Post by waltervl »

Alain wrote: Thursday 03 June 2021 9:06

@waltervl Yes, I have to fill in an account in the app.
What if you try: http://UserName:Password@DaikinIP:Port/common/basic_info
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

waltervl wrote: Thursday 03 June 2021 9:09
Alain wrote: Thursday 03 June 2021 9:06

@waltervl Yes, I have to fill in an account in the app.
What if you try: http://UserName:Password@DaikinIP:Port/common/basic_info
Same error
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

These guys seem to be working something out in the new interface. It's not for Domoticz, but I've done that dance before with the Qlima/Midea units. Once the communication can be done through a command line and a python script, I should be able to get it into the Domoticz Framework.

https://github.com/cbrandlehner/homebri ... issues/123
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
BurningTyre
Posts: 28
Joined: Wednesday 21 August 2019 15:44
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: Arnhem, The Netherlands
Contact:

Re: Daikin Hardware

Post by BurningTyre »

I understand from this topic:

https://community.home-assistant.io/t/d ... 270936/223

That there is a working solution for Home Assistant right now.

Im curious if there is anyone capable of converting this to a solution for Domoticz?
boppos
Posts: 3
Joined: Wednesday 09 March 2016 13:14
Target OS: Windows
Domoticz version:
Contact:

Re: Daikin Hardware

Post by boppos »

BurningTyre wrote: Tuesday 05 October 2021 13:58 I understand from this topic:

https://community.home-assistant.io/t/d ... 270936/223

That there is a working solution for Home Assistant right now.

Im curious if there is anyone capable of converting this to a solution for Domoticz?
Is anyone working on this? I am in the marked for an airco and daikin is good for my home. Is there a way to help integrating the new BRP069C4x in domoticz?
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

I had a look at it a few weeks ago, but haven't done anything yet. It's not as important to me anymore, because I just bought the old external controller (which fits neatly inside the case, out of sight) and an adapter cable for in total €100 and connected it through port S21 on the pcb. You can then use the already existing script and it works like a charm. The original wifi board is also still connected to the Daikin Residential Controller app, so it is now controllable through 2 different apps on my phone and Domoticz.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
boppos
Posts: 3
Joined: Wednesday 09 March 2016 13:14
Target OS: Windows
Domoticz version:
Contact:

Re: Daikin Hardware

Post by boppos »

Alain wrote: Wednesday 20 October 2021 13:04 I had a look at it a few weeks ago, but haven't done anything yet. It's not as important to me anymore, because I just bought the old external controller (which fits neatly inside the case, out of sight) and an adapter cable for in total €100 and connected it through port S21 on the pcb. You can then use the already existing script and it works like a charm. The original wifi board is also still connected to the Daikin Residential Controller app, so it is now controllable through 2 different apps on my phone and Domoticz.
This seems to be a good solution to me. Which unit do you use and which external controler. I see the BRP069B45 or do you have a different type?
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

BRP069B42 with Daikin S21 reducer kit voor Stylish
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
ksacca
Posts: 80
Joined: Thursday 31 May 2018 21:49
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Daikin Hardware

Post by ksacca »

As I've been waiting for a while for someone smarter than me to create a domoticz plugin for the new models, I started working on a node red flow to control daikin units using https://flows.nodered.org/node/node-red ... ikin-cloud. At first I wanted to try for myself if it could work, but then I started making an updated version that uses loops and variables so it could (in theory for now) work on any domoticz install.

The flow can read and set the state of multiple daikin units by looping the entire array returned by the daikin node. All needed settings for this to work (like the factory SSID of the unit) are automatically read from the cloud and stored in variables.

I have 5 different indoor units on 2 outdoor units (3 using BRP069C4x cloud only controller, 2 using BRP069B4x). All of them can be controller by this flow. For now I'm already able to set:
  • Power (on/off)
  • Target temperature setpoint (which is dependent on the current mode)
  • Operation mode (auto, cooling, heating, fanOnly, dry)
  • Fan direction (horizontal swing, vertical swing or 3D swing)
  • Fan speed (1, 2, 3, 4, 5, auto, quiet)
All this information is also retrieved from the cloud and devices are updated in domoticz (in case you used the app or remote to set the unit).
As the cloud can take a minute to update devices, there's a built in timeout. If you set any device through domoticz, the flow will stop reading data in the cloud for 3 minutes. This is to avoid having wrong states in domoticz. Of course you can just set multiple devices for your unit (on/off, temperature and mode). This wil not impact operations through domoticz.

You can also activate or deactivate the parse option. When deactivated, domoticz will not trigger scripts, mqtt, on/off actions, ... when a device was updated by cloud data. If you do want to trigger actions and the "avoid loop" option in domoticz MQTT is disabled, you can enable an option in the node red flow. Every time a device gets updated by the cloud, it's IDX is written to an array. When the flow receives an mqtt message from that device, it will first check if it was not just updated and discard the message if needed (and clear the IDX from the array). I needed this as I use homebridge, so the "prevent loop" option has to be disabled.

On top of the list above, the flow also reads the room temperature for each indoor unit, as well as the outdoor temperature (if you only have one outdoor unit you can only set 1 device for outdoor temperature by leaving the IDX blank).

I still have to add econo and powerful modes too (fairly easy to do). I didn't check the power readings yet as I have no idea how this works in domoticz (never used it before, except for zwave).

The data is sent and received using MQTT. On each update of the cloud (each minute in my case) there's an http call to domoticz to get the status of all devices (which is then stored in variables). This is used to compare what is available in the cloud so devices in domoticz are not updated if it's not needed. Unfortunately I couldn't find a way to retrieve only the status of devices of one specific dummy hardware (if someone knows how to do it, please let me know). Using getdeviceinfo using MQTT was not an option, as it would interfere with other incoming messages (I tried to filter it, but if a device was triggered at the same time in domoticz you could have strange behavior).

If credentials are needed, they can be set in the flow. A subflow is used (type credentials) so the username and password are encrypted in the node red config file. For now basic auth for domoticz is supported (in case you need username and password, otherwise leave blank). The data will be base64 encoded for you. You can also configure the username and password for the MQTT broker if required. On the first run (or at restart), the name and number of your units will be printed to the debug panel (for easier configuration).

For now you need to manually configure dummy devices in domoticz (switches, setpoints, temperature, selectors, ...) for each device you wish to control. You then need to enter the IDX's of those devices in the variables which are grouped per type. Other than that, everything is (or should be) automatic.

tldr: If anyone would be interested to test the flow once I'm finished I would be happy to share. Please let me know. It would be great if you have some node-red experience to debug if needed. The flow has been running succesfuly on my test setup for a few days. Still have to improve a few things and document some parts first though.
ccounotte
Posts: 9
Joined: Friday 15 December 2017 21:16
Target OS: Windows
Domoticz version:
Contact:

Re: Daikin Hardware

Post by ccounotte »

Hello all,

I have 3 units with old wifi controller attached to them, all configured in domoticz and working fine.

I just installed airco app from play store and it wants to update wifi controllers from v3.3.6 to v4.0.3.

Does anyone know if it's safe to update?

I'm trying to see if any controller will give me energy consumption at all.

Thanks.
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

Mine want updates, but I'm not doing it. Who knows what will be blocked. For all we know, the new firmware disables the S21 connector on the circuit board. My units work fine as they are, so I'm leaving them alone.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
Alain
Posts: 164
Joined: Sunday 26 April 2020 5:27
Target OS: Linux
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: Daikin Hardware

Post by Alain »

Oh, and I measure energy consumption with a Zigbee plug in the wall outlet.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
ccounotte
Posts: 9
Joined: Friday 15 December 2017 21:16
Target OS: Windows
Domoticz version:
Contact:

Re: Daikin Hardware

Post by ccounotte »

Thanks, won't update too! If it ain't broke don't fix it :)

I used to have a sonoff pow that worked for a few years but it suddenly broke and the pow R2 replacement just keep triggering the fuse so I can't use it anymore and was looking for a replacement and remembered that Daikin app could give some info about energy consumption.
ccounotte
Posts: 9
Joined: Friday 15 December 2017 21:16
Target OS: Windows
Domoticz version:
Contact:

Re: Daikin Hardware

Post by ccounotte »

Alain wrote: Monday 24 July 2023 22:31 Oh, and I measure energy consumption with a Zigbee plug in the wall outlet.
Are all ZigBee plugs compatible with domoticz? Found a ZigBee pow and some more recent ZigBee plugs that seem to have a better design.
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests