Rain gauge protocol

so-what

Hi,

I have this rain gauge but it seems there is no protocol for it yet. Is someone willing to write a protocol for this device? It would be much appreciated. Some debug lines:

16:58:28.987 [pimatic-homeduino] debug: data: "RF receive 436 2124 3840 8088 0 0 0 0 0101010101010101010101010101010102010202010201010101010101010101020202020203"
16:58:29.000 [pimatic-homeduino] debug: received: [ 436, 2124, 3840, 8088 ] 0101010101010101010101010101010102010202010201010101010101010101020202020203
18,0

17:15:43.735 [pimatic-homeduino] debug: data: "RF receive 432 2132 3856 8108 0 0 0 0 0101010101010101010101010101010102010202010102020101010101010101020101010203"
17:15:43.748 [pimatic-homeduino] debug: received: [ 432, 2132, 3856, 8108 ] 0101010101010101010101010101010102010202010102020101010101010101020101010203
17,9

19:35:58.878 [pimatic-homeduino] debug: data: "RF receive 432 2128 3848 8104 0 0 0 0 0101010101010101010101010101010102010201010201010101010101010101020202010203"
19:35:58.896 [pimatic-homeduino] debug: received: [ 432, 2128, 3848, 8104 ] 0101010101010101010101010101010102010201010201010101010101010101020202010203
16.4

19:47:14.061 [pimatic-homeduino] debug: data: "RF receive 432 2128 3856 8092 0 0 0 0 0101010101010101010101010101010102010201010101020101010101010101020102020203"
19:47:14.075 [pimatic-homeduino] debug: received: [ 432, 2128, 3856, 8092 ] 0101010101010101010101010101010102010201010101020101010101010101020102020203
16,1

14:25:35.142 [pimatic-homeduino] debug: data: "RF receive 440 2124 3836 8096 0 0 0 0 0101010101010101010101010101010102010101020101010201010201020201020202020203"
14:25:35.155 [pimatic-homeduino] debug: received: [ 440, 2124, 3836, 8096 ] 0101010101010101010101010101010102010101020101010201010201020201020202020203
13,6 /3mm

14:27:50.122 [pimatic-homeduino] debug: data: "RF receive 440 2124 3840 8096 0 0 0 0 0101010101010101010101010101010102010101020101010201010201020201020202020203"
14:27:50.135 [pimatic-homeduino] debug: received: [ 440, 2124, 3840, 8096 ] 0101010101010101010101010101010102010101020101010201010201020201020202020203
13,6 /6mm

14:29:20.124 [pimatic-homeduino] debug: data: "RF receive 440 2124 3840 8088 0 0 0 0 0101010101010101010101010101010102010101020101010102010102010202020202020203"
14:29:20.137 [pimatic-homeduino] debug: received: [ 440, 2124, 3840, 8088 ] 0101010101010101010101010101010102010101020101010102010102010202020202020203
13,6 /7,5mm

first 3 lines are temperature with 0mm rain, last 3 lines is with heavy rainfall

mwittig

@so-what The encoding seems to be fairly easy.

The pulse to binary mapping:
01 --> 0
02 --> 1

Decode for the first sample, and the last two samples with heavy rain. Note, the y value on the second sequence differs from your reading (6mm).

0000 0000 0000 0000 1011 0100 0000 0000 1111 1 03
                    xxxx xxxx yyyy yyyy
					
					x: 180 / 10 = 18,0
					y: 0
					
0000 0000 0000 0000 1000 1000 1001 0110 1111 1 03
0000 0000 0000 0000 1000 1000 1001 0110 1111 1 03
                    xxxx xxxx yyyy yyyy
					
					x: 136 / 10 = 13,6
					y: 150 /10 = 15

0000 0000 0000 0000 1000 1000 0100 1011 1111 1 03					
                    xxxx xxxx yyyy yyyy
					
					x: 136 / 10 = 13,6
					y: 75 /10 = 7,5

Can you please

create some more heavy rain examples?
explain the use second value? I couldn’t find this on the data sheet
resync the rainsensor with the weather station and post the resulting log messages, once the sensor has been synced with weather station? I am wondering whether or not the first two octets will have a different value

EDIT: Does heavy rain means it is measurement of rain intensity? See also https://en.wikipedia.org/wiki/Rain_gauge#Pluviometer_of_intensities

so-what

hi @mwittig

tnx for helping.

It is measurement of how much rain is falling in mm. The values are in mm per 24 hrs, the per 1 hr value is always giving 0mm, this cant be right.
Here are some new logs(i moved it to my desk, so temp is rising)

17:42:50.306 [pimatic-homeduino] debug: data: "RF receive 440 2120 3844 8092 0 0 0 0 0101010101010101010101010101010102020101010102010101010101010101020202010203"
17:42:50.319 [pimatic-homeduino] debug: received: [ 440, 2120, 3844, 8092 ] 0101010101010101010101010101010102020101010102010101010101010101020202010203
19.4 degrees /0 mm

17:44:20.322 [pimatic-homeduino] debug: data: "RF receive 440 2120 3832 8096 0 0 0 0 0101010101010101010101010101010102020101010201010102010102010202010202020103"
17:44:20.335 [pimatic-homeduino] debug: received: [ 440, 2120, 3832, 8096 ] 0101010101010101010101010101010102020101010201010102010102010202010202020103
19.6 degrees /1.5mm per 24hrs

17:46:35.843 [pimatic-homeduino] debug: data: "RF receive 440 2120 3828 8092 0 0 0 0 0101010101010101010101010101010102020101020101010202020202010201010101020103"
17:46:35.855 [pimatic-homeduino] debug: received: [ 440, 2120, 3828, 8092 ] 0101010101010101010101010101010102020101020101010202020202010201010101020103
20.0 degrees /6.5mm per 24hrs

17:51:05.827 [pimatic-homeduino] debug: data: "RF receive 440 2124 3832 8100 0 0 0 0 0101010101010101010101010101010102020101020201020101010101010101010101020103"
17:51:05.840 [pimatic-homeduino] debug: received: [ 440, 2124, 3832, 8100 ] 0101010101010101010101010101010102020101020201020101010101010101010101020103
20.5 degrees /6.5mm per 24hrs

17:56:20.827 [pimatic-homeduino] debug: data: "RF receive 440 2120 3840 8096 0 0 0 0 0101010101010101010101010101010102020102010101010202010102010101020101020203"
17:56:20.840 [pimatic-homeduino] debug: received: [ 440, 2120, 3840, 8096 ] 0101010101010101010101010101010102020102010101010202010102010101020101020203
20.8 degrees /10.5mm per 24hrs

18:03:50.838 [pimatic-homeduino] debug: data: "RF receive 444 2120 3828 8092 0 0 0 0 0101010101010101010101010101010102020102010102020101010202010102010202010103"
18:03:50.851 [pimatic-homeduino] debug: received: [ 444, 2120, 3828, 8092 ] 0101010101010101010101010101010102020102010102020101010202010102010202010103
21.1 degrees /11 mm per 24hrs

After sync:
18:09:50.838 [pimatic-homeduino] debug: data: "RF receive 440 2120 3840 8092 0 0 0 0 0101010101010101010101010101010102020102010202020101010101010101020102010203"
18:09:50.852 [pimatic-homeduino] debug: received: [ 440, 2120, 3840, 8092 ] 0101010101010101010101010101010102020102010202020101010101010101020102010203

And for the not known value, can it be battery status? With 1 empty battery it says:
18:49:22.567 [pimatic-homeduino] debug: data: "RF receive 440 2124 3828 8092 0 0 0 0 0101010101010102010101010101010102020102020201020101010101010101010101020103"
18:49:22.580 [pimatic-homeduino] debug: received: [ 440, 2124, 3828, 8092 ] 0101010101010102010101010101010102020102020201020101010101010101010101020103

BTW, how do i get those results in the nice coding area like you do?

PS i see it didnt change with a empty battery

mwittig

Ah, ok. I didn’t notice the first value is a temperature reading.

@so-what said:

BTW, how do i get those results in the nice coding area like you do?
You can use three back-ticks to start and end a codeblock as shown in the following example. However, do not not indent the backticks. For inline code you can use single backticks.

    ```
    My code
    ```

PS i see it didnt change with a empty battery
Does the weather-station shows a battery symbol for sensor? I couldn’t find this on the datasheet and resolution of the lcd picture is too low. However, one bit changed which might be the battery indicator.

battery empty
0000 0001 0000 0000 1101 1101 0000 0000 0001 0 03

I have also found this FHEM post which contains some interesting information. However, the code snippet have never been integrated with FHEM and may not be correct. I am posting an excerpt here for reference, only.

  #                /--------------------------- Channel, changes after every battery change 0-3     
  #               /     /----------------------- Tendenz 1 = steigend      
  #              /     //----------------------- Batterie 0 = ok      
  #             /     //     /------------------ Vorzeichen (Temp - 2048)         
  #            /     //     /            
  #           /     //     /  /----------------- Temp z.B. 236 = 0011101100 hex             
  #          /     //     /  /             / ---- Regenmenge 50 = 000110010 hex
  #         /     //     /  /             /  
  #        00111010000000.00.1111.0000.000000000.1100  24,0 C
  #        00111010000000.00.1110.1100.000110010.0110  23,6 C    +0,5mm (9,5mm))
  #        00111001000000.00.1111.0110.000000000.011
  #        00111110000000.01.0000.1001.000000000.101
  #        00111110000000.01.0000.1001.101011110.000
  #        00111110000000.00.1111.0011.000000000.001 24,3 C  fallend
  #        00111110000000.00.1111.0010.000000000.000 24,2 C  fallend
  #        00111110000000.00.1111.0001.000000000.011 24,1 C fallend
  #        00111110000000.00.1111.0010.000000000.000
  #        00111110000000.00.1111.0001.000000000.011
  #        00111100000000.00.1111.1011.000000001.011
  #        00111100000000.00.1111.0111.000000000.111 
  #        00111100000000.00.1111.1010.000000001.010
  #        00111100000000.00.1111.0101.000000000.101
  #        00111100000000 00 1111 0100 000000000 100  24,4 C fallend
  #        00111100000000 00 1111 0010 000000000 010  24,2 C gleichbleibend
  #        00111001000000 00 1111 0001 000000000 100  24,1 C gleichbleibend  Batterie critisch
  #        00111110010000 00 1111 1000 000000001 110
  #        00111110000000 00 1111 0111 000000000 101  24,7 C 
  #        00111110000100 00 1111 0001 001011001 100
  #        00111110000000 01 0000 0000 000110010 100  25,6 C steigend
  #        00111110000000 01 0000 0011 000000001 111  25,9 C steigend
  #        00111110000000 00 1111 1110 001100101 101
  #        00111110000011.11.1011.1010.000000000 011
  #        00111110000011 11 1010 0000 000000001 000  -7,2 C

I still have concerns about the rain sensor readings as they differ a lot from your base station readings. I don’t think these values are presenting the results but they’re raw data from the sensor may be rocker strokes (Wippenschläge)?! http://forum.fhem.de/index.php?topic=38831.150 is suggesting that a rocker stroke is decimal 28 which equals to 0.5 mm rain fall in agiven time interval. Well, I think it is more likely a rocker stroke is 25.

@Developer Who has some expertise with rain sensors?

so-what

@mwittig I did a new check for the battery symbol and after trying a few batteries i get a 1/2 full battery symbol. So yes, there is a battery indicator on the base.

About the rocker stroke. I made a new log and the base reading tells me 1 stroke (from left to right) is 0.5mm, back again is 1mm. I left out the temperature reading at the base in this log.

0x
17:35:53.862 [pimatic-homeduino] debug: data: "RF receive 440 2120 3836 8096 0 0 0 0 0101010102020202010101010101010102020102020202010101010101010101020201010203"
17:35:53.876 [pimatic-homeduino] debug: received: [ 440, 2120, 3836, 8096 ] 0101010102020202010101010101010102020102020202010101010101010101020201010203
0 mm

1x (lever from left to right)
17:38:08.849 [pimatic-homeduino] debug: data: "RF receive 440 2124 3828 8100 0 0 0 0 0101010102020202010101010101010102020102020202010101010202010102010201010103"
17:38:08.863 [pimatic-homeduino] debug: received: [ 440, 2124, 3828, 8100 ] 0101010102020202010101010101010102020102020202010101010202010102010201010103
0.5mm

2x (back to start position)
17:40:23.881 [pimatic-homeduino] debug: data: "RF receive 444 2124 3828 8096 0 0 0 0 0101010102020202010101010101010102020102020202020101010202010102010201020103"
17:40:23.903 [pimatic-homeduino] debug: received: [ 444, 2124, 3828, 8096 ] 0101010102020202010101010101010102020102020202020101010202010102010201020103
1.0mm

3x
17:42:38.863 [pimatic-homeduino] debug: data: "RF receive 444 2120 3828 8096 0 0 0 0 0101010102020202010101010101010102020102020202020101010202010102010201020103"
17:42:38.882 [pimatic-homeduino] debug: received: [ 444, 2120, 3828, 8096 ] 0101010102020202010101010101010102020102020202020101010202010102010201020103
1.5mm

I hope this helps

so-what

Hi, i did some new readings to confirm the value of 1 rocker stroke. Like @mwittig was thinking 1 rocker stroke gives a value of 25, value at the base 0,5mm.

0101010102020202010101010101010102020101020202010101010101010101020201020203 123725
0000 1111 0000 0000 1100 1110 0000 0000 1101 1 03
                    20,6      0         

0101010102020202010101010101010102020101020202010101010202010102010201020103 123810
0000 1111 0000 0000 1100 1110 0001 1001 0101 0 03
                    20,6      25        

0101010102020202010101010101010102020101020202010101010101010101020201020203 123855
0000 1111 0000 0000 1100 1110 0000 0000 1101 1 03
                    20,6      0

2 rocker strokers in 1 broadcast

0101010102020202010101010101010102020102010201010101010101010101010202010103 141455
0000 1111 0000 0000 1101 0100 0000 0000 0110 0 03
                    21,2      0

0101010102020202010101010101010102020102010201020101020201010201010202010103 141540
0000 1111 0000 0000 1101 0101 0011 0010 01100 03
                    21,3      50

0101010102020202010101010101010102020102010201020101010101010101010202020103 141625
0000 1111 0000 0000 1101 0101 0000 0000 0111 0 03                             
                    21,3      0

So pushing the lever 3x between 2 broadcasts gives a value of 75

0101010102020202010101010101010102020102010102020102010102010202020202010203 133725
0000 1111 0000 0000 1101 0011 0100 1011 1110 1 03
                    21,1      75

the last 6 numbers is the time

Is it possible to write a protocol for this device with this information?

mwittig

@so-what said:

Is it possible to write a protocol for this device with this information?

I think so, but I’ll not be able to do it with the next two weeks as I’ll be travelling.
May be some other @Developer would like to take the initiative?