yes i am using the 1 wire as a service
many years when i modified the schema i created 20 extraTemps so i will use
my extraTemp10 to extraTemp 20
thanks for your help apprecaite it
On Thursday, May 4, 2023 at 11:27:02 AM UTC+1 gjr80 wrote:
> Short answer is no it will not overwrite existing loop packet data.
>
> But there may be a bit more to it in your case. If you have a Davis
> Vantage and a 1 wire system I assume you are running the vantage driver
> with a separate service to augment the vantage produced loop packet with 1
> wire data. If you then use the Ecowitt gateway driver as a service the
> overall result may depend on the order the 1 wire and Ecowitt gateway
> driver service appear in the service list. If the Ecowitt service is first
> then the Ecowitt service will only be augmenting the vantage loop packet
> (again not overwriting any existing loop packet data). What the 1 wire
> service then does with the 1 wire data and the Ecowitt augmented loop
> packet depends on the 1 wire service. If the services are in the other
> order then any 1 wire data will always be preserved.
>
> If you do have a conflict in field names, and you want to preserve the
> Ecowitt data, then all you need do is alter the field map used by the
> Ecowitt service. The easiest way to do this is with a
> [[field_map_extensions]] stanza, eg:
>
> [GW1000]
> ....
> [[field_map_extensions]]
> extraTemp20 = temp6
>
> extraTemp20 would need to be added to your database schema if you wish to
> save the data to database, alternatively you could re-use an existing
> unused database field.
>
> Gary
>
> On Thursday, 4 May 2023 at 19:19:54 UTC+10 vigilance wx wrote:
>
>> I would like to install the GW1000 extension as a service
>>
>>
>>
>> I have a Davis vantage and 6 extraTemp sensors connected to a 1 wire
>> system
>>
>> I am unsure regarding the explanation if it will over write my 1 wire
>> system or not
>>
>> looking in the gw1000.py I see
>>
>> # Default field map to map device sensor data to WeeWX fields. Field
>> names
>>
>> # in the WeeWX wview_extended schema are used where there is a direct
>>
>> # correlation to the WeeWX wview_extended schema or
>>
>> # weewx.units.obs_group_dict. If there is a related but different
>> field in
>>
>> # the wview_extended schema then a WeeWX field name with a similar
>> format
>>
>> # is used. Otherwise fields are passed through as is.
>>
>> # Field map format is:
>>
>> # WeeWX field name: Gateway device field name
>>
>> default_field_map = {
>>
>> 'inTemp': 'intemp',
>>
>> 'outTemp': 'outtemp',
>>
>> 'dewpoint': 'dewpoint',
>>
>> 'windchill': 'windchill',
>>
>> 'heatindex': 'heatindex',
>>
>> 'inHumidity': 'inhumid',
>>
>> 'outHumidity': 'outhumid',
>>
>> 'pressure': 'absbarometer',
>>
>> 'relbarometer': 'relbarometer',
>>
>> 'luminosity': 'light',
>>
>> # we can't pass through 'uv'; it's too much like 'UV', so use the
>>
>> # Ecowitt term 'uvradiation'
>>
>> 'uvradiation': 'uv',
>>
>> 'UV': 'uvi',
>>
>> 'dateTime': 'datetime',
>>
>> 'extraTemp1': 'temp1',
>>
>> 'extraTemp2': 'temp2',
>>
>> 'extraTemp3': 'temp3',
>>
>> 'extraTemp4': 'temp4',
>>
>> 'extraTemp5': 'temp5',
>>
>> 'extraTemp6': 'temp6',
>>
>>
>> thanks for an help
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/b83ac5e0-2f48-4646-bc11-26a34fd6f74an%40googlegroups.com.
