Autor Thema: New module: DaikinAC  (Gelesen 4230 mal)

Offline wulfmain

  • New Member
  • *
  • Beiträge: 11
Antw:New module: DaikinAC
« Antwort #45 am: 11 Juni 2020, 23:54:57 »
Works perfect. Thank you so much! I really appreciate your Great work!
Raspberry Pi mit FHEM & Tablet UI, CUL, MySensors, Homematic-Komponenten, AVM-Komponenten, Onkyo AV Receiver, VuUltimo 4k, Volumio, Synology ...

Offline realkev

  • New Member
  • *
  • Beiträge: 13
Antw:New module: DaikinAC
« Antwort #46 am: 14 Juni 2020, 11:22:12 »
The error message that you are getting seems clear: the airco unit closes the HTTP connection but did not sent any data. So the module got an empty response where it was expecting status data. That is not a big issue, if a failure happens on a poll you'll just miss one interval. For a set, the set will fail and you'll need to retry.

What you're seeing is definitely an issue in the Daikin wifi control unit. I haven't seen that issue.  You might try doing a couple of manual requests to the control interface and see if you can replicate that.

I've been thinking about implementing an automatic immediate retry whenever the request to the unit fails. However, that is a bit more complex than it seems due the asynchronous nature of the requests to the unit, using nonblocking IO. So an automatic retry will require some architectural changes in the module. It's on the todo list, so whenever I can find the time to rework this into the module, I will.

Hi Roelb,

thanks for your feedback, the empty responses weren't causing a significant issue within my system, nevertheless I am facing some other problems with the module at the moment:

2020.06.14 05:48:47 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 8504
2020.06.14 05:48:47 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 8503
2020.06.14 05:48:47 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 8502
2020.06.14 05:25:52 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 7597
2020.06.14 05:25:52 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 7596
2020.06.14 05:25:52 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 7595
2020.06.14 05:02:51 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 6685
2020.06.14 05:02:51 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 6684
2020.06.14 05:02:51 1: Timeout for HVAC_DaikinAC_Write reached, terminated process 6683

Is there any maximum of commands being defined in certain period of time?
I am using a DOIF to regulate the temperature in a room by controlling the AC...

Best regards,
Kevin

Offline roelb

  • Developer
  • New Member
  • ****
  • Beiträge: 30
Antw:New module: DaikinAC
« Antwort #47 am: 14 Juni 2020, 11:35:33 »
This might be a concurrency issue. As my module uses the FHEM nonblocking features for all requests, firing multiple requests at the same time (through some form of automation) will fork any number of processes that in turn perform the actual request to the aircon unit.

Daikin uses a AzureWave AW-CU300 integrated module for their Wifi controllers. This contains a Marvell 88MW300 microprocessor. I don't know what they have implemented in terms of handling concurrent requests. However, I can't get any of their units to fail in my own installation, whatever number of requests I fire at them.

Try adding 100ms of sleep in between your automated requests. If you have multiple Doif's that trigger on the same event, try adding different short delays to each of them so that they don't fire at /exactly/ the same time.