Perfect.  Thanks.  That's what I was looking for.

On Saturday, January 9, 2021 at 8:11:23 PM UTC-8 gjr80 wrote:

> OK, maybe I am mis-reading your post and what you want/expect to 'see'. 
> When I said "*displaying the GW1000 and sensor configuration information 
> currently only available through the WS View app*" I meant everything you 
> can access under the menu in the top right hand corner of the WS View App 
> (believe that is the '*More*' menu in both the Android and Apple apps). 
> The --get-xxxx command line options should correspond closely to the item 
> names under the '*More*' menu and each should present the same info on 
> screen as fund under the respective '*Menu*' sub-menu. You certainly 
> should be able to see calibration offsets but of course not in --live-data 
> or loop packets.
>
> The release notes from the v0.2.0 release on GitHub gives a better run 
> down:
>
>    - added --get-services command line option to display GW1000 supported 
>    weather services settings
>    - added --get-pm25-offset command line option to display GW1000 PM2.5 
>    sensor offset settings
>    - added --get-mulch-offset command line option to display GW1000 
>    multi-channel TH sensor calibration settings
>    - added --get-soil-calibration command line option to display GW1000 
>    soil moisture sensor calibration settings
>    - added --get-calibration command line option to display GW1000 sensor 
>    calibration settings
>    - renamed --rain-data command line option to --get-rain-data
>
>
> Gary
> On Sunday, 10 January 2021 at 13:15:58 UTC+10 vince wrote:
>
>> My gear is all working fine.  I probably misread your note a bit, 
>> thinking that "*displaying the GW1000 and sensor configuration 
>> information currently only available through the WS View app*" included 
>> seeing the calibration offsets we do in their app after finding them buried 
>> down in that brutal GUI they provide.   I did see the --sensors option 
>> which was pretty interesting though.  No problems here at all.  Works 
>> great.  Thanks.
>>
>> On Saturday, January 9, 2021 at 1:48:13 PM UTC-8 gjr80 wrote:
>>
>>> On Sunday, 10 January 2021 at 07:37:10 UTC+10 vince wrote:
>>>
>>>> On Saturday, January 9, 2021 at 12:20:38 PM UTC-8 gjr80 wrote:
>>>>
>>>>> On Sunday, 10 January 2021 at 05:44:27 UTC+10 vince wrote:
>>>>>
>>>>>> Works great here, thanks.   Also liked the wiki pages.
>>>>>>
>>>>>> I noted the new (?) _sig values in --live-data
>>>>>>
>>>>> Mine all show a value of 4
>>>>>>
>>>>> I'm assuming the values are 0-4 where 4 is best (???)
>>>>>>
>>>>> The Sensor battery states 
>>>>> <https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states> 
>>>>> wiki page provides details on sensor battery states reported by the 
>>>>> driver; 
>>>>> basically the meaning depends on the sensor concerned.
>>>>>
>>>>
>>>> Yes, saw that...but I was asking about the sig(nal?) status fields in 
>>>> the new version.
>>>>
>>>
>>> Yes you did, sorry too early here. The API documentation provides no 
>>> real info on what signal level means, my understanding is it is not a true 
>>> signal level like we normally understand signal level to be, but rather it 
>>> is an indicator of whether the most recent broadcasts have been received 
>>> from the sensor. But yes more is better.
>>>
>>>
>>>> And are the calibration things available in the --live-data information 
>>>> ?
>>>> I have my sensors slightly calibrated, but don't see any of that info 
>>>> in the --live-data output.
>>>>
>>>> GW1000 live sensor data: absbarometer: 1014.3, datetime: 1610218338, 
>>>> humid1: 38, humid2: 41, inhumid: 39, intemp: 21.1, outhumid: 98, outtemp: 
>>>> 1.4, relbarometer: 1025.8, soilmoist1: 38, temp1: 20.7, temp2: 19.7, 
>>>> wh26_batt: 0, wh26_sig: 4, wh31_ch1_batt: 0, wh31_ch1_sig: 4, 
>>>> wh31_ch2_batt: 0, wh31_ch2_sig: 4, wh51_ch1_batt: 0, wh51_ch1_sig: 4
>>>>
>>>> I guess I'm struggling a little with how to display all the new cool 
>>>> stuff and what the units are, especially since the API isn't public yet it 
>>>> seems.
>>>>
>>>
>>> Calibration data is not explicitly included in the —live-data output, 
>>> though any relevant calibration data should have been applied to sensor 
>>> data in the —live-data output. I have not explicitly tested that though. 
>>> What units do you have a problem with?
>>>  
>>> Gary
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f89edc7f-ac10-4195-98d8-132da75c7eb6n%40googlegroups.com.

Reply via email to