Replies: 1 comment 1 reply
-
CRC checks out to the usual poly 0x31 init 0x00. Re ID/type: is the ID printed somewhere or could the first nibble/byte be just a type code really? We see that on other protocols. edit: just noted the "ID: 3 bytes (matches bar code underside of unit covering pgm port)" comment in BreezePro. The first bits could be a type code still. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
tldr: I'm thinking of trying to add a unified La Crosse View device, based on the sensor ID to distinguish.
I've got a bunch of LTV-WL1 sensors, so am about to write some code based on the other La Crosse View devices — seems there are four so far (Breeze Pro, R1, TH3, WR1).
I'm pretty sure they all actually are the same protocol. For example, the WiFi-connected stations happily receive from any of the sensors & forward to their cloud service, even if they can't display the sensor data locally. https://www.lacrossetechnology.com/pages/view-sensor-compatibility-us for example has a list; almost without exception everything has the
*
meaning it can pass through to the cloud.-X n=LCV,m=FSK_PCM,s=104,l=104,r=9600,preamble={24}aa2dd4
seems to collect all of them (at least the W1, TH2, TH3, and WL1.)Right now it looks like all the different devices distinguish mainly by packet length. But... even from the same sensor, that's variable. Bitbench WL1, after preamble
Here is some with the pre-amble, including testing adding water to one, which changes the wetdry field from 0f0 to f0f. I also confirmed it uses the same (raw-400)/10 formula: Bitbench with preamble
[Note that still had the on startup bit in the format, but I confirmed when replacing the battery that the WL1 sensor didn't set that. Also, I haven't done the CRC math yet to make sure it's actually a CRC.]
So, err, I sort of think the only way to tell the sensors apart is by the device ID. I notice all my sensors of the same type start with the same hex digit... I have a bunch of TH2, they all start with 3 (from 3207d9 through 37c6e6); the WL1 sensors all start 50 (504936 through 50b9de). I've actually got more of those on order, so probably that will be a higher ID.
(The WL1 appears to use the same packet format as TH2, just with different meanings for the 2 12-bit fields. And oddly they didn't put the temperature in the same spot.)
Beta Was this translation helpful? Give feedback.
All reactions