Homey Community

Daikin AI

app

#21

Hi,

ret=OK,pow=1,mode=4,adv=,stemp=17.0,shum=0,dt1=25.0,dt2=M,dt3=25.0,dt4=17.0,dt5=17.0,dt7=25.0,dh1=AUTO,dh2=50,dh3=0,dh4=0,dh5=0,dh7=AUTO,dhh=50,b_mode=4,b_stemp=17.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=5,dfr4=A,dfr5=A,dfr6=5,dfr7=5,dfrh=5,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0


#22

Thanks, at least this proves that the protocol in unchanged which makes me somewhat hopefull… To further investigate the issue I still need access to a Type B adapter…

For now all I can say don’t expect the problem to be solved soon, if it can be fixed at all by me (Daikin does not document its interface).


#23

Update: a fellow Daikin AI app user was so kind to lend me his type B adapter, meaning that I am now able to troubleshoot the issue in detail and hopefully find a solution for it.

I have installed this adapter into my own Emura 2 and as expected I am also unable to pair with my Emura 2. However before I tried it to pair I updated my Airconditioners IP address setting with that of the type B adapter (which was assigned a new IP-address through DHCP…) and as expected I have no problem of controlling my Emura 2, so it seems that the issue is limited to pairing.

Advice: after updating your firmware do NOT remove the already paired device when you can not control the airconditioner but first check that the IP address that is used is correct from the settings menu and update that as needed. If it is okay, reboot Homey etc but in no case remove the already paired device (as pairing is broken for now).

![P


#24

Update: A fix is currently being tested by my Alpha version testers, if all goes well I will submit this version (v1.1.3) as beta version to the Athom app store early next week.

November 28th update: version 1.1.3 is now available in the Homey App Store as beta. This version will be promoted to stable after 2 weeks unless major problems are reported by beta version users.


#27

Hi Peter.
Seems not to work with Homey v2.
All flows are broken.

Christoph


#28

Hi Christoph, with Homey v2 you mean firmware v2?

Broken flows happen unfortunately when upgrading / switching between beta / stable version. Solution: pair airco device again and fix/repair your broken flows in that case. Inconvenient for sure but nothing I can do about it.


#29

Yes Peter I mean firmware v2.

Re-adding the device did partually resolve the issue.
Now I stuck to a homey error when saving the flow.

So I guess your part is working.


#30

May I ask what is the fundamental difference in this new B model firmware version?
I’ve been investigating this issue in other services and your help you be very much appreciated.
Tks


#31

HTTP requests, i.e. http://xxx.xxx.xxx.xxx/aircon/get_control_info, respond with a 403 (forbidden) iso 200 (OK) statuscode.


#32

First of all, thanks for the tip. However, I have been trying to replicate the problem and seems like (at least manually) all GET commands are returning 200 to the calls.


#33

Making these calls via a browser indeed returns 200, however same call using this https://github.com/request/request library returns a 403. Good luck troubleshooting your issue.


#34

Dear Peter,

Thank you so much. Indeed… the calls over browser works perfect but through any REST calls it fails with 403.

Another interesting thing: you can telnet port 80 and keep it open until you done in A-type devices but in B-type devices, the connection is closed as soon as you connect to.

If you don’t mind, what was you workaround?


#35

Nevermind Peter!

If you send the header with HOST in capital letters you get 403. If you do Host: it works!
Crazy behaviour. With A-type it doesnt matter what you use.

Thanks for the support!


#36

v1.1.3 just upgraded to the stable channel.