Extra Sensors: Difference between revisions

286 bytes added ,  08:16, 9 September 2021
m
Line 7: Line 7:
''Extra Sensors'' is a feature already present in Cumulus 1. Ignored for long time by CumulusUtils, with the rise of the [https://www.ecowitt.com/shop/homePage Ecowitt ecology] and the support of CumulusMX for the GW1000 (and higher) devices, it has been decided to make ''Extra Sensors'' a standard module of CumulusUtils.  
''Extra Sensors'' is a feature already present in Cumulus 1. Ignored for long time by CumulusUtils, with the rise of the [https://www.ecowitt.com/shop/homePage Ecowitt ecology] and the support of CumulusMX for the GW1000 (and higher) devices, it has been decided to make ''Extra Sensors'' a standard module of CumulusUtils.  


''Extra Sensors'' have a certain complexity because they are divers, not configured (or only partly) by the user and there is a lot of redundancy in the logging while another sensor is not being logged (lightning). For the obvious reason of the absence of a log, the lightning sensor will be ignored by CumulusUtils.  
''Extra Sensors'' have a certain complexity because, although handled by CumulusMX, they are kind of anarchic: unregulated, CumulusMX does not care, when detected they are always displayed only logged when logging is switched on and then not all of them are logged. There are more webtags than logged sensors etc... This complexity made some additional handling necessary.


Please read the paragraph operation carefully and report any difficulty in operating the module both in this Wiki, from within the website or as a module.
For the obvious reason of the absence of a log, the lightning sensor will be ignored by CumulusUtils as are additional sensors which  can not be logged (like e.g. LeafTemp3 and 4).
 
Please read the paragraph operation carefully and report any difficulty in operating the module both in this Wiki, from within the website or otherwise. I think all cases are covered but you never know.


== Operation ==
== Operation ==