Esphome + node mcu + c1101 no signal

Maurizio · 17 Grudzień 2023 19:59

Let me start by saying I’m a neophile
I’m trying to run the system to acquire the consumption of a hyperl sensus meter
I don’t think he’s reading anything.
I tried putting an antenna connected to the more powerful c1101 component, but nothing
I tried bringing the antenna closer to the meter with an SMA extension. but nothing.
I can’t move nodemcu closer to the meter because it doesn’t receive the wireless line.
I was thinking of using the wired line but I see that everything is a bit complicated and I’m not sure that it will work.
Do you have any advice for me?
this is my yaml

this is output

thanks

szopen · 17 Grudzień 2023 20:34

please paste YAML and also logs as is,
pictures only as additional resources…

Maurizio · 17 Grudzień 2023 20:50

substitutions:

   ## device settings
  device_name_short: "water-meter-nmc"
  device_description: "Wasserzähler NODEMCU V3 + CUL - CC1101, IZAR module (Diehl IZAR RC 868 I R4 PL (SzczepanLeon) - all Watermeters"
  projectname: "Diehl IZAR RC 868.Watermeter"
  appversion: "2.0.7"

  ## logger settings
  log_level: "DEBUG"  # not that logging need memory, so in production mode use "WARN"
  log_wmbus: "DEBUG" # Loglevel for wmbus meters component
  log_baudrate: "0" # 0 disable uart logger messages

# ----------------------------------------------------------------
# HARDWARE:  NODEMCU V3 ESP8266 80MHz, 80KB RAM, 4MB Flash
# ----------------------------------------------------------------
esp8266:
  board: nodemcuv2
  restore_from_flash: true

## ----------------------------------------------------------------
## ESPHOME APPLICATION
## ----------------------------------------------------------------
esphome:
  name: ${device_name_short}
  comment: ${device_description}
  # Automatically add the mac address to the name
  # so you can use a single firmware for all devices
  name_add_mac_suffix: false
  project:
    name: ${projectname}
    version: ${appversion}
  build_path: ./build/${device_name_short}
  on_boot:
    priority: -100.00
    then:
      - globals.set:
          id: boot_counter
          value: !lambda "return id(boot_counter)+=1;"
      - logger.log:
          level: INFO
          tag: "system"
          format: "BOOTMESSAGE:${device_name_short} API is connected, Device ready!"
      - component.update: bootcounter
  on_shutdown:
    priority: 700
    then:
      - logger.log:
          level: ERROR
          tag: "system"
          format: "BOOTMESSAGE:${device_name_short} is down!"

## ----------------------------------------------------------------
## External components
## ----------------------------------------------------------------
external_components:

  # uses the latest version from SzczepanLeon
  # https://github.com/SzczepanLeon/esphome-components
  # You can make ESPHome check the repository every time by setting this option to 0s
  - source: github://SzczepanLeon/esphome-components@main
    refresh: 0s
    components: [wmbus]

  # use local component from
  # https://github.com/zdzichu6969/esphome-components
  - source:
      type: local
      path: custom_components
    components: [backup]

backup:
  auth:
    username: !secret web_username
    password: !secret web_password
  force_update: false

## ----------------------------------------------------------------
## Global variables
## ----------------------------------------------------------------
globals:

  - id: boot_counter
    type: int
    restore_value: yes
    initial_value: "0"

## ---------------------------------------------------
## WIFI Settings 3 wifis
## ---------------------------------------------------
wifi:
  id: wifi_nodemcu
  networks:
    - ssid: !secret ssid1_name
      password: !secret ssid1_pswd
      priority: 0
  domain: !secret domain

## ---------------------------------------------------
## mDNS Component
## ---------------------------------------------------
mdns:
  # if mDNS is disabled, they will no longer be able to automatically find your devices.
  disabled: false

## ---------------------------------------------------
## The captive portal component in ESPHome is a
## fallback mechanism for when connecting to the
## configured WiFi fails.
## ---------------------------------------------------
captive_portal:

## ---------------------------------------------------
## LOGGER COMPONENT
## ---------------------------------------------------
logger:
  id: appslogger
  level: ${log_level}
  baud_rate: ${log_baudrate}
  logs:
    wmbus: ${log_wmbus}
    wMBus-lib: ${log_wmbus}

## ---------------------------------------------------
## OTA COMPONENT
## ---------------------------------------------------
ota:
  password: !secret ota_pswd
  safe_mode: false
  on_begin:
    then:
      - logger.log:
          format: "OTA Start"
          tag: "OTA"
          level: WARN
  on_progress:
    then:
      - logger.log:
          level: WARN
          tag: "OTA"
          format: "OTA progress %0.1f%%"
          args: ["x"]
  on_end:
    then:
      - logger.log:
          format: "OTA End"
          tag: "OTA"
          level: WARN
  on_error:
    then:
      - logger.log:
          format: "OTA update error %d"
          tag: "OTA"
          level: ERROR
          args: ["x"]

## ---------------------------------------------------
## COMPONENT WEBSERVER
## ---------------------------------------------------
web_server:
  port: 80
  version: 2
  js_url: !secret webserver_jsurl

## ---------------------------------------------------
## Home Assistant API COMPONENT
## ---------------------------------------------------
api:
  id: espapnuc
  port: 6053
  reboot_timeout: 0s

## ---------------------------------------------------
## SNTP COMPONENT
## ---------------------------------------------------
time:
  - platform: sntp
    id: time_sntp
    timezone: Europe/Berlin
    servers:
      - 0.at.pool.ntp.org
      - 0.pool.ntp.org
      - 1.pool.ntp.org

    on_time_sync:
      then:
        - logger.log:
            tag: "system"
            level: INFO
            format: "Synchronized sntp clock"

# ---------------------------------------
# COMPONENT MQTT Brocker
# ---------------------------------------
mqtt:
  broker: !secret mqtt_broker1
  port: !secret mqtt_port1
  username: !secret mqtt_username1
  password: !secret mqtt_password1
  

wmbus:
  mosi_pin: GPIO13  
  miso_pin: GPIO12  
  clk_pin: GPIO14   
  cs_pin: GPIO15    
  gdo0_pin: GPIO05  
  gdo2_pin: GPIO04  

  # log_unknown (Optional): Show telegrams from not configured meters in log. Defaults to False
  log_unknown: True

## ---------------------------------------------------
## SWITCHES
## ---------------------------------------------------
switch:
  # reset boot counter value
  - platform: template
    name: "Device Reset Boot Counter"
    turn_on_action:
      then:
        - lambda: |-
            id(boot_counter) = 0;
            id(bootcounter).publish_state(id(boot_counter));
        - logger.log:
            level: WARN
            tag: "system"
            format: "${device_name_short} reset boot counter o.k!"
        - component.update: bootcounter

  - platform: restart
    name: "Device Restart"
    id: restart_switch

  # save device boot (develop only)
  - platform: safe_mode
    name: "Device Restart (Safe Mode)"

  # reset the device to factory reset (develop only)
  - platform: factory_reset
    name: "Device Restart Factory"

## ---------------------------------------------------
## SENSORS
## ---------------------------------------------------
sensor:

  - platform: wmbus
    # Meter ID (usually from sticker). Can be specified as decimal or hex.
    # only hex is working for my watermeter !
    # see: https://github.com/SzczepanLeon/esphome-components/issues/6
    # edit watermeterid in the secrets file
    # settings to add the watermeterid to the lqi, rssi and total_water_m3
    meter_id: 0
    #meter_id: "000000" # !secret watermeterId
    type: iperl
    key: ""
    add_prefix: true

    # The LQI value reported by the CC1101 is a 7 bit unsigned number with a range from 0 to 127.
    # Note that a lower value indicates a better link.
    # The LQI of a received packet will be bad (higher number) when there is lot of interference.
    lqi:
      id: wmbus_cc1101_lqi
      name: "WLAN CC1101 LQI"
      entity_category: "diagnostic"
      unit_of_measurement: "lqi"

    # The RSSI value reported by the CC1101 is a 8 bit signed number with an effective
    # range from -138 dBm to -10.5 dBm when the CC1101 is operating around 868 MHz.
    # RSSI stands for received signal strength (power) indication (in dBm).
    # A higher value indicates higher power. (internal only)
    rssi:
      name: "WLAN CC1101 RSSI"
      id: wmbus_cc1101_rssi
      unit_of_measurement: "%"
      entity_category: "diagnostic"

    # waterdisplay - get the total watermter m3 from the wmbus telegram
    total_water_m3:
      name: "Watermeter Display"
      id: "waterdisplay"
      unit_of_measurement: "m³"
      state_class: total_increasing
      device_class: "water"
      accuracy_decimals: 3
      on_value:
        then:
          - lambda: |-
              ESP_LOGI("wmbus", "Water Display value: %f", id(waterdisplay).state);

    # water current month (wM-Bus v2.1.4)
    current_month_total_water_l:
      name: "Watermeter current month"
      id: "watermonth"
      accuracy_decimals: 2
      unit_of_measurement: "L"
      state_class: total_increasing
      device_class: "water"

    # get the last month total watermter m3 from the wmbus telegram  (wM-Bus 2.1.10)
    last_month_total_water_m3:
      name: "Water last month"
      id: "waterdisplay_lastmonth"
      unit_of_measurement: "m³"
      state_class: total_increasing
      device_class: "water"
      accuracy_decimals: 3
      icon: mdi:counter

    # get the battery life time (wM-Bus v2.1.4)
    remaining_battery_life_y:
      name: "Watermeter battery life"
      id: "watermeter_batterie"
      entity_category: "diagnostic"
      icon: mdi:battery

    # get the last transmit periode (wM-Bus v2.1.4)
    transmit_period_s:
      name: "Watermeter transmit periode"
      id: "watermeter_last_reading"
      entity_category: "diagnostic"
      icon: mdi:timelapse

    current_alarms:
      id: "watermeter_current_alarms"
      name: "Watermeter current alarm"
      entity_category: "diagnostic"
      icon: mdi:alarm-light

    previous_alarms:
      id: "watermeter_prev_alarms"
      name: "Watermeter previous alarm"
      entity_category: "diagnostic"
      icon: mdi:alarm-light

  # Wifi quality RSSI used by wifi_signal_db
  - platform: wifi_signal
    id: wifi_signal_db
    update_interval: 60s
    internal: true
    disabled_by_default: true

  # Wifi quality RSSI in percentage
  # Received Signal Strength (RSSI) is a measure of incoherent (raw) RF power in a channel.
  - platform: copy # Reports the WiFi signal strength in %
    source_id: wifi_signal_db
    name: "Device WLAN RSSI"
    filters:
      - lambda: return min(max(2 * (x + 100.0), 0.0), 100.0);
    unit_of_measurement: "%"
    entity_category: "diagnostic"

 # device boot counter
  - platform: template
    name: Device Boot counter
    id: bootcounter
    accuracy_decimals: 0
    state_class: "measurement"
    entity_category: "diagnostic"
    lambda: return (id(boot_counter));

INFO ESPHome 2023.11.6
INFO Reading configuration /config/esphome/esphome-web-ed57ca.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@main
INFO Starting log output from water-meter-nmc.local using esphome API
INFO Successfully connected to water-meter-nmc in 0.120s
INFO Successful handshake with water-meter-nmc in 0.034s
[21:48:10][I][app:102]: ESPHome version 2023.11.6 compiled on Dec 17 2023, 20:38:50
[21:48:10][I][app:104]: Project Diehl_IZAR_RC_868.Watermeter version 2.0.7
[21:48:10][C][wifi:559]: WiFi:
[21:48:10][C][wifi:391]:   Local MAC: 84:F3:EB:ED:57:CA
[21:48:10][C][wifi:396]:   SSID: 'eero_zt'[redacted]
[21:48:10][C][wifi:397]:   IP Address: 192.168.1.81
[21:48:10][C][wifi:398]:   BSSID: 80:B9:7A:D5:F3:06[redacted]
[21:48:10][C][wifi:400]:   Hostname: 'water-meter-nmc'
[21:48:10][C][wifi:402]:   Signal strength: -56 dB ▂▄▆█
[21:48:10][C][wifi:406]:   Channel: 6
[21:48:10][C][wifi:407]:   Subnet: 255.255.255.0
[21:48:10][C][wifi:408]:   Gateway: 192.168.1.254
[21:48:10][C][wifi:409]:   DNS1: 192.168.1.209
[21:48:10][C][wifi:410]:   DNS2: 192.168.1.219
[21:48:10][C][logger:416]: Logger:
[21:48:10][C][logger:417]:   Level: DEBUG
[21:48:10][C][logger:418]:   Log Baud Rate: 0
[21:48:10][C][logger:420]:   Hardware UART: UART0
[21:48:10][C][logger:424]:   Level for 'wmbus': DEBUG
[21:48:10][C][logger:424]:   Level for 'wMBus-lib': DEBUG
[21:48:10][C][template.sensor:022]: Template Sensor 'Device Boot counter'
[21:48:10][C][template.sensor:022]:   State Class: 'measurement'
[21:48:10][C][template.sensor:022]:   Unit of Measurement: ''
[21:48:10][C][template.sensor:022]:   Accuracy Decimals: 0
[21:48:10][C][template.sensor:023]:   Update Interval: 60.0s
[21:48:10][C][template.switch:068]: Template Switch 'Device Reset Boot Counter'
[21:48:10][C][template.switch:090]:   Restore Mode: always OFF
[21:48:10][C][template.switch:057]:   Optimistic: NO
[21:48:10][C][restart:068]: Restart Switch 'Device Restart'
[21:48:10][C][restart:070]:   Icon: 'mdi:restart'
[21:48:10][C][restart:090]:   Restore Mode: always OFF
[21:48:10][C][safe_mode_switch:068]: Safe Mode Switch 'Device Restart (Safe Mode)'
[21:48:10][C][safe_mode_switch:070]:   Icon: 'mdi:restart-alert'
[21:48:10][C][safe_mode_switch:090]:   Restore Mode: always OFF
[21:48:10][C][factory_reset.switch:068]: Factory Reset Switch 'Device Restart Factory'
[21:48:10][C][factory_reset.switch:070]:   Icon: 'mdi:restart-alert'
[21:48:10][C][factory_reset.switch:090]:   Restore Mode: always OFF
[21:48:10][C][copy.sensor:015]: Copy Sensor 'Device WLAN RSSI'
[21:48:10][C][copy.sensor:015]:   Device Class: 'signal_strength'
[21:48:10][C][copy.sensor:015]:   State Class: 'measurement'
[21:48:10][C][copy.sensor:015]:   Unit of Measurement: '%'
[21:48:10][C][copy.sensor:015]:   Accuracy Decimals: 0
[21:48:10][C][captive_portal:088]: Captive Portal:
[21:48:10][C][backup:033]: Backup:
[21:48:10][C][backup:034]:   URL path is /config.yaml
[21:48:10][C][backup:036]:   Basic authentication enabled
[21:48:10][C][web_server:168]: Web Server:
[21:48:10][C][web_server:169]:   Address: water-meter-nmc.local:80
[21:48:10][C][sntp:053]: SNTP Time:
[21:48:10][C][sntp:054]:   Server 1: '0.at.pool.ntp.org'
[21:48:10][C][sntp:055]:   Server 2: '0.pool.ntp.org'
[21:48:10][C][sntp:056]:   Server 3: '1.pool.ntp.org'
[21:48:10][C][sntp:057]:   Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[21:48:10][C][mdns:115]: mDNS:
[21:48:10][C][mdns:116]:   Hostname: water-meter-nmc
[21:48:10][C][ota:097]: Over-The-Air Updates:
[21:48:10][C][ota:098]:   Address: water-meter-nmc.local:8266
[21:48:10][C][ota:101]:   Using Password.
[21:48:10][C][api:139]: API Server:
[21:48:10][C][api:140]:   Address: water-meter-nmc.local:6053
[21:48:10][C][api:144]:   Using noise encryption: NO
[21:48:10][C][mqtt:133]: MQTT:
[21:48:10][C][mqtt:134]:   Server Address: 192.168.1.224:1883 (192.168.1.224)
[21:48:10][C][mqtt:136]:   Username: ''[redacted]
[21:48:10][C][mqtt:137]:   Client ID: 'water-meter-nmc-84f3ebed57ca'[redacted]
[21:48:10][C][mqtt:139]:   Discovery prefix: 'homeassistant'
[21:48:10][C][mqtt:140]:   Discovery retain: YES
[21:48:10][C][mqtt:142]:   Topic Prefix: 'water-meter-nmc'
[21:48:10][C][mqtt:144]:   Log Topic: 'water-meter-nmc/debug'
[21:48:10][C][mqtt:147]:   Availability: 'water-meter-nmc/status'
[21:48:10][C][wifi_signal.sensor:009]: WiFi Signal 'wifi_signal_db'
[21:48:10][C][wifi_signal.sensor:009]:   Device Class: 'signal_strength'
[21:48:10][C][wifi_signal.sensor:009]:   State Class: 'measurement'
[21:48:10][C][wifi_signal.sensor:009]:   Unit of Measurement: 'dBm'
[21:48:10][C][wifi_signal.sensor:009]:   Accuracy Decimals: 0
[21:48:10][C][mqtt.switch:041]: MQTT Switch 'Device Reset Boot Counter': 
[21:48:10][C][mqtt.switch:042]:   State Topic: 'water-meter-nmc/switch/device_reset_boot_counter/state'
[21:48:10][C][mqtt.switch:042]:   Command Topic: 'water-meter-nmc/switch/device_reset_boot_counter/command'
[21:48:10][C][mqtt.switch:041]: MQTT Switch 'Device Restart': 
[21:48:10][C][mqtt.switch:042]:   State Topic: 'water-meter-nmc/switch/device_restart/state'
[21:48:10][C][mqtt.switch:042]:   Command Topic: 'water-meter-nmc/switch/device_restart/command'
[21:48:10][C][mqtt.switch:041]: MQTT Switch 'Device Restart (Safe Mode)': 
[21:48:10][C][mqtt.switch:042]:   State Topic: 'water-meter-nmc/switch/device_restart_safe_mode/state'
[21:48:10][C][mqtt.switch:042]:   Command Topic: 'water-meter-nmc/switch/device_restart_safe_mode/command'
[21:48:10][C][mqtt.switch:041]: MQTT Switch 'Device Restart Factory': 
[21:48:10][C][mqtt.switch:042]:   State Topic: 'water-meter-nmc/switch/device_restart_factory/state'
[21:48:10][C][mqtt.switch:042]:   Command Topic: 'water-meter-nmc/switch/device_restart_factory/command'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 WLAN CC1101 LQI':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_wlan_cc1101_lqi/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 WLAN CC1101 RSSI':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_wlan_cc1101_rssi/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Watermeter Display':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_watermeter_display/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Watermeter current month':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_watermeter_current_month/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Water last month':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_water_last_month/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Watermeter battery life':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_watermeter_battery_life/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Watermeter transmit periode':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_watermeter_transmit_periode/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Watermeter current alarm':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_watermeter_current_alarm/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor '0x00 Watermeter previous alarm':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/0x00_watermeter_previous_alarm/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor 'Device WLAN RSSI':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/device_wlan_rssi/state'
[21:48:10][C][mqtt.sensor:028]: MQTT Sensor 'Device Boot counter':
[21:48:10][C][mqtt.sensor:032]:   State Topic: 'water-meter-nmc/sensor/device_boot_counter/state'
[21:48:10][C][wmbus:416]: wM-Bus v2.4.6:
[21:48:10][C][wmbus:433]:   CC1101 frequency: 868.950 MHz
[21:48:10][C][wmbus:434]:   CC1101 SPI bus:
[21:48:10][C][wmbus:435]:     MOSI Pin: GPIO13
[21:48:10][C][wmbus:436]:     MISO Pin: GPIO12
[21:48:10][C][wmbus:437]:     CLK Pin:  GPIO14
[21:48:10][C][wmbus:438]:     CS Pin:   GPIO15
[21:48:10][C][wmbus:439]:     GDO0 Pin: GPIO5
[21:48:10][C][wmbus:440]:     GDO2 Pin: GPIO4
[21:48:10][C][wmbus:447]:   Available drivers:  amiplus, apator08, apator162, apatoreitn, bmeters, c5isf, compact5, dme07, elf, evo868, fhkvdataiii, hydrocalm3, hydrus, iperl, itron, izar, mkradio3, mkradio4, qheat, qwater, sharky774, topaseskr, ultrimis, unismart, vario451
[21:48:10][C][wmbus:465]:   Meter:
[21:48:10][C][wmbus:466]:     ID: 0 [0x00000000]
[21:48:10][C][wmbus:467]:     Type: iperl
[21:48:10][C][wmbus:468]:     Mode: T1
[21:48:10][C][wmbus:469]:     Key: ''
[21:48:10][C][wmbus:471]:     Sensor '0x00 Watermeter current alarm'
[21:48:10][C][wmbus:471]:       State Class: ''
[21:48:10][C][wmbus:471]:       Unit of Measurement: ''
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 0
[21:48:10][C][wmbus:471]:       Icon: 'mdi:alarm-light'
[21:48:10][C][wmbus:471]:     Sensor '0x00 Watermeter current month'
[21:48:10][C][wmbus:471]:       Device Class: 'water'
[21:48:10][C][wmbus:471]:       State Class: 'total_increasing'
[21:48:10][C][wmbus:471]:       Unit of Measurement: 'L'
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 2
[21:48:10][C][wmbus:471]:       Icon: 'mdi:water'
[21:48:10][C][wmbus:471]:     Sensor '0x00 Water last month'
[21:48:10][C][wmbus:471]:       Device Class: 'water'
[21:48:10][C][wmbus:471]:       State Class: 'total_increasing'
[21:48:10][C][wmbus:471]:       Unit of Measurement: 'm³'
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 3
[21:48:10][C][wmbus:471]:       Icon: 'mdi:counter'
[21:48:10][C][wmbus:471]:     Sensor '0x00 WLAN CC1101 LQI'
[21:48:10][C][wmbus:471]:       Device Class: 'signal_strength'
[21:48:10][C][wmbus:471]:       State Class: 'measurement'
[21:48:10][C][wmbus:471]:       Unit of Measurement: 'lqi'
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 0
[21:48:10][C][wmbus:471]:     Sensor '0x00 Watermeter previous alarm'
[21:48:10][C][wmbus:471]:       State Class: ''
[21:48:10][C][wmbus:471]:       Unit of Measurement: ''
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 0
[21:48:10][C][wmbus:471]:       Icon: 'mdi:alarm-light'
[21:48:10][C][wmbus:471]:     Sensor '0x00 Watermeter battery life'
[21:48:10][C][wmbus:471]:       State Class: 'measurement'
[21:48:10][C][wmbus:471]:       Unit of Measurement: ''
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 0
[21:48:10][C][wmbus:471]:       Icon: 'mdi:battery'
[21:48:10][C][wmbus:471]:     Sensor '0x00 WLAN CC1101 RSSI'
[21:48:10][C][wmbus:471]:       Device Class: 'signal_strength'
[21:48:10][C][wmbus:471]:       State Class: 'measurement'
[21:48:10][C][wmbus:471]:       Unit of Measurement: '%'
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 0
[21:48:10][C][wmbus:471]:     Sensor '0x00 Watermeter Display'
[21:48:10][C][wmbus:471]:       Device Class: 'water'
[21:48:10][C][wmbus:471]:       State Class: 'total_increasing'
[21:48:10][C][wmbus:471]:       Unit of Measurement: 'm³'
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 3
[21:48:10][C][wmbus:471]:       Icon: 'mdi:water'
[21:48:10][C][wmbus:471]:     Sensor '0x00 Watermeter transmit periode'
[21:48:10][C][wmbus:471]:       State Class: 'measurement'
[21:48:10][C][wmbus:471]:       Unit of Measurement: 's'
[21:48:10][C][wmbus:471]:       Accuracy Decimals: 0
[21:48:10][C][wmbus:471]:       Icon: 'mdi:timelapse'
[21:48:50][D][sensor:093]: 'Device Boot counter': Sending state 1.00000  with 0 decimals of accuracy
[21:49:03][D][sensor:093]: 'wifi_signal_db': Sending state -58.00000 dBm with 0 decimals of accuracy
[21:49:03][D][sensor:093]: 'Device WLAN RSSI': Sending state 84.00000 % with 0 decimals of accuracy

szopen · 17 Grudzień 2023 20:52

Complete YAML please (can be with comments, use post edit feature
I have broken keyboard so it is not easy to write anything…

You should delete sensor section, because you need any telegrams in the log before configuring sensor

Maurizio · 17 Grudzień 2023 21:11

I copied everything
So I have to remove the whole part from lqi: onwards?

szopen · 17 Grudzień 2023 21:28

You should delete wmbus sensors related part only (as it is bad for sure - meter id isn’t zero, so you have to find any info in logs before configuring that sensor),
in fact you need any raw telegrams in the logs, so you can decode them online here
https://wmbusmeters.org/
and only having decoded information you can do some working sensor configuration in the YAML.
A necessary condition is the correct operation of the CC1101 receiver.

Maurizio · 18 Grudzień 2023 07:54

I purchased this shield c1101

honestly, I’m not sure about connecting the following 2 pins
clk_pin
cs_pin

As you can see from the photo they are not shown so I gave it a try
The device seems to work.
But I’m not sure.
He certainly doesn’t hear anything even if it doesn’t give an error.
I don’t know if using an antenna with an extension cord makes things better.
The device is currently 10/15 meters from the meter.
Maybe they are too far away?
the only obstacle is the garage door.
I’ve seen that some have used devices like this to overcome the distance:
SDR DVB-T RTL2832U R820T2 RTL-SDR

Thanks in advance

szopen · 18 Grudzień 2023 10:03

This module looks nice, but it’s still Chinese… You can verify the connections using the official data sheet

but in my opinion (but only you can veriify it having this in hands):
SCK = CLK
CKN = CS

You should know if your meter is 433MHz or 868MHz it is a must, because CC1101 modules have different antena filters depending on band. Yours (based on photo) is 433MHz

szopen · 18 Grudzień 2023 10:29

Post został podzielony na nowy temat: Bmeters roblem z odczytem jednego z 2 identycznych wodomierzy

Maurizio · 21 Grudzień 2023 08:26

HI
I’m trying to use a new board
az-delivery-devkit-v4
But I have even more problems

now I have this error:
[09:20:47][C][wmbus:416]: wM-Bus v2.4.9:
[09:20:47][C][wmbus:433]: CC1101 frequency: 434.475 MHz
[09:20:47][C][wmbus:434]: CC1101 SPI bus:
[09:20:47][C][wmbus:435]: MOSI Pin: GPIO23
[09:20:47][C][wmbus:436]: MISO Pin: GPIO19
[09:20:47][C][wmbus:437]: CLK Pin: GPIO18
[09:20:47][C][wmbus:438]: CS Pin: GPIO5
[09:20:47][C][wmbus:439]: GDO0 Pin: GPIO16
[09:20:47][C][wmbus:440]: GDO2 Pin: GPIO17
[09:20:47][E][wmbus:453]: Check connection to CC1101!
I followed a tutorial that gave this configuration.
Honestly, I’m starting to doubt whether I’ll get a result
Now I will try to buy a new shield cc1101
Maybe you can give me some more info on a shied to buy that is fine
Thanks in advance
Maurizio