ESP8266/ESP32 + CC1101 - projekt "everblu-meters" 433MHz

Did you have aby problem with them?

They have not had any clue what is happening. They told that these meters fail regularly. I can just guess due to bad reception at their truck, most likely as the transmitted signal reaches the meter, but the reply does not reach the truck.

A guy from Slovenia reported the same issue on the HA forum. In his case they just replaced the module. In my case they replaced the whole meter and the module.

Meanwhile they were unable to read, I was still able to read it without any issue.

Did you use projekt pyskowiak

1 polubienie

Yes, I did. The initial one, then he added automatic discovery for MQTT and some other improvements.

Though I had to modify a bit as it was initially unable to read the meter.

And you dont use water meter?

Not anymore. Since the water company replaced it. I did not want to cause more trouble(and cost) for them…

But if I would be able to check their software for reading, I would try to disable the setting which cause the whole issue for them, but I am not an employee of the water company. They obviously don’t know how the software and hardware is working. As my experience, they cannot even care less about it. It just a convenience from them that they can drive around the city in a car, stop in front of each house which has a meter like this, and they don’t need to get out of the car anymore.

And I am really sorry, that I am writing in English, but I do not speak Polish. But please write me in Polish, I can use translation easily and it is better for me, because if something is wrong with the translation, I can ask my wife to translate it for me. And it is generally less trouble for you to get the English right. :+1:

You would change the 10 to 16, but it is UTC, so if you want now 16:00 Local Time, then you should set it to 14.

You need to remove the /* and */ to enable the frequency search code, as I quoted above. You need the ESP32 to be connected to a computer to see the serial log, where it would be printed.

Once you found the frequency, you need to update it in the everblu_meters.h:

// Change these define according to your hardware

#define FREQUENCY 433.8683f

#define GDO0 5 //header  11 

#define METER_YEAR              15
#define METER_SERIAL            886451

Don’t forget to update the YEAR and SERIAL number according the readme of the project, omit the leading 0 from the serial…

can you help me with rtl_433 ?
my config


# https://github.com/merbanan/rtl_433/blob/master/conf/rtl_433.example.conf

 #  output mqtt://${192.168.1.185}:${1883},user=${tasfdota},pass=${zonfd23},retain=${true}




output kv
output json
gain          0
frequency     868.45M
hop_interval  600
ppm_error     0
sample_rate   1000k
report_meta   time:tz
output mqtt://192.168.1.185:1883,user=tasfdta,pass=zofdfd3,retain=0,devices=rtl_433/AlectoV1
output json
protocol 16




## Protocols to enable (command line option "-R")

 protocol 1   # Silvercrest Remote Control
 protocol 2   # Rubicson, TFA 30.3197 or InFactory PT-310 Temperature Sensor
 protocol 3   # Prologue, FreeTec NC-7104, NC-7159-675 temperature sensor
 protocol 4   # Waveman Switch Transmitter
 protocol 6   # ELV EM 1000
# protocol 7   # ELV WS 2000
# protocol 8   # LaCrosse TX Temperature / Humidity Sensor
# protocol 10  # Acurite 896 Rain Gauge

and log
from addon rtl_433

[20:45:16] WARNING: rtl_433 now supports automatic configuration and multiple radios. The rtl_433_conf_file option is deprecated. See the documentation for migration instructions.
Starting rtl_433 -c /config//rtl_433/rtl_433.conf.template
rtl_433 version 23.11 branch  at 202311281352 inputs file rtl_tcp RTL-SDR

New defaults active, use "-Y classic -s 250k" if you need the old defaults

MQTT: Publishing MQTT data to 192.168.1.185 port 1883
MQTT: Publishing device info to MQTT topic "rtl_433/AlectoV1".
Found Fitipower FC0013 tuner
[SDR] Using device 0: Realtek, RTL2838UHIDIR, SN: 00000001, "Lifeview LV5TDeluxe"
Exact sample rate is: 1000000.026491 Hz
Allocating 15 zero-copy buffers

and i dont see anything in MQTT EXPLORER

What is your goal here?

Do you have an RTLSDR to confirm that the meter replies to the CC1101 when it transmits to it?

Just use the RTLSDR with SDR# and Airspy Downloads - AIRSPY

Or is it for a different topic?

Looking at your snippets

Are you working in the right conf file?

You should get a line in the log like this, if you configured correctly the protocol:

[Protocols] Registered 6 out of 243 device decoding protocols [ 1-4 5 16 ]

Personally I would also set the sample rate to 1024k.

Do you have an MQTT Connected... in your log as well?

hi i have this but i dont see it in MQTT explorer on windows

time      : 2024-05-10 22:15:59.812162             Protocol  : 172
model     : Bresser-6in1 id        : 21200803
channel   : 0            Battery   : 1             Temperature: 22.3 C       Humidity  : 64            Sensor type: 1            Wind Gust : 2.1 m/s       Wind Speed: 1.8 m/s       Direction : 248           UV        : 0.0           Startup   : 1             Flags     : 0             Integrity : CRC
Modulation: FSK          Freq1     : 868.3 MHz     Freq2     : 868.5 MHz
RSSI      : -7.1 dB      SNR       : 27.2 dB       Noise     : -34.4 dB
{"time" : "2024-05-10 22:15:59.812162", "protocol" : 172, "model" : "Bresser-6in1", "id" : 555747331, "channel" : 0, "battery_ok" : 1, "temperature_C" : 22.300, "humidity" : 64, "sensor_type" : 1, "wind_max_m_s" : 2.100, "wind_avg_m_s" : 1.800, "wind_dir_deg" : 248, "uv" : 0.000, "startup" : 1, "flags" : 0, "mic" : "CRC", "mod" : "FSK", "freq1" : 868.313, "freq2" : 868.465, "rssi" : -7.140, "snr" : 27.222, "noise" : -34.363}
{"time" : "2024-05-10 22:15:59.812162", "protocol" : 172, "model" : "Bresser-6in1", "id" : 555747331, "channel" : 0, "battery_ok" : 1, "temperature_C" : 22.300, "humidity" : 64, "sensor_type" : 1, "wind_max_m_s" : 2.100, "wind_avg_m_s" : 1.800, "wind_dir_deg" : 248, "uv" : 0.000, "startup" : 1, "flags" : 0, "mic" : "CRC", "mod" : "FSK", "freq1" : 868.313, "freq2" : 868.465, "rssi" : -7.140, "snr" : 27.222, "noise" : -34.363}
[Auto Level] Current noise level -42.1 dB, estimated noise -40.7 dB

Do you have an MQTT Connected... in your log as well?

2024-05-10 21:48:01: Client rtl_433-4801ffff6ace closed its connection.
2024-05-10 21:48:06: New connection from 172.30.32.1:34040 on port 1883.
2024-05-10 21:48:06: New client connected from 172.30.32.1:34040 as rtl_433-4801ffff6ace (p2, c0, k60, u'rtl').

I think you are not alone:

thx you they must repair it ?

Just try to reinstall the addon, maybe.

how other people repair it ?

Witaj jak kompiluje płytke mam takie znaki w serial monitor. odkomentowałem znaki.
serial monitor

!!�9�!%!!!!�9!��!!�!%!!�!!!�9��9�!%!��9��!!!!Qx�!!N!��9�!%!%!!!)!)!�o�Ȉy�9��)!)�9�!=!)�9�9�9��9��9��y�9��)�
m!��9��)�Htx4`,l$�:htll�4 :da�l���0Z���!�!=!�!�!)!)!�!)�Y!)!�!�!)!)!��dn��HHt�4 >��p�$$Rhl��4$Z��9�![!)!)�9�!�

Nie wiem, nie znam się, ale taka sieczka czasem się zdarza jak masz ustawioną nieprawidłową prędkość portu szeregowego.

Zmienię i zobaczymy co dalej

No chyba że podsłuchujesz port w trakcie przesyłania pliku binarnego.
Ale nie wczuwając się w sytuację zupełnie nie wiem co robisz.
A tak skąpe informacje nie naprowadzają w żadnym kierunku.