This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
Note: besides fixing the bug, this version (v0.6.1) also adds support for the Daikin Comfora series.
Anyone that would like to test v1.0.0 send me a PM so I can give you access to the alpha branch.
Dus werkt hij niet .
Word de module BRP06B tzt nog toegevoegd?
enter this:
http://192.168.2.163/aircon/get_control_info ;
(replace 192.168.2.163 with the IP-address of your Airco)
url in your browser you should see a response like:
ret=OK,pow=0,mode=4,adv=,stemp=24.0,shum=0,dt1=24.0,dt2=M,dt3=21.5,dt4=24.0,dt5=24.0,dt7=24.0,dh1=0,dh2=0,dh3=0,dh4=0,dh5=0,dh7=0,dhh=50,b_mode=4,b_stemp=24.0,b_shum=0,alert=255,f_rate=A,f_dir=0,b_f_rate=A,b_f_dir=0,dfr1=A,dfr2=B,dfr3=A,dfr4=A,dfr5=A,dfr6=A,dfr7=A,dfrh=5,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=3,dfd7=0,dfdh=0
Please answer this question first....
if it does not response
1/ check your IP-address first...
2/ if it does, check under setting that demo mode is off
Can you elaborate on what the problem exacly is? Does nothing work or what do you see / not see?
The Daikin unit is perfectly accessible through the Daikin app.
My homey can sometimes read the temperature: it can see if I change the temperature by means of the IR remote control but can't see any of the other setting (operation mode; swing on/off).
The ping to the configured IP is responsive:
What ever variable is changed via the IR remote control (or app) is visualised in the Homey:
Temperature/Fan speed/Operation mode/swing position
However, I cannot change them through the Homey in the field shown in the picture...
The type B WiFi adapter (BRP069Bxx) is NOT supported at this moment by the Daikin AI app, I am working on a solution. However I am not sure if the issue can be fixed at all nor how long this will take, till now all my attempts to fix it failed...
Special thanks to @bobje89, one of my App users, who was so kind to lend me his type B adapter to trouble shoot.
Depending on the feedback of the alpha version testers I will likely publish it on Wednesday (23/5) as Beta (with little or no change) to the Homey App Store, approval will take between 5 and 10 days.
Users of the Inverter model are advised to switchover to the Comfora model.
Question: can the user that experienced this crash sent me a PM with a screenshot of Homey its memory usage, report the amount of apps installed on Homey etc.? Thanks in advance.
Tip: after making the screenshot... give your Homey a fresh start by pressing the restart button.
I have an inverter, BRP069B adapter. Homey is receiving the information but is not able to send commands.
When I turn the AC on via the Daikin app, the Homey will detect the settings but I cannot turn on or off the AC via Homey. I have tried different settings for the "fw <= v2.0.1" but with no avail.
Anyone is experiencing the same?
Daikin AI v1.0.5 only partially fixes the type B adapter problem, action flows cards do not work due to a software bug. I identified the cause of the problem and am now testing the fix.
2018-05-28 13:59:20 [log] [ManagerDrivers] [emura] [0] Emura ip-address: 192.168.0.32
Suggestion for this user:
1/ remove your emura airco (with name "Klima Schlafzimmer") from Homey
2/ give Homey a fresh start from Homey's settings menu
3/ pair your Emura airco again and ensure that the refresh interval is set to 10 seconds.
Please report if this fixes the issue.
Will report if an issue accours.
Incorrect refresh interval
Correct refresh interval
I want to thank you once more for your outstanding support and the really excellent working 1.0.7 "alpha" Daikin App.
It is going to get a cool summer now ;.)
Christoph
Last couple of weeks, with the extreme warm weather in the Netherlands, many of you started for the first time actually using the app, building flows etc and as a result a couple of software bug surfaced. Together with the help of a couple of alpha version testers I was able to crush these bugs. Likely after the weekend I will submit v1.0.8 to the app store for approval.
I also would like to point out that v1.0.5 caused some unexpected side affects which could lead to application crashes, when this happens see my may 28th post.
Known bugs (in v1.0.5)
Fixed in v1.0.8