Hi,
Here is a blast from the past, in summary, I invested in the TFA
equipment in 2017 but it has taken me this long (dont ask!) to attempt
to implement connectivity via weewx . To be fair, the mobile phone app
has given me all I needed up till now, but between redundancy and covid
I now find time to look at something better.
I installed weewx and the interceptor extension, configured the
interceptor with the lacrosse driver and the weatherhub to use the weewx
box (LXC container actually) as a proxy.
I started receiving packets in the interceptor and in the logs, I get
this for example:
Sep 20 15:02:50 burdock weewx[4965] DEBUG user.interceptor: empty
queue Sep 20 15:03:00 burdock weewx[4965] DEBUG user.interceptor:
empty queue Sep 20 15:03:10 burdock weewx[4965] INFO
user.interceptor: unknown format for HTTP_IDENTIFY:
'800F1450:001D8C0F1450:C0' Sep 20 15:03:10 burdock weewx[4965] DEBUG
user.interceptor: send: 00:00 Sep 20 15:03:10 burdock weewx[4965]
DEBUG user.interceptor: empty queue
I captured the packets emitted by the weatherhub and received by the
weewx box, they are destined for www.data199.com, so clearly the
lacrosse driver as it stands isnt going to work for me since the
upstream destination is www.data199.com rather then
box.weatherdirect.com. Here was a typical transaction captured with the
weatherhub returned to direct access, the HTTP_IDENTIFY apparently sent
in clear text, but I have obfuscated it anyway..
PUT http://www.data199.com/gateway/put HTTP/1.1
Host: www.data199.com
Connection: close
HTTP_IDENTIFY: XXXXXXXX:XXXXXXXXXXXX:XX
Content-Type: application/octet-stream
Content-Length: 64
HTTP/1.1 200 OK
Server: BaseHTTP/0.6 Python/3.7.3
Date: Sun, 20 Sep 2020 15:03:10 GMT
HTTP_FLAGS: 00:00
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
X-ApsNet-Version: 2.0.50727
Cache-Control: private
Content-Length: 0
Content-Type: application/octet-stream
Date: Sun, 20 Sep 2020 15:03:10 GMT
Connection: close
So, I am guessing the lacrosse driver never attempted to make use of the
payload (I have 8 sensors connected to this weatherhub) but I am
doubting the format is compatible even if I can sort out the
authentication. It may be a step too far to get this working - unless
anyone can guide me through the further analysis of these packets.
Thanks
--
Andy
On 14/12/2017 04:34, mwall wrote:
hi andy,
welcome to weewx!
TFA uses the same hardware as many other vendors. For example:
TFA matrix = lacrosse ws23xx
TFA primus = lacrosse ws28xx
TFA nexus = hideki te923
the klimalogg and klimalogg pro use the same sensors, but i think the
klimalog pro has a computer interface whereas the klimalogg does not.
the klimalogg pro console communicates with a computer via a usb RF
receiver.
the klimalogg pro transceiver uses almost the same protocol as the
transceiver for the lacross ws28xx weather stations.
the TFA weatherhub looks a lot like the lacross gw1000u, and the
sensors that go with it look identical to the lacrosse sensors. i see
"mobile alerts" on the TFA gateway device:
http://wettershop.de/31-4003-02-weatherhub-mit-regenmesser-fuer-smartphones-ios-oder-android-starter-set-3.html
lacrosse has a "mobile alerts" service too:
http://www.lacrossealertsmobile.com/
so to answer your question: if the tfa weatherhub is the same as the
lacrosse gw1000u, and if they use the same protocol, then you can use
the weewx-interceptor driver to capture data from it.
m
--
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/4mDDP_xuzC4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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/a8f01903-080d-1a6e-edb8-4c030c3cee79%40gmail.com.
