Now I have one more Question.
On the sender Site I have this Config now:
[[MQTT]]
server_url = xxxxx
topic = weather
unit_system = METRIC
binding = loop, archive
aggregation = aggregate
append_units_label = false
So I sent loop and archive.
Both will sent as "loop".
In this case the receiver show the same Data, with the same Time.
If I have the binding only "archive" the receiver is 5 Minutes back.
Which is the right config for me?
Regards
Christian
Christian Radermacher schrieb am Freitag, 5. März 2021 um 17:54:34 UTC+1:
>
> Now everything is working fine, I have no idea, why the Skin would not
> generate.
> I will play around, an come back with other questions, if necessary.
>
> Thanks to all, helped me
>
> Regards
> Christian
> Christian Radermacher schrieb am Freitag, 5. März 2021 um 17:40:19 UTC+1:
>
>> Hi Rich,
>>
>> thanks for the reply. Now I can see that it is working, but my Skin would
>> not be generated. So I search another error.
>>
>> Regards
>> Christian
>>
>> [email protected] schrieb am Freitag, 5. März 2021 um 16:18:42 UTC+1:
>>
>>> Thinking more, I am pretty sure the alpha code won’t work for you.
>>> - rich
>>>
>>> On Friday, 5 March 2021 at 09:58:38 UTC-5 [email protected] wrote:
>>>
>>>> Christian,
>>>> I’d recommend adding ‘append_units_label = False’ on the publish side.
>>>> This will stop the appending of units to the label and you won’t have to
>>>> rename them on the subscribing side.
>>>>
>>>> I’d expect the subscribing config to look something like this.
>>>>
>>>> [MQTTSubscribeDriver]
>>>> driver = user.MQTTSubscribe
>>>>
>>>> host =
>>>>
>>>> [[message_callback]]
>>>> type = json
>>>>
>>>> [[topics]]
>>>> unit_system = METRIC
>>>> [[[weather/loop]]]
>>>>
>>>> If you post the log from startup through one archive period, I could
>>>> dig deeper.
>>>>
>>>> Important note, with the set up above, I believe you are publishing
>>>> archive records. These are received and put into loop packets by
>>>> MQTTSubscribe. WeeWX would then create archive records out of them. I
>>>> think
>>>> this should all work, but there might be some timing issues. The log would
>>>> show what is going on.
>>>> I do have alpha/experimental code that would receive the MQTT payload
>>>> and process it as an archive record. It would very much be “use at your
>>>> own
>>>> risk”.
>>>> - rich
>>>>
>>>> On Friday, 5 March 2021 at 09:05:50 UTC-5 [email protected]
>>>> wrote:
>>>>
>>>>> ok, i installed the receiver Weewx new from scratch. No it seems to
>>>>> work without errors.
>>>>> I See in the (debugLevel 2) the incoming MQTTValues. But they don't
>>>>> where displayed in the screen. It seems, there is one point missing.
>>>>>
>>>>> Regards
>>>>> Christian
>>>>>
>>>>> [email protected] schrieb am Freitag, 5. März 2021 um 14:32:15 UTC+1:
>>>>>
>>>>>> a driver creates the original packet with a timestamp, a service
>>>>>> changes (usually adds to) the existing packet.
>>>>>> some modules, like gw1000, can be configured to be in either mode
>>>>>> (i.e. originate packets, or augment existing packets produced by some
>>>>>> other
>>>>>> driver). i do this, with vantage as driver and gw1000 in service mode
>>>>>>
>>>>>> On 5 Mar 2021, at 10:59 pm, Christian Radermacher <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>> In which case I user Service, in which case I use driver?
>>>>>>
>>>>>>
>>>>>>
--
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/20f378b8-8b46-4bb5-bd68-29a52a2edb02n%40googlegroups.com.
