## ------------------------------------------------------------------ ## WMBUS METER D1 MINI + CC1101 for Diehl IZAR RC 868 I R4 PL ## HARDWARE: D1 MINI ESP8266 80MHz, 80KB RAM, 4MB Flash ## ## CC1101 TESTCASE FOR ALL WATERMETERS ## DO NOT USE THIS CONFIGURATION FOR PRODUCTION ## ## This version shows data from the all watermeters. ## Use this for frist test to find your watermeterID. ## ## ------------------------------------------------------------------ substitutions: ## device settings device_name_short: "water-meter-dmini" device_description: "TEST: Wasserzähler Wemos D1 Min, CUL - CC1101, IZAR module (Diehl IZAR RC 868 I R4 PL (SzczepanLeon) - find watermeters" projectname: "Diehl IZAR RC 868.Watermeter-Test" appversion: "3.0.0" ## all watermeters wmid: "0", your watermeter: wmid: !secret watermeterId ## wmid: "0" wmid: "0x43430778" ## logger settings, use DEBUG or VERBOSE to see the telegram data log_level: "DEBUG" # In production mode use "WARN" log_wmbus: "DEBUG" # Loglevel for wmbus meters component log_baudrate: "0" # Disable uart logger messages log baudrate=0 ## ---------------------------------------------------------------- ## HARDWARE: WEMOS D1 MINI ESP8266 80MHz, 80KB RAM, 4MB Flash ## ---------------------------------------------------------------- # wemmos D1 Mini = d1_mini # D1 mit externer Antenne = d1_mini_pro # esp01 mit 1MB Speicher = esp01_1m esp8266: board: d1_mini restore_from_flash: true preferences: flash_write_interval: 1min ## --------------------------------------------------- ## ESPHOME Configuration ## --------------------------------------------------- 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: then: - globals.set: id: boot_counter value: !lambda "return id(boot_counter)+=1;" - logger.log: level: WARN tag: "system" format: "BOOTMESSAGE:${device_name_short} API is connected, Device ready!" - component.update: bootcounter on_shutdown: then: - logger.log: level: ERROR tag: "system" format: "BOOTMESSAGE:${device_name_short} is down!" ## --------------------------------------------------- ## External components ## --------------------------------------------------- external_components: # uses the version 3 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@version_3 refresh: 0s components: [wmbus] ## --------------------------------------------------- ## Global variables ## --------------------------------------------------- globals: - id: boot_counter type: int restore_value: yes initial_value: "0" - id: last_value type: float restore_value: yes initial_value: "0.00" ## --------------------------------------------------- ## WIFI Settings 3 wifis ## --------------------------------------------------- wifi: networks: - ssid: !secret ssid3_name password: !secret ssid3_pswd priority: 0 - ssid: !secret ssid1_name password: !secret ssid1_pswd priority: 1 - ssid: !secret ssid2_name password: !secret ssid2_pswd priority: 2 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} ## --------------------------------------------------- ## DEBUG COMPONENT ## --------------------------------------------------- debug: update_interval: 5s ## --------------------------------------------------- ## OTA COMPONENT ## --------------------------------------------------- ota: password: !secret ota_pswd platform: esphome 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: espapiwm2_d1 port: 6053 reboot_timeout: 0s ## --------------------------------------------------- ## SNTP Time server ## --------------------------------------------------- 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: # Components should trigger on_time_sync when they update the system clock. then: - if: condition: lambda: 'return id(device_lastBoot_time).state == "";' then: - text_sensor.template.publish: id: device_lastBoot_time state: !lambda return id(time_sntp).now().strftime("%Y-%m-%dT%H:%M:%S %Z"); - logger.log: level: WARN tag: "system" format: "Synchronized sntp clock" ## --------------------------------------------------- ## WMBUS DEVICE D1MINI WEMOS --> CC1101 ## --------------------------------------------------- ## ## GDO0 ## o ## 7 ## | GD02 ╭-------o 2 (GND) ## | 6 ## | o | ## | | | ## ╭――x――x――o――o――x――x――x――o――╮ ## │ D1 D2 - │ ## │ │ ## │ D1MINI WEMOS │ ## ANT │ │ USB ## │ │ ## │ D5 D6 D7 D8 + │ ## ╰――x――x――x――o――o――o――o――o――╯ ## | | | | | ## | | | | ╰-----o 1 (+3.3V) ## | o | o ## | 5 | 8 ## | MISO| CSN ## o o ## 4 3 ## CLK MOSI ## ## -------------------------------------------------- wmbus: mosi_pin: GPIO13 #D7 MOSI Attached to Hardware SPI controller MOSI SPI Interface miso_pin: GPIO12 #D6 MISO Attached to Hardware SPI controller MISO SPI Interface clk_pin: GPIO14 #D5 SCK Attached to Hardware SPI controller CLK cs_pin: GPIO15 #D8 CSN Attached to Hardware SPI controller, Controls Boot Mode; CS SPI Interface 10k Pull-Down, boot fails if pulled high !!! gdo0_pin: GPIO04 #D1 SDA Clock output. High Impedance ! gdo2_pin: GPIO05 #D2 SCL FIFO status signals. High Impedance ! # log_unknown (Optional): Show telegrams from not configured meters in log. Defaults to False log_unknown: True ## --------------------------------------------------- ## 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: ${wmid} type: izar 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: name: "CC1101 LQI" id: wmbus_cc1101_lqi entity_category: "diagnostic" state_class: "measurement" 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: "CC1101 RSSI" id: wmbus_cc1101_rssi unit_of_measurement: "dBm" icon: mdi:rss state_class: "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 icon: mdi:counter on_value: then: - lambda: |- ESP_LOGD("system", "Water Display value: %f, last value: %f", id(waterdisplay).state, id(last_value)); id(last_value)=id(waterdisplay).state; # water current month (wM-Bus v2.1.4) current_month_total_water_l: name: "Water 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 v2.1.4). 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" state_class: "measurement" accuracy_decimals: 2 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" state_class: "measurement" icon: mdi:timelapse # get the current alarmcode (wM-Bus v2.1.4) current_alarms: id: "watermeter_current_alarms" name: "Watermeter current alarm" entity_category: "diagnostic" icon: mdi:alarm-light # get the previous alarmcode (wM-Bus v2.1.4) previous_alarms: id: "watermeter_prev_alarms" name: "Watermeter previous alarm" entity_category: "diagnostic" icon: mdi:alarm-light # Wifi quality RSSI (%) - platform: wifi_signal name: Device WLAN Signal id: wifi_signal_db update_interval: 60s filters: - lambda: return min(max(2 * (x + 100.0), 0.0), 100.0); entity_category: "diagnostic" unit_of_measurement: "%" # The debug component can be used to debug problems with ESPHome. # At startup, it prints a bunch of useful information like reset reason, # free heap size, ESPHome version and so on. - platform: debug # Reports the free heap size in bytes. free: name: "Heap Free" entity_category: "diagnostic" # Reports the fragmentation metric of the heap (0% is clean, more than ~50% is not harmless). fragmentation: name: "Heap Fragmentation" entity_category: "diagnostic" # Reports the largest contiguous free RAM block on the heap in bytes. block: name: "Heap Max Block" entity_category: "diagnostic" # Reports the longest time between successive iterations of the main loop. loop_time: name: "Application Loop Time" entity_category: "diagnostic" # device boot counter - platform: template name: Boot counter id: bootcounter accuracy_decimals: 0 state_class: "measurement" entity_category: "diagnostic" lambda: |- return (id(boot_counter)); ## --------------------------------------------------- ## SWITCHES ## --------------------------------------------------- switch: # reset boot counter value - platform: template name: Boot Counter reset 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 # restart device - platform: restart name: "Restart device" id: restart_switch # save device boot (develop only) - platform: safe_mode name: "Restart (Safe Mode)" # reset the device to factory reset (develop only) - platform: factory_reset icon: mdi:lock-reset name: Restart factory default ## --------------------------------------------------- ## TEXT SENSORS ## --------------------------------------------------- text_sensor: - platform: debug # Reports the device information: device: name: "Device Info" entity_category: "diagnostic" # Reports the last reboot reason in a human-readable form. reset_reason: name: "Reset Reason" entity_category: "diagnostic" # Last boot timestamp - platform: template name: "Last Boot timestamp" disabled_by_default: true id: device_lastBoot_time icon: mdi:clock-start