[weewx-user] Re: yet another question to GW1000 api driver mapping

On Sunday, December 20, 2020 at 12:03:05 PM UTC-8 gjr80 wrote: > You are indeed lucky (fortunate?) that your TH32 sensor ID is ‘32’, mine > is ‘e4’. I'm on the correct side of the equator, use a non-metric unit system, and the one true RF band (915MHz) :-) Dunno if that matters any re: the ha

[weewx-user] Re: yet another question to GW1000 api driver mapping

You are indeed lucky (fortunate?) that your TH32 sensor ID is ‘32’, mine is ‘e4’. Gary On Monday, 21 December 2020 at 04:53:12 UTC+10 vince wrote: > Yes - works great as-is.Running the --live-data check makes it very > easy to figure out what to map to what. > > FWIW, my EcoWitt app shows

[weewx-user] Re: yet another question to GW1000 api driver mapping

Yes - works great as-is.Running the --live-data check makes it very easy to figure out what to map to what. FWIW, my EcoWitt app shows it as a "T&H ID: 32" in their very difficult to figure out mobile app under Menu => DeviceList, then clicking on my gateway id there, then hitting More =>

[weewx-user] Re: yet another question to GW1000 api driver mapping

Yes I'm aware of the WH26/WH32 issue, I have a WH32 myself. Interestingly the GW1000 API does not mention the term 'WH32' anywhere.In fact, to date I have not seen 'WH32' mentioned anywhere on the Ecowitt.net display/dashboard nor anywhere in the WS View app. The closet I have seen WH32 being '

[weewx-user] Re: yet another question to GW1000 api driver mapping

Gary - this thread got me thinking of adding battery status to my minimal EcoWitt skin (GitHub link) I have a GW1000 and a WH32 outdoor sensor and run weewx 4.2.0 dpkg raspi using 0.1.0b12 of your driver. pi@pi3jr:~ $ PYTHONPATH=/usr/share

[weewx-user] Re: yet another question to GW1000 api driver mapping

> [[field_map_extension]] >txBatteryStatus = wh65_batt > > and the entry in the stanza [Accumulator] accordingly, wrote back an > untouched copy of seasons.inc, uncommented the original label in > skins.conf, and voila, after weewx restart, everything looks ok. Although, > I would have

[weewx-user] Re: yet another question to GW1000 api driver mapping

Ok, this is the missing point. Actually, I hesitate because of this highlight in the Customization Guide: *Warning!* Make a backup of the data before doing any of the next steps! -

[weewx-user] Re: yet another question to GW1000 api driver mapping

The penny drops. Have you added wh65_battery to your database schema? $current.wh65_battery will work without wh65_battery being in your schema but $day.wh65_battery requires wh65_battery be in your schema. Refer to Adding a new type to the database

[weewx-user] Re: yet another question to GW1000 api driver mapping

Thanks, Gary. The typo was here, not in seasons.inc. But I had another assumption: When displaying the values $current.txBatteryStatus.raw and $current.wh65_battery.raw , I could see, that the first one was empty, and only the second value was existent. My assumption was, that $ day.txBatterySt

[weewx-user] Re: yet another question to GW1000 api driver mapping

Peter, Your understanding is correct. The logic in the code now appears correct but I think you are using the incorrect field name. Earlier you posted an archive record: REC:2020-12-16 13:30:00 CET (1608121800) altimeter: 30.09246486970751, appTemp: 46.07291271146897, barometer: 30.0921696

[weewx-user] Re: yet another question to GW1000 api driver mapping

Aaah, now I start to understand! The first part is just a definition. Got it! Thanks In skin.conf stanza [Labels] [Generic] I found txBatteryStatus = Transmitter I replaced the left side with wh65_batteryStatus In Seasons.inc I found: #set $have_battery_status = 0 #for $x in

[weewx-user] Re: yet another question to GW1000 api driver mapping

No, I did not say to change the get_battery_status() definition, what I sad was that elsewhere in your template, where you call get_battery_status(), you need to call it using $get_battery_status($current.wh65_battery.raw). You should put the get_battery_status() definition back how it was. sen

[weewx-user] Re: yet another question to GW1000 api driver mapping

Typo: $get_battery_status($current.wh65_battery.raw), of course with closed brakets Vetti52 schrieb am Donnerstag, 17. Dezember 2020 um 11:01:26 UTC+1: > Ok, I added the entries into accumulator. So, this part is completed now. > But still the battery value is missing. > > The construct in sen

[weewx-user] Re: yet another question to GW1000 api driver mapping

Ok, I added the entries into accumulator. So, this part is completed now. But still the battery value is missing. The construct in sensors.inc #def get_battery_status($x) #if $x == 0 $get_battery_status($current.wh65_battery.raw : GOOD #else $get_battery_status($current.wh65_battery.raw : LOW

[weewx-user] Re: yet another question to GW1000 api driver mapping

Peter, Comments below. Gary On Wednesday, 16 December 2020 at 23:18:26 UTC+10 Vetti52 wrote: > Thanks, Gary, for your polite explanations. > Since I have read some of your comments with equal advices in other > threads, I proceeded already to sucessfully map the fields. Otherwise I did > not

[weewx-user] Re: yet another question to GW1000 api driver mapping

As I could not wait for an answer, I tried to replace $x in the example mentioned above (marked in yellow) by any of the supposed expressions. But in any case I get this type of error: ERROR weewx.cheetahgenerator: Generate failed with exception '' ERROR weewx.cheetahgenerator: Ignoring te

[weewx-user] Re: yet another question to GW1000 api driver mapping

Thanks, Gary, for your polite explanations. Since I have read some of your comments with equal advices in other threads, I proceeded already to sucessfully map the fields. Otherwise I did not even had an idea about field_map in GW1000. Sorry, that you need to explain again and again the compari

[weewx-user] Re: yet another question to GW1000 api driver mapping

Some comments below. Hopefully it gives you a process to work through to identify your problem. Gary On Wednesday, 16 December 2020 at 06:37:40 UTC+10 Vetti52 wrote: > Well, I started this conversation already at another thread ( > https://groups.google.com/g/weewx-user/c/ua0JjTp1DW8/m/AFGZf7Ay