Begonnen von roelb, 26 März 2020, 19:16:24
Zitat von: hugomckinley am 04 April 2020, 13:36:37My solution would be the "normal" behavior of other FHEM modules.
ZitatIf you want to know, if the readings are current, you could introduce a last-successful-poll reading
ZitatI agree with you, that the usecases are very different, but I still think 10sec are not the usual case.
Zitatit would not generate events in the log, but if not that would be too much entries in the filelog/dblog. But if it is documented users can decide their intervals correctly. I am a friend of slim databases and of not doing things that are not necessary
define <devicename>_LOG FileLog <filename> <devicename>:(pwr.*_last|pwr_year_cur|power|pow|cmpfreq|mompow|stemp|shum|mode|rate|swing|powerful|streamer|econo|.*_ifchanged:.*
ZitatI would suggest to generate the attributes for the intervals when the device is defined, so the user can see the values imediately in the device.
2020.04.05 18:18:22 2: AC_WZ_OG HVAC_DaikinAC_Poll(): failed (HVAC_DaikinAC_Poll) - Timeout while attempting to poll 192.168.64.5 (Timeout: process terminated)
Zitat von: markusphi am 06 April 2020, 13:43:39PERL WARNING: Argument "interval=180" isn't numeric in int at ./FHEM/58_HVAC_DaikinAC.pm line 110.2020.04.05 22:39:40 3: AC_s_WZ: internal interval timer stopped180 <> numeric?
Syntax: define <name> HVAC_DaikinAC <hostname/ip> [interval=60] [interval_powered=10]
define MY_DEVICE_NAME HVAC_DaikinAC 22.214.171.124 300 120
Zitat von: hugomckinley am 05 April 2020, 20:02:37I think the problem is not the value of the timeout, but the unit doesn't answer at all.Is it possible to make a second try before logging this error?
Zitat von: roelb am 06 April 2020, 17:16:33I'll update the usage error and documentation with a couple of examples to clarify this.