Commands not executed about daikin-mqtt HOT 9 CLOSED

Thanks for reporting. Indeed. While

yourac/aircon/power/set true works, the other commands do not work for me as well. Will check and fix.

from daikin-mqtt.

I have refactored the daikin connector quite a bit. Will test in the next days/weeks. If you want a preliminary release, let me know.

from daikin-mqtt.

Thanks. Give me the prerelease if you think that my tests can help you.
Otherwise I'll wait for your next final release.

from daikin-mqtt.

Its available now. Please note: internally I changed many things. So expect some new issues.
Thanks for testing and contribution!

from daikin-mqtt.

Sorry for late feedback; i'm a bit busy at work. I'll post test result asap

from daikin-mqtt.

Hi, sorry again to be late. I've done some tests and it seems all ok.
Following the tests and few notes.
Thanks

topic: targettemp/set
Sent variuos msgs with different temperature, split status power off - ok
Note: the new temp is applied but the topic targetemp is updated using the standard cycle so you haven't immediate feedback of the change
Log:

2020-06-21 09:22:28.130 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending targettemp=25.0 to giorno
2020-06-21 09:23:01.978 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending targettemp=26.0 to giorno
2020-06-21 09:23:29.049 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending targettemp=24.0 to giorno
2020-06-21 09:27:23.555 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending targettemp=26.0 to giorno

Topic: fan/set
Sent variuos msgs with different fan speed (F1 to F4), split status power off - ok
Note: the new temp is applied but the topic fan is updated using the standard cycle so you haven't immediate feedback of the change
One command has not been executed by the split but i think it's ok, this kind of adapter somtimes doesn't answer the service calls (verified using my own script)
Log

2020-06-21 09:30:47.844 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F1 to giorno
2020-06-21 09:31:03.066 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F4 to giorno - no set
2020-06-21 09:31:25.627 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F4 to giorno
2020-06-21 09:32:34.562 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F3 to giorno

Topic: mode/set
Sent variuos msgs with different set (F1 to F4), split status power off - ok
Note: the new temp is applied but the topic fan is updated using the standard cycle so you haven't immediate feedback of the change
Log

2020-06-21 09:30:47.844 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F1 to giorno
2020-06-21 09:31:03.066 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F4 to giorno
2020-06-21 09:31:25.627 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F4 to giorno
2020-06-21 09:32:34.562 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending fan=F3 to giorno

Inital status: power Off, mode Cool -> published command "Dry" -> final status: power On, mode Dry

2020-06-21 09:34:07.677 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending power=on to giorno
2020-06-21 09:34:08.626 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending mode=Dry to giorno
Note: changing the mode has powered on the split

Inital status:power On, mode Dry -> published command "cool" (note the wrong command) -> final status: power Off, mode Dry

2020-06-21 09:34:31.266 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending power=off to giorno
2020-06-21 09:37:29.900 [MQTT Call: client-for-daikin-on-IT000000682235] INFO 
org.magcode.daikin.mqtt.Subscriber - Sending power=off to giorno

Note: sending an incorrect command (cool vs Cool) has powered off the split

Inital status: power Off, mode Dry -> published command "Cool" -> final status: power On, mode Cool

2020-06-21 10:01:17.578 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending power=on to giorno
2020-06-21 10:01:18.517 [MQTT Call: client-for-daikin-on-IT000000682235] INFO  org.magcode.daikin.mqtt.Subscriber - Sending mode=Cool to giorno

Topic: power/set
Inital status: power On, mode Cool -> published command "Off" -> final status: power Off, mode Cool
2020-06-21 10:02:06.642 [MQTT Call: client-for-daikin-on-IT000000682235] INFO org.magcode.daikin.mqtt.Subscriber - Sending power=Off to giorno

Inital status: power Off, mode Cool -> published command "On" -> final status: power On, mode Cool
2020-06-21 10:07:26.402 [MQTT Call: client-for-daikin-on-IT000000682235] INFO org.magcode.daikin.mqtt.Subscriber - Sending power=On to giorno

from daikin-mqtt.

Just a note for readme. The topic power/set is not present int the list of topic to send commands:

from daikin-mqtt.

The only thing that seems not comfortable is the automatic "power On" when changing the mode.
Usually i prefer to have "specific" commands without broader effects

from daikin-mqtt.

I'll close this issue; this new version seems very good.
I'll bring in "production" stage

Thanks for your work.

from daikin-mqtt.