Domoticz

Recently installed a 5-in-1 PWS of type CCare DSX100 (= lookalike for Cresta/Bresser_DSX100).
For data-interface to outside world it applies Firmware ProWeatherlink.
That firmware by standard setup realises remote data-upload over WLAN and Internet to WUnderground and to WeatherCloud.
Under 'Advanced' a setup for a 3rd interface is available:
in another Bresser-manual found that this interface may be applied to upload to AWEKAS.
See page 15 of the file attached to this link.
Therefore this 3rd interface seems suitable to feed data to other organisations/applications.

Question: would it be possible to apply this 3rd interface to feed data from the PWS over the local WLAN to Domoticz? If, howto?
Argument: Reading back from WUnderground is a functional solution to get the data into Domoticz, but over long route => the direct path is better.

The device also transmits on the 868 Mhz frequency.
You could also try with a RFXCom 868 transceiver or RFLink
I have an 868 Mhz weather station looking similer and this I can receive with a RFXCom transceiver

But best to ask RFXCom if they support it

Have a look at the WSView Plus app (android) together with the Wunderground Direct Receiver hardware plugin. Domoticz reads the data from the indoor station via wifi.
More info is also on the WXforum.net https://www.wxforum.net/index.php

Much succes in connecting your weather station.

Indeed, reading the 868MHz-signals from the sensorhead is the most direct route.
Application of the functionality of the local WLAN-interface is next best:
1. 'interception' of messages to WUnderground is one way
2. if the mentioned 3rd interface could straightforwardly direct it's messages to a local Domoticz-instance, it would be better.

In both latter cases some software will be required to get the data and to translate it for Domoticz.
In case 2. it is first required to know the contents of the output file.
Obviously that knowledge might be emperically deducted by setup the 3rd interface for messages towards AWEKAS and then intercepting those messages,
but perhaps somebody already has experience ....

Might also 'turnaround' the question related to case 2. for a setup wnich catches an 'unknown' file directed to a receiver-script:
- aim the url of the 3rd interface towards the processor having the receiver-script
- the receiver-script stores the catched file for later review&dissection.
Looks similar to WireShark, but much simpler, because destination is controlled in advance and the receiver is ready-to-go.
Some developer with practical info for such setup?
Might have some general value for comparable situations in which 'trigger & aim' seems available, but outcome unknown.