LaCrosse Breeze Pro LTV-WSDTH01 supported

[john spanitz]

I read through all the supported devices on GitHub but am unsure if this device has been tested and is currently supported. Can anyone point me in the right direction or confirm working?

https://www.lacrossetechnology.com/products/ltv-wsdth01

[John D. Peterson]

Hello John Spanitz,
Others can add more details about what you need to do to help support a new device but to start with, following the instructions

here will get you started towards providing the information needed to add support for a new device:

https://github.com/merbanan/rtl_433/blob/master/docs/CONTRIBUTING.md  

Also, see threads like this one on steps to provide useful data to add future support:
https://groups.google.com/forum/#!topic/rtl_433/0xGnm2J5Rcs  

As I mentioned, I also have this device and will hopefully be able to supply data as well. The documentation shows these devices work in the 915MHz ISM band. Have you found the frequency that yours is working at yet? I will need to bring mine in the house and monitor chunks of bandwidth with something like SDR# to try and find it if you haven't already.

--
John D. Peterson/w4jdp
http://www.alabamarailfan.com

On Fri, Jul 24, 2020 at 1:17 PM John D. Peterson <jo...@alabamarailfan.com> wrote:

Hello All,

Probably redundant as I assume the OP has one, but I have this sensor also and am happy to provide any pictures, FCC data, logged information, etc to assist the cause. I had planned on doing this when I first got the unit but life has been busy with other projects! :)

Thank you for everyone's contributions to make a great application!

-- 

John D. Peterson/W4JDP

http://www.alabamarailfan.com

On Fri, Jul 24, 2020, 7:59 AM john spanitz <jo...@tyadca.com> wrote:

I read through all the supported devices on GitHub but am unsure if this device has been tested and is currently supported.  Can anyone point me in the right direction or confirm working?

https://www.lacrossetechnology.com/products/ltv-wsdth01

--
You received this message because you are subscribed to the Google Groups "rtl_433" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtl_433+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rtl_433/77800d65-02f7-453e-b2dd-251fe90aebb6o%40googlegroups.com.

[Michael Bruski]

I captured four nice sample files today from my LTV sensor using the following incantation:

osmocom_fft -a rtl -v -f 914.959357M -s 2.4e6 -g 20    (use -c to add ppm correction if you need it).

I know next to nothing about digital signals but this looks like FSK to me when I opened the samples in inspectrum.  Not sure if this will prohibit inclusion in the rtl_433 device list

or not (saw mention some where that rtl_433 can't handle FSK signals?).   If that is the case, we might need a new program to deal with it.  Analysis with rtl_433 seems to suggest this

is a FSK-PCM signal.

Looking at the FCC filings for the LTV (915MHz transmitter) and the TX145wsdth (433.92MHz transmitter), both appear to use the same circuit boards.  The only visible difference is the LTV antenna is shorter and has a 26MHz crystal/oscillator on board while the TX145 has a 13.553MHz crystal onboard.   The source file for the TX141 device (which includes TX145wsdth and others) shows the packet structure is PRE 5b, BAT 1b, TEST(?) 1b, CH(?) 2h, TYPE 4h, TEMP_WIND 12d, HUM_DIR 12d, CHK 8h, 1x.  In type 1 packets, WIND-SPEED and WIND-DIRECTION are sent.  In type 2 packets, TEMPERATURE and HUMIDITY are sent.  I wouldn't be surprised if the structure is the same for the LTV.

Mike/AJ9X

[Michael Bruski]

Somebody want to write the device driver for this guy?  I can put up a few of the sample files I used to bust the protocol.  For now, here is what I have discovered.

I did not work on the 8 bit flags or the CRC check.  Maybe someone can take that on when I get the samples put up.  Might take a while until I figure out how to post those files.

Note that the boards for this sensor and the LaCrosse TX145wsdth are pretty much identical, the MCU programming must be different.  The TX145 sends temp/hum in one

type of message and wind speed/direction in another message type.   The Breeze Pro sends all data in one message, and, it does not repeat.

LaCrosse Breeze Pro LTV-WSDTH01 sensor

(https://www.lacrossetechnology.com/products/ltv-wsdth01)

sensor uses HopeRF CMT2119A ISM transmitter
console (79400) uses HopeRF CMT2219A ISM receiver

bit length 106.842us
message length 28.46ms (fixed, includes sync, preamble, postamble and end gap)
modulation FSK/PCM
center frequency 914.938MHz

Protocol details

sync       (7 bytes - 0x55)
preamble   (5 bytes - 0x5A 0x55 0x45 0xBA 0x81)
device ID  (19 bits - changes when battery is replaced)
flags??    (8 bits - unknown, possibly battery status?, solar charge?, message type?, test?, flags?, channel?)
temp °C    (12 bits, offset 400, scale 10, range: -29°C to 60°C per device specifications)
humidity   (12 bits, range: 10 to 99% relative per device specifications)
wind speed (12 bits, range: 0 to 178 kMh per device specifications)
wind dir   (12 bits, range: 0 to 359° per device specifications)
checksum   (8 bits, ???)
postamble  (4 bytes - 0x00 0xD2 0xD2 0xD2)
end gap    (55 bits - all zeros

Mike/AJ9X

[Michael Bruski]

Hi all,

I'm new to using github so could use some help.  I submitted some sample files and doc files a few days ago for this device to rtl_433_tests.  This morning I completed a device decoder for it and it tests out beautifully.  The only thing missing is a CRC check - I don't know how to reverse engineer that.  I also have 3 bits undefined and can't stimulate the device to trigger any changes to them.   But, I can decode the important sensor values;  temp, humidity, wind speed, wind direction and device id.   Should I put the decoder in rtl_433 or rtl_433_tests?

Some of the protocol info in my last message is incorrect.  The preamble is 0x695516ea05 (inspectrum was showing 2 extra sync bits that the flex decoder appears to miss - threw me for awhile).   Postamble changes as a result also and should be 3 bytes (0x696969).  I broke out the flags (total of 6 bits, not 8, my bad) to be 2 bits (each unknown function), 3 bit sequence number, and 1 more bit (again, unknown function) followed by temp/hum/speed/direction.

Mike/AJ9X

[Benjamin Larsson]

On 03/09/2020 21:38, Michael Bruski wrote:
> Hi all,
>
> I'm new to using github so could use some help.  I submitted some sample
> files and doc files a few days ago for this device to rtl_433_tests.
> This morning I completed a device decoder for it and it tests out
> beautifully.  The only thing missing is a CRC check - I don't know how
> to reverse engineer that.  I also have 3 bits undefined and can't
> stimulate the device to trigger any changes to them.   But, I can decode
> the important sensor values;  temp, humidity, wind speed, wind direction
> and device id.   Should I put the decoder in rtl_433 or rtl_433_tests?
>
> Some of the protocol info in my last message is incorrect.  The preamble
> is 0x695516ea05 (inspectrum was showing 2 extra sync bits that the flex
> decoder appears to miss - threw me for awhile).   Postamble changes as a
> result also and should be 3 bytes (0x696969).  I broke out the flags
> (total of 6 bits, not 8, my bad) to be 2 bits (each unknown function), 3
> bit sequence number, and 1 more bit (again, unknown function) followed
> by temp/hum/speed/direction.
>
> Mike/AJ9X

Regarding the CRC if you provide lots of messages (>10k?) we can
probably figure it out.

The decoder is best sent as a PR to rtl_433. If you have issues with git
and github then attach it to an issue and we'll eventually help out
merging the code.

MvH
Benjamin Larsson

[Michael Bruski]

Thank you sir!   I uploaded the file and created a pull request.

Mike/AJ9X

[Gary Sinclair]

Are you having any issues with it?  Mine is sending

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

time      : 2021-05-09 21:04:49

model     : LaCrosse-BreezePro                     Sensor ID : 0b76ed

Sequence  : 3            unknown   : 0             Temperature: 56.7 F       Humidity  : 63 %          Wind speed: 4.9 mi/h      Wind direction: 95        Integrity : CRC

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

time      : 2021-05-09 21:04:49

model     : LaCrosse-TH3 Sensor ID : 0b76ed

Sequence  : 3            unknown   : 0             Temperature: 56.7 F       Humidity  : 63 %          Integrity : CRC

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

I'm guessing that the mqtt topic is getting overwritten before I can see the change so Im only getting the contents of the second message.