As long as the serial monitor does not show a result for your meter means the frequency is not identified.
When the test identifies a frequency you will see the data from your meter in the serial monitor. Then you can update everblue_meters.h file with the recognized frequency. Please also double check the wires from your D1 in order to make sure that they are correct wired.
I flashed another wemos d1 and solded the wires to the board. The wiring for the WemosD1 was according to the instructions in the repository and the cc1101 according this:
.
And now the logs show this:
I really dont know what else i can do
I have the same concern as you.
Initially I had made the configuration with an RPI3B + CC1101, the information went up correctly in HA.
I decided to switch to an ESP32 while keeping my CC1101.
So Iām on an ESP32-WROOM-32 + CC1101 E07M1101D key.
MQTT configuration is OK in HA but I donāt have any data coming back. If I run a frequency scan, it does not detect any (yet the same CC1101 key worked with my RPI3B).
I tested less than 3 meters from my counter: KO (while it passed with my RPI3B at more than 10m)
I rechecked my wiring and it seems OK (I adapted the following diagram according to my CC1101 key because I have only 8 pins).
If anyone has a leadā¦
How many times a day do you query the meter?
I am testing the Raspberry Pi version of this solution and it works well.
I tested the RPI version and me too it worked fine. One reading per day, I had my counter index in HA. I tried to switch to an ESP but there impossible to make it work.
I just ordered a Wemos D1 (I had an ESP from another brand before.) and a new CC1101 antenna, I will try again when I receive the material.
Iām reading my meter every 10 minutes - I will keep you all posted on how this affects battery life - currently I have 109 months remaining according to results provided by the meter.
However, as noted by other people, the meter only responds during business hours, so I ammended the code to only query between 05:00 and 18:00.
And that raises my question - does anyone know how to instruct the meter to send a command to make it respond outside business hours as well?
(I think it may be beyond the scope of this forum so I will raise it with the creator of the code as well)
Those have successfully implemented reading their meters using the CC1101 - whatās the working range on the comms?
I fear the weak link will be the power behind the broadcast within the cyble device.
Any help on this would be much appreciated - I might give this a go if thereās a chance I could communicate with my water meter at the perimeter of my propertyā¦
Mine is ~15m and with 2 solid wood doors between the reader and the meter. I had similar concerns, but seems fine. My office where I built and tested the device is at the back of my house which is even further (~30m with multiple doors/walls between it and the street, was still fine). Officially I believe the CC1101 are rated to 300m but that might be āline of sightā
1 Like
Thanks! Very helpful. My meter is buried in a small 50cm well, about 8 metres away from where the CC1101 aerial will be positioned - so there might be a chance itāll work. Ā£15 seems relatively inexpensive to try it out. 
Mines about the same, 10m away from the garage where the aerial is. In a water meter housing underground about half a metre. Been working fine for a few months now. I have it reading every hour 7-5pm Monday to Saturday. Sunday no readings get returned.
The only thing that is rubbish is you get a big spike in the morning in 1st read as itās the diff between the last at 5pm the previous day.
Looks great in the energy dashboard.
1 Like
Hi,
What frequency are you using and what counter do you have?
I have a Everblu Cyble enhanced 2 which says 433Mhz.
But canāt find the frequency.
After a few scans, I found mine was
#define FREQUENCY 433.857422f
probably different to yours though
2 Likes
Ok. Great. I will try a few more times.
Allow me, another question, did you change the following code in everblu_meters.h?
// Change these define according to your ESP8266 board
#ifdef ESP8266
#define SPI_CSK PIN_SPI_SCK
#define SPI_MISO PIN_SPI_MISO
#define SPI_MOSI PIN_SPI_MOSI
#define SPI_SS PIN_SPI_SS
#endif
Iām using a Wemos D1 mini lite.
Hello! Has anyone got the YAML that goes in the configuration.yaml file for the sensor?
Iāve got everything else up and running, but Iām unsure of how the sensor is set up. Thanks in advance!
Edit: I have mosquitto broker up and running in HA, and it will receive messages sent by the everblue_meters script when run from a PuTTY session. Iām just not sure how to permanently expose that topic within HA.
No I never changed any of that, D1 mini here also
1 Like
You donāt need nothing in yaml about sensors.
You just need to:
- Install EspMQTTClient through Arduino library manager as it required for MQTT
- Update WiFi and MQTT details in everblu-meters-esp8266.ino, if you do not use username and password for MQTT then comment those out with //
You should use the MQTTUsername and MQTTPassword defined in MQTT broker add-on in Home Assistant.
2 Likes
Yap. It seems that scanned correctly. Now updating the frequency and tomorrow Iāll check if it sent to MQTT/HA.
which cc1101 did you use?
EBYTE long distance CC1101 CC1101 433 MHz rf mĆ³dulo transmissor-recetor CC1101 433 MHz
https://www.amazon.es/dp/B07P8S9M4W?psc=1&ref=ppx_yo2ov_dt_b_product_details
My set-up is a Raspberry Pi 4, which I set up using the connections and configuration information from this README page: GitHub - neutrinus/everblu-meters: Fetch water usage data from Cyble meters
Everything works; Iām getting real values from my water meter via the everblu_meters script, which are then broadcast using mosquitto-dev, which I can successfully listen for in HA.
I figured that as soon as something broadcast to the mosquitto broker I have running on HA, the HA itself would set that ātopicā up as an appropriate device within HA - because i have the MQTT integration ādiscoverā option set to enabled.
Any help on how I can get my meter to show up in HA as an explicit device would be appreciated.