ERROR: Unknown wireless control state: dmnd_run = 0

[FulvioSpelta]

Hi i've immediately used your .jar (thanks a lot for it) and i got the error:

java -jar daikin-mqtt-1.0.0-jar-with-dependencies.jar

11:41:55.182 [main] INFO  org.magcode.daikin.DaikinMqttClient - Loading properties from C:\Users\A130754\Dropbox\Sviluppo\_Tests\daikinmqtt/daikin.properties
11:41:55.549 [main] INFO  org.magcode.daikin.DaikinMqttClient - Connected to MQTT broker.
11:41:55.561 [main] INFO  org.magcode.daikin.DaikinMqttClient - Subscribed to daikintest/ac-room1/aircon/+/set
Exception in thread "main" java.lang.IllegalArgumentException: Unknown wireless control state: dmnd_run = 0
        at net.jonathangiles.daikin.wireless.WirelessDaikin.readDaikinState(WirelessDaikin.java:123)
        at net.jonathangiles.daikin.DaikinBase.<init>(DaikinBase.java:45)
        at net.jonathangiles.daikin.wireless.WirelessDaikin.<init>(WirelessDaikin.java:19)
        at net.jonathangiles.daikin.DaikinFactory.createWirelessDaikin(DaikinFactory.java:22)
        at org.magcode.daikin.DaikinMqttClient.main(DaikinMqttClient.java:61)

Maybe it can be a problem related to the wireless adapter or firmware revision.

The response the the services:

aircon/get_control_info
ret=OK,pow=0,mode=3,adv=,stemp=24.0,shum=0,dt1=25.0,dt2=M,dt3=24.0,dt4=25.0,dt5=25.0,dt7=25.0,dh1=AUTO,dh2=50,dh3=0,dh4=0,dh5=0,dh7=AUTO,dhh=50,b_mode=3,b_stemp=24.0,b_shum=0,alert=255,f_rate=5,f_dir=0,b_f_rate=5,b_f_dir=0,dfr1=5,dfr2=5,dfr3=5,dfr4=5,dfr5=5,dfr6=5,dfr7=5,dfrh=5,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0,dmnd_run=0,en_demand=0

aircon/get_model_info
ret=OK,model=0000,type=N,pv=3.20,cpv=3,cpv_minor=20,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=1,temp=1,temp_rng=0,m_dtct=1,ac_dst=--,disp_dry=0,dmnd=1,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=7,en_ipw_sep=1,en_mompow=0,hmlmt_l=10.0

If you like to go deeper and maybe support this device I can provide you the complete set of calls and support for testing.

Let me know and thanks again. f

[magcode]

Hi, this seems to be known issue in the underlying library. I can fix this. Will take some time. Do you know what Wifi adapter you have?

[FulvioSpelta]

Please be patient a while: asap i'll post the device label.

[FulvioSpelta]

Hi, here the info of the WiFi controller I'm using. I bought it a couple of years ago.

[magcode]

Yeah. Its different to mine. I'll provide an improved version within the next days. Lets see if it works with your controller...

[FulvioSpelta]

Attached the full set of response to the documented uri called having the split in idle state, Feel free to ask if you need something. Thanks

Daikin.pdf Daikin.xlsx

[magcode]

Can you try with the latest release 1.0.1 please?

[FulvioSpelta]

Hi, thanks for your time. I've started the tests, the 1.0.1 version is started regularly and it is publishing data from my 2 splits. During the day I'll check continuity of service, data and commands and let you know the results.

To stress a bit i've set refresh interval at 30 sec.

[FulvioSpelta]

After some hours running i've found that the number of msgs publish is different depending on topic; here the full count of msgs for 1 split:

Etichette di riga	Conteggio di id
daikintest/notte/$fw/name	12
daikintest/notte/$fw/version	12
daikintest/notte/$homie	12
daikintest/notte/$implementation	12
daikintest/notte/$localip	12
daikintest/notte/$name	12
daikintest/notte/$nodes	12
daikintest/notte/$state	256
daikintest/notte/$stats/interval	12
daikintest/notte/$stats/uptime	256
daikintest/notte/aircon/$name	12
daikintest/notte/aircon/$properties	12
daikintest/notte/aircon/$type	12
daikintest/notte/aircon/fan	256
daikintest/notte/aircon/fan/$settable	12
daikintest/notte/aircon/fandirection	256
daikintest/notte/aircon/fandirection/$settable	12
daikintest/notte/aircon/intemp	256
daikintest/notte/aircon/mode	256
daikintest/notte/aircon/mode/$settable	12
daikintest/notte/aircon/otemp	256
daikintest/notte/aircon/power	256
daikintest/notte/aircon/power/$settable	12
daikintest/notte/aircon/targettemp	256
daikintest/notte/aircon/targettemp/$settable	12

The topics having 256 messages have been published every 30 sec, the others every 10 minutes. I suppose that is ok for the homie convention. Next things in further posts in order to have the topic separated

[magcode]

indeed, the homie convention divides messages into the "device" and the "nodes". I declared this "program" as the "device" and the wifi adapters as the nodes. The device information does not change often so I hardcoded it with a 10 min update. You usually don't need to care about the device messages. (Unless you want to implement some "autodiscovery".

[FulvioSpelta]

LWT

Moved in new issue #3

[FulvioSpelta]

MQTT Reconnect

Moved in new issue #4

[FulvioSpelta]

Device unreachable Moved in new issue #5

[FulvioSpelta]

Note: I don't want to bother you, I'm trying to give an help to the test in field. Feel free to ignore me :-)

[FulvioSpelta]

I'll open every single report ad separate issue in order to have contextualized comments. You'll see here the deleted messages.