OpenDaikin Binding from MarketPlace Questions

kevin · November 12, 2018, 10:46pm

Try typing into a web browser http://ipAddress/aircon/get_control_info?
and post what you get back (if you put this in the middle of 3 lines with 5 spaces before it on your post it will go into the easier to read code format)
That should let @caffineehacker know whether your aircon is returning the fan information - mine doesn’t but I think most do

Riccardo_Ottolina · November 12, 2018, 11:37pm

 ret=OK,pow=0,mode=3,stemp=25.0,shum=--,dt1=25.0,dt2=--,dt3=25.0,dt4=25.0,alert=0,adv=,f_rate=3,dfr1=3,dfr2=-,dfr3=3,dfr4=3,dfr6=3

and
get_sensor_info?

 ret=OK,htemp=24,otemp=-,hhum=-,err=0

thank you!

kevin · November 12, 2018, 11:49pm

No fan information in there - sounds like we have the exact same problem. I’m currently using mine with a simple work around using the http binding in case you just want ON and OFF control. You can use something in a rule like

acHost = http://yourACipAddress:80/
var acCommandString = ""

rule "Turn AC ON"
when Item AC changed then
if (AC.state == ON){
    acCommandString = "aircon/set_control_info?pow=1&mode=0&stemp=18&shum=0"
    logInfo("DaikinPower", "acCommandString=" + acCommandString)
    logInfo("DaikinPower", "sendHttpGetRequest() returns: " + sendHttpGetRequest(acHost + acCommandString, 5000)) 
    }
if (AC.state == OFF){
    var acCommandString = "aircon/set_control_info?pow=0&mode=0&stemp=18&shum=0"
    logInfo("DaikinPower", "acCommandString=" + acCommandString)
    logInfo("DaikinPower", "sendHttpGetRequest() returns: " + sendHttpGetRequest(acHost + acCommandString, 5000)) 
    }
end

Hopefully the fixed binding will appear soon

caffineehacker · November 30, 2018, 4:06am

Interesting, it should be up on the Marketplace with the null pointer fix, but I admit I have no idea how OpenHab updates addons from the Marketplace so it might not be pulling the latest if you’ve installed it previously.

Edit: Looks like when the version bumped from 2.3 to 2.4 I needed to update where the jar was picked up from in the marketplace. I made the update so it should now be pointing to the most recent jar.

kevin · November 30, 2018, 7:13am

I’ve worked a solution out using the HTTP binding which is working well, although I’ll give your binding a test when I get chance. Is there any way to add extra receiving items to it such as compressor frequency which I’ve just added to my setup so I can work out the best way to get maximum cooling

Riccardo_Ottolina · December 1, 2018, 10:58am

Thank you!
I put the jar from https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.opendaikin/2.4.0-SNAPSHOT/ in the addons folder and it works ow!

thank you so much, I will test it further in next days!

Paul_Smedley · December 1, 2018, 8:44pm

This looks interesting. I just installed a Daikin BRP15B61 Wifi adapter for a Daikin ducted AC system.

The API looks similar but also a little different Using Wireshark I’ve discovered API per my post at https://forums.whirlpool.net.au/forum-replies.cfm?t=2768285

eg http://ipAddress/aircon/get_sensor_info? is http://ipAddress/skyfi/aircon/get_sensor_info? on the BRP15B61

Wondering if the opendaikin plugin could easily be modified to support multiple Daikin adapters?

Thanks!

Cheers,

Paul

noppes123 · December 31, 2018, 10:55am

The opendaikin binding works nice, again thanks for that @caffineehacker.

I did notice one small issue. When starting OH there are multiple warnings about wrong command type:

2018-12-31 10:59:57.235 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_84' on channel power
2018-12-31 10:59:57.235 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_84' on channel settemp
2018-12-31 10:59:57.635 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_84' on channel mode
2018-12-31 10:59:57.866 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_84' on channel fanspeed
2018-12-31 10:59:58.104 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_84' on channel fandir
2018-12-31 10:59:58.333 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_92' on channel power
2018-12-31 10:59:58.563 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_92' on channel settemp
2018-12-31 10:59:59.048 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_92' on channel mode
2018-12-31 10:59:59.075 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_92' on channel fanspeed
2018-12-31 10:59:59.303 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_92' on channel fandir
2018-12-31 10:59:59.418 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_85' on channel power
2018-12-31 10:59:59.669 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_85' on channel settemp
2018-12-31 11:00:00.133 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_85' on channel mode
2018-12-31 11:00:00.140 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_85' on channel fanspeed
2018-12-31 11:00:00.370 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_85' on channel fandir
2018-12-31 11:00:00.382 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_83' on channel power
2018-12-31 11:00:00.616 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_83' on channel settemp
2018-12-31 11:00:01.082 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_83' on channel mode
2018-12-31 11:00:01.089 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_83' on channel fanspeed
2018-12-31 11:00:01.315 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_83' on channel fandir
 ...

Not a big thing. Just wanted to report it (maybe something for a next release ).

Paul_Smedley · January 1, 2019, 4:59am

Yeah I see these too here with my recompiled version of the opendaikin binding for use with the AU Daikin Airbase adaptor. I haven’t yet had a chance to investigate why this happens.

Cheers,

Paul

rjduraocosta · January 14, 2019, 2:52pm

Hello to all,

I have been running OH in a windows 10 PC and after the upgrade from OH2.3 to OH 2.4 I experienced the following with this binding (from the events.log):

2019-01-14 08:43:50.979 [hingStatusInfoChangedEvent] - ‘opendaikin:ac_unit:acsuite’ changed from ONLINE to UNINITIALIZED
2019-01-14 08:43:50.997 [hingStatusInfoChangedEvent] - ‘opendaikin:ac_unit:acsuite’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

And the communication never recoverers again, I had to restart OH and after a few minuts the same again.
I had to go back to OH2.3.

Any ideas?

Thanks and best regards

Paul_Smedley · January 14, 2019, 8:48pm

I saw something similar when I updated to Openhab 2.4. a dependency for opendaikin wasn’t present in 2.4 and had to be installed manually.

Openhab.log probably has some clues.

Cheers,

Paul

rjduraocosta · January 17, 2019, 5:40pm

Thanks for your reply. After I did the upodate procedure again everything worked again.

Best regards.

fenderislife · April 18, 2019, 9:28pm

@caffineehacker Hello Tim,
any hope to have Daikin BRP069A81 supported in a future version on OpenDaikin?
I’m a total noob, but if anyone can tell me how I’m happy to help.
Opendaikin binding installs correctly on my OpenHab 2.4 (Raspberry PI - Raspbian) and recognizes my A/C machine, but it won’t do anything when I click.
Thank you again

noppes123 · April 18, 2019, 9:37pm

Any entries in the log files? If not you can enable debugging for the binding to see what’s going on. Perhaps that gives some clues…
I’ll check which device type I have tomorrow, for comparison, don’t recall the exect product number but its very similar to yours.

fenderislife · April 18, 2019, 9:40pm

Hello Ron, thank you for your answer.
As I wrote before, I’m a total noob. How can I see the log files? How can I enable debugging for the binding?
Sorry for my lack of knowledge.
Thank you

noppes123 · April 18, 2019, 9:47pm

If you know how to setup an SSH connection with the Pi, you should type the command:

tail -fn20 var/log/openhab2/events.log -fn20 /var/log/openhab2/openhab.log

and watch the logs while trying to control the AC.

fenderislife · April 18, 2019, 9:49pm

Thank you. I don’t have to use SSH since I have a monitor connected to my Pi.
I will do it as I return home and post the results here.
Thank you for your help.

fenderislife · April 19, 2019, 11:14am

Never mind Ron.
I had the 2.3 version installed, I really apologize for not having checked it before posting. Again, sorry for your loss of time.
I installed the 2.4 version, restarted OpenHab and now it works like a charm.

Unfortunately I still can’t control Setpoint and Mode parameters on the OpenHab 2 app for Android.

Here the log, if it can be of any help:

pi@raspberrypi:/ $ tail -fn20 var/log/openhab2/events.log -fn20 /var/log/openhab2/openhab.log
==> var/log/openhab2/events.log <==
2019-04-19 13:47:33.784 [vent.ItemStateChangedEvent] - opendaikin_ac_unit_192_168_1_123_power changed from ON to OFF
2019-04-19 13:48:17.428 [vent.ItemStateChangedEvent] - network_pingdevice_62aa5636_lastseen changed from 2019-04-19T13:47:17.124+0200 to 2019-04-19T13:48:17.396+0200
2019-04-19 13:48:49.396 [ome.event.ItemCommandEvent] - Item 'opendaikin_ac_unit_192_168_1_123_settemp' received command 21.5
2019-04-19 13:48:49.412 [nt.ItemStatePredictedEvent] - opendaikin_ac_unit_192_168_1_123_settemp predicted to become 21.5
2019-04-19 13:48:49.423 [vent.ItemStateChangedEvent] - opendaikin_ac_unit_192_168_1_123_settemp changed from 20.0 to 21.5
2019-04-19 13:48:55.485 [ome.event.ItemCommandEvent] - Item 'opendaikin_ac_unit_192_168_1_123_settemp' received command 20
2019-04-19 13:48:55.492 [nt.ItemStatePredictedEvent] - opendaikin_ac_unit_192_168_1_123_settemp predicted to become 20
2019-04-19 13:48:55.505 [vent.ItemStateChangedEvent] - opendaikin_ac_unit_192_168_1_123_settemp changed from 21.5 to 20
2019-04-19 13:49:17.533 [vent.ItemStateChangedEvent] - network_pingdevice_62aa5636_lastseen changed from 2019-04-19T13:48:17.396+0200 to 2019-04-19T13:49:17.515+0200
2019-04-19 13:49:35.841 [ome.event.ItemCommandEvent] - Item 'opendaikin_ac_unit_192_168_1_123_power' received command ON
2019-04-19 13:49:35.844 [nt.ItemStatePredictedEvent] - opendaikin_ac_unit_192_168_1_123_power predicted to become ON
2019-04-19 13:49:35.864 [vent.ItemStateChangedEvent] - opendaikin_ac_unit_192_168_1_123_power changed from OFF to ON
2019-04-19 13:49:37.543 [ome.event.ItemCommandEvent] - Item 'opendaikin_ac_unit_192_168_1_123_power' received command ON
2019-04-19 13:49:37.549 [nt.ItemStatePredictedEvent] - opendaikin_ac_unit_192_168_1_123_power predicted to become ON
2019-04-19 13:49:41.430 [ome.event.ItemCommandEvent] - Item 'opendaikin_ac_unit_192_168_1_123_power' received command OFF
2019-04-19 13:49:41.437 [nt.ItemStatePredictedEvent] - opendaikin_ac_unit_192_168_1_123_power predicted to become OFF
2019-04-19 13:49:41.444 [vent.ItemStateChangedEvent] - opendaikin_ac_unit_192_168_1_123_power changed from ON to OFF
2019-04-19 13:50:17.610 [vent.ItemStateChangedEvent] - network_pingdevice_62aa5636_lastseen changed from 2019-04-19T13:49:17.515+0200 to 2019-04-19T13:50:17.578+0200
2019-04-19 13:51:17.892 [vent.ItemStateChangedEvent] - network_pingdevice_62aa5636_lastseen changed from 2019-04-19T13:50:17.578+0200 to 2019-04-19T13:51:17.831+0200
2019-04-19 13:52:18.243 [vent.ItemStateChangedEvent] - network_pingdevice_62aa5636_lastseen changed from 2019-04-19T13:51:17.831+0200 to 2019-04-19T13:52:18.220+0200

==> /var/log/openhab2/openhab.log <==
2019-04-19 13:24:36.569 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_123' on channel mode
2019-04-19 13:26:36.270 [WARN ] [su.litvak.chromecast.api.v2.Channel ] - Got IOException while reading due to stream being closed (stop=true)
2019-04-19 13:26:36.401 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2019-04-19 13:26:43.907 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2019-04-19 13:26:43.948 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel
2019-04-19 13:26:43.958 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Stopped Home Builder
2019-04-19 13:26:43.982 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
2019-04-19 13:27:53.171 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2019-04-19 13:27:53.391 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2019-04-19 13:27:53.536 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to '41.857676,12.4549021'.
2019-04-19 13:28:09.286 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-04-19 13:28:11.242 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'chromecast:chromecast:dbc49f231be46b9ba4d5916913ab3fb2' to inbox.
2019-04-19 13:28:11.264 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'opendaikin:ac_unit:192_168_1_123' to inbox.
2019-04-19 13:28:11.634 [WARN ] [lipse.smarthome.io.net.exec.ExecUtil] - Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "arping" (in directory "."): error=2, File o directory non esistente)
2019-04-19 13:28:13.978 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_123' on channel power
2019-04-19 13:28:13.984 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_123' on channel settemp
2019-04-19 13:28:14.104 [WARN ] [ikin.handler.OpenDaikinAcUnitHandler] - Received command of wrong type for thing 'opendaikin:ac_unit:192_168_1_123' on channel mode
2019-04-19 13:28:14.622 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.1.122:8080
2019-04-19 13:28:14.626 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.1.122:8443
2019-04-19 13:28:15.277 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui

This is what I get when I type http://192.168.1.123/aircon/get_control_info? in Chromium:


ret=OK,pow=0,mode=3,stemp=20.0,shum=--,dt1=20.0,dt2=--,dt3=20.0,dt4=20.0,alert=0,adv=,f_rate=3,dfr1=3,dfr2=-,dfr3=3,dfr4=3,dfr6=3

And this is what I get when I type http://192.168.1.123/aircon/get_sensor_info?

ret=OK,htemp=23,otemp=23,hhum=-,err=0

Thank you

mtrax · June 4, 2019, 11:27am

Hi is there support for the BRP15B61 wifi module?
and where do I get latest stable version of this addon?

noppes123 · June 4, 2019, 7:42pm

You can find the ‘beta’ version in this post.
Lately the author of the binding doesn’t seem to be working on migrating it to the new build system and actively maintain it. To my knowledge there is no new version.

As far as support for BRP15B61 is concerned, that’s a matter of testing. Many WiFi models seem to be based on the same API.