Hi,

HA is generating huge amounts of these log entries, but I can’t find the source:

home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'as_timestamp' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'as_timestamp' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'timestamp_custom' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'as_timestamp' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_r')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'as_timestamp' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'timestamp_custom' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_r')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'as_timestamp' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_ri')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'as_timestamp' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'timestamp_custom' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_ri')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'as_timestamp' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_ris')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'as_timestamp' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'timestamp_custom' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_ris')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'as_timestamp' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_risi')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'as_timestamp' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'timestamp_custom' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_risi')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'as_timestamp' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_risin')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'as_timestamp' will return 'None', however this template will fail to render in Home Assistant core 2022.1
home-assistant.log.1:2022-01-20 11:33:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'timestamp_custom' got invalid input 'None' when rendering template '# {{ as_timestamp(state_attr('sun.sun', 'next_risin')) | timestamp_custom('%H:%M') }}' but no default was specified. Currently 'timestamp_custom' will return 'None', however this template will fail to render in Home Assistant core 2022.1

Problem is, I’ve got absolutely no idea where this template is defined. It was part of a Markdown dashboard card, but I deleted that one. I checked all the plain-text files in my conf dir manually, nowhere to be found. Restarting HA has no effect.

Is there some caching going on?

Installation details:

System Health

1 post - 1 participant

Read full topic

Hi all.
I’ve been trying to improve an automation for two months and I can’t. @Didgeridrew and @123 helped me with the templatehttps://community.home-assistant.io/t/help-with-template-in-automation-to-control-netatmo-valves-with-a-thermostat/363233 and it works but there are many times that it doesn’t and I need help. I put it and explain:

alias: termostato_atico_on_alternativa
trigger:
  - platform: numeric_state
    entity_id: climate.termostato_atiko
    value_template: >-
      {{ ((state_attr('climate.termostato_atiko', 'temperature') | float) -
      (state_attr('climate.termostato_atiko', 'current_temperature') | float)) |
      abs }}
    above: 0.1
condition: []
action:
  - service: script.turn_on
    target:
      entity_id: script.valvula_atico_on
mode: single

alias: termostato_atico_off
trigger:
  - platform: numeric_state
    entity_id: climate.termostato_atiko
    value_template: >-
      {{ (state.attributes.current_temperature - state.attributes.temperature) |
      abs }}
    above: 1
condition: []
action:
  - service: >-
      script.turn_{{ 'on' if state_attr('climate.termostato_atiko',
      'current_temperature')|float >= state_attr('climate.termostato_atiko',
      'temperature')|float else 'off' }}
    target:
      entity_id: script.valvula_atico_off
mode: single

The shutdown automation has no problem, where I have the problem is in the startup. For triogger it, it is MANDATORY that the temperatures are equal and drop 0.1, if the schedule varies the target temperature and it is higher than the temperature, the boiler turns on but the valves are closed.

I have been reading the documentation and the template model has that mandatory feature. In this post of @Didgeridrew Help with template in automation to control netatmo valves with a thermostat - #10 by Didgeridrew . Is there any way to make it work?

Thanks for the help and sorry for the Google translation.

1 post - 1 participant

Read full topic

At the moment I use a Veraedge for about 6 years, and have plugin/app Reactor which is a very powerfull tool to do automations. At the moment I have HA running in docker on my Synology NAS and connected a conbee 2 to pay with Zigbee.

I have some questions/findings. In Vera you can use/create virutal switches. I use this virtual switch to start an automation which sets my heater on for 10 minutes and of for 15 minutes in a loop, as long as the virtual switch is set to on.

I was a bit disappointed not to find a virtual switch in HA, but only the binary helper. Which is not completely the same, as it toggles. I know Homey also has virtual switches.

How can I solve this in HA?

1 post - 1 participant

Read full topic

What i cant understant? I try to make hours forecast card but weather.home_hourly isint work at all?
“Entity not available”

1 post - 1 participant

Read full topic

Hi, I’ve tried the following:

1. Manually upload the backup file on startup screen & later on the supervisor backup page. But I keep getting this error

2. Upload the backup file to /usr/share/hassio/backup using winscp. Tapping the reload option nor restarting the homeassistant does not list down the backup file in the ui
   

3. Google Drive backup just fails to download the file to homeassistant.
   

Nothing shows up the logs for some reason

Any ideas on how I could fix this?

1 post - 1 participant

Read full topic

Hi all,

Have been using home assistant for the better part of a month and migrated almost completely from Homey and really enjoying the experience so far. The dashboards, the node-red flows, everything that can be integrated, just wow!

I’m facing one issue, have integrated my Blink camera’s (two sync modules, 5 camera’s) and would like to trigger a recording of the camera on my driveway, based on motion at my front door coming from the ring camera. The blink camera is further away but would like a second angle of the person/motion event for my door.

This worked in Homey but this is one of the flows which I can’t get to work and/or understand what to do. Is it even possible with the current or any integration to start a recording on a blink camera? If anybody can point me in the right direction/tell me if it’s even possible or has a node-red flow to share, that would be much appreciated.

1 post - 1 participant

Read full topic

Hi all,

I’m tring to figure out how to allign a peace of text with the icon in front off it.

In the image below you can see that the icon is a little bit higher than the text behind it:

I’m also trying to integrate a picture as the background of the card, but that doesn’t seem to work the way i quessed it.
Any help would be really appreciated

The code:

type: custom:button-card
entity: person.maurice
icon: mdi:account
aspect_ratio: 1/1
name: Maurice
styles:
  card:
    - background: /local/images/Maurice.jpg
    - border-radius: 10%
    - padding: 10%
    - color: ivory
    - font-size: 15px
    - text-shadow: 0px 0px 5px black
    - text-transform: capitalize
  grid:
    - grid-template-areas: '"i temp" "n n" "Batterij Batterij" "Wifi Wifi" "Locatie Locatie"'
    - grid-template-columns: 1fr 1fr
    - grid-template-rows: 1fr min-content min-content min-content min-content
  name:
    - font-weight: bold
    - font-size: 30px
    - color: white
    - align-self: middle
    - justify-self: start
    - padding-bottom: 4px
  img_cell:
    - justify-content: start
    - align-items: start
    - margin: none
  icon:
    - color: |
        [[[
          if (entity.state < 60) return 'lime';
          if (entity.state >= 60 && entity.state < 80) return 'orange';
          else return 'red';
        ]]]
    - width: 70%
    - margin-top: '-10%'
  custom_fields:
    Wifi:
      - padding-bottom: 2px
      - align-self: middle
      - justify-self: start
      - '--text-color-sensor': >-
          [[[ if (states["sensor.iphone_van_maurice_bssid"].state > 80) return
          "red"; ]]]
    Batterij:
      - padding-bottom: 2px
      - align-self: middle
      - justify-self: start
      - '--text-color-sensor': >-
          [[[ if (states["sensor.iphone_van_maurice_battery_level"].state > 60)
          return "green"; ]]]
    Locatie:
      - padding-bottom: 2px
      - align-self: middle
      - justify-self: start
      - '--text-color-sensor': >-
          [[[ if (states["sensor.iphone_van_maurice_distance"].state > 80)
          return "red"; ]]]
custom_fields:
  Wifi: |
    [[[
      return `<ha-icon
        icon="mdi:wifi-arrow-up-down"
        style="width: 40px; height: 20px; color: deepskyblue;">
        </ha-icon><span>WIFI: <span style="color: var(--text-color-sensor);">${states['sensor.iphone_van_maurice_ssid'].state}</span></span>`
    ]]]
  Batterij: |
    [[[
      return `<ha-icon
        icon="mdi:battery-charging-30"
        style="width: 40px; height: 20px; color: deepskyblue;">
        </ha-icon><span>Batterij: <span style="color: var(--text-color-sensor);">${states['sensor.iphone_van_maurice_battery_level'].state}%</span></span>`
    ]]]
  Locatie: |
    [[[
      return `<ha-icon
        icon="mdi:map-marker"
        style="width: 40px; height: 20px; color: deepskyblue;">
        </ha-icon><span>Locatie: <span style="color: var(--text-color-sensor);">${states['device_tracker.iphone_van_maurice_2'].state}</span></span>`
    ]]]

1 post - 1 participant

Read full topic

Hi, I’m setting up a new Linux server (Ubuntu) for my home hassistant.
I have HA supervised, installed into a container.
NGINX proxy manager (container) for the reverse proxy.
DuckDNS (container)

all managed by Portainer.

I have created the host into NGINX of my duckdns subdomain , with lets encrypt. Http scheme. The proxy give me green light on the status.

My Linux server is connected to a Netgear Acces point. The acces point is connected (wan port) to the ISP router. NAT between Router and Access point and between Access point and Server is active on ports 80 443.

If I try to connect to my duckdns subdomain, I get error:
'A request from a reverse proxy was received from 172.17.0.5, but your HTTP integration is not set-up for reverse proxies ’

172.17.0.5 is the docker IP address of the proxy server, so I added to HA configuration file:
'http:
use_x_forwarded_for: true
trusted_proxies:
- 172.17.0.5 ’

Try to reconnect and :
‘Login attempt or request with invalid authentication from ISP router ip (192.168.X.X)’

I try to change the proxy host scheme to HTTPS or add the ISP router ip to the trusted proxies but didn’t work…

Any idea how to resolve …

Tks in advance.

Francesco

1 post - 1 participant

Read full topic

I’m trying to setup an automation that triggers when a tank has been refilled. Specifically, I want to trigger when:

From Below 60
To Above 75

However the only triggers that take into account the old state are things like state triggers that don’t use things like below and above.

I’ve tried toying with templates, but can’t find a way to use the old state to compare to the new state.

5 posts - 3 participants

Read full topic

Hi!

I’m guessing that the answer to my questions is “template sensor”, but I need some help in getting started…

I have a “dumb” dish washer mounted on a smart socket, allowing me to see power consumption etc in Home Assistant. I want to use this information to generate new sensors, making my dishwasher somewhat smarter. Based on power consumption data, I would like to have the following new sensors:

• One that count the number of cycles (to keep track of the number of cycles during a month)
• One that shows a status of the cycle (e.g. Inactive, Wash ongoing, Complete)
• One that shows elapsed time (e.g. 01:20 since going from “inactive” to “wash ongoing”)

Power consumption through a cycle would normally look like this:

I’m guessing the three highs are heating up water, and in between just circulating the water in the dish washer. My dish washer opens up automatically at the end, and it is possible that a fan is active in the end to try to dry up all the wash, hence the “End” should perhaps be at 02:05 instead of 01:20.

Similarly, I have a smart socket on my tumble dryer, where I would love to do the same. A cycle here would normally look like this:

Appreciate all help - as well as ideas or other tips related to this topic!

Best regards,
Pjotr (Norway)

1 post - 1 participant

Read full topic

Good morning all!

So I was unfortunately impacted by the “removing Z-wave devices for non-ready nodes” issue that was fixed in 12.10. For that patch, I want to say a huge thank you to those involved with fixing it as well as pushing out a patch and not making me wait until February.

Now to my question: when I was first presented with 50+ devices generically renamed to “GE Smart Switch” last week, I reverted to the last backup that didn’t exhibit this issue, which for me, was 2021.09.

Now that fixed the renaming issue, but ever since I restored from that 2021.09 backup onward, unfortunately seemed to have introduced a recurring instability into my Z-Wave network, which has persisted into my upgrade to 2021.12.10. The issue presents as a subset of devices that randomly “become unavailable” to Home Assistant whenever I try to interact with them. It is never the same device, and about 4-5 devices a day that do this. In the app, they usually show as “dead.”

About 75% of the time, if I immediately click “Re-Interview Device”, “Heal”, and then restart the Z-Wave JS service in Supervisor, the device will come back. The other 25% of the time, it won’t come back immediately but seems to fix itself overnight. Sometimes, I get a quick popup error message about “failed three times” that I have yet to be able to capture.

And here’s what it looks like in the Logbook.

So I guess I have a couple of questions.

1.) Where can I look in the logs to figure out what’s going on here?
2.) Is this a known problem, and what can I do to fix it?
3.) If it’s not known, does anyone have recommendations on a fix that doesn’t require me to factory-reset my entire Z-Wave network?

1 post - 1 participant

Read full topic

Is it possible to have multiple conditions within a trigger? Here’s my automation which turns off the bathroom light after 5 minutes of no motion.

  - id: 'bathroom_no_motion'
    alias: Bathroom No Motion
    trigger:
    - platform: state
      entity_id: sensor.bathroom_motion
      to: 'False'
      for:
        minutes: 5
    condition:
    - condition: state
      entity_id: light.bathroom_light
      state: 'on'
    action:
    - service: script.telegram_notification
      data:
        message: "No motion for 5 mins in the bathroom, so light switched off"
    - type: turn_off
      device_id: 5337e30db9d29e0eaecd3090e32cc37f
      entity_id: light.bathroom_light
      domain: light
    mode: single

I have an input boolean called “peak_time” which is set to on or off based on the time of day. If it’s “on” then I need to change the bathroom no motion timer to allow 15 minutes before switching off. I’ve looked at using a service_template, but not sure where to change the timer.

any ideas? Thanks!

1 post - 1 participant

Read full topic

In the developer tools → State I selected my climate.playroom and I get the settings below. I see hvac_modes, but I don’t see anywhere that the current mode is selected. I do see hvac_action, but this is only useful for my needs when the hvac is running, idle does me no good.

I’m pretty sure that what I need is there somehow, as the image below shows the current mode, even though the system is idle.

I have a few automations I want to create that requires me to know the current HVAC mode, but I don’t currently see how to get the current mode, given the data below that’s available.

My thermostats are imported using: Honeywell Total Connect Comfort (US) - Home Assistant

At one point in the past I was able to operation_mode

'{{ is_state_attr(''climate.master_bedroom'', ''operation_mode'', ''cool'') }} '

, but it appears that sometime after 12/20/2020 this attribute was removed.

Any assistance in getting at the current mode would be greatly appreciated.

hvac_modes:
  - 'off'
  - heat_cool
  - cool
  - heat
min_temp: 40
max_temp: 90
fan_modes:
  - 'on'
  - auto
preset_modes:
  - none
  - away
  - Hold
current_temperature: 73
temperature: 68
target_temp_high: null
target_temp_low: null
current_humidity: 128
fan_mode: auto
hvac_action: idle
preset_mode: null
aux_heat: 'off'
fan_action: idle
permanent_hold: false
dr_phase: -1
friendly_name: Playroom
supported_features: 91

1 post - 1 participant

Read full topic

Hello,

I have a state-switch custom card inside a grid card. The state-switch is functioning correctly outside the grid, but inside the grid, the second position don’t show the card. The state switch change the climate card between the thermostat and AC depending on a input_boolean value.

We can see three cards below. The state swicth, the toggle and the grid containing the same state switch card in the second column. I try swapping the columns. I tried swapping position of the on and off. I tried putting other card, like buttons. But the second state of the state switch (in this case ‘off’) always show nothing.

WinterTime = ‘on’

WinterTime = ‘off’

Code of the grid card:

type: grid
cards:
  - type: custom:lovelace-theweathernetworkcard
    entity: weather.saguenay
    entity_current_condition: sensor.cw_current_condition
    entity_humidity: sensor.cw_curr_humidity
    entity_temperature: sensor.cw_curr_temp
    entity_wind: sensor.cw_curr_wind
    entity_wind_gust: sensor.cw_curr_windg
    entity_wind_uom: sensor.cw_curr_wind_uom
    entity_feels_like: sensor.cw_curr_ftemp
    entity_condition_icon: sensor.cw_curr_cond_ico
    entity_temp_uom: sensor.cw_temp_uom
    entity_uv: sensor.cw_curr_uv_index
    entity_cond1: sensor.cw_ico_1
    entity_cond2: sensor.cw_ico_2
    entity_cond3: sensor.cw_ico_3
    entity_cond4: sensor.cw_ico_4
    entity_temp1: sensor.cw_temp_1
    entity_temp2: sensor.cw_temp_2
    entity_temp3: sensor.cw_temp_3
    entity_temp4: sensor.cw_temp_4
    entity_ftemp1: sensor.cw_ftemp_1
    entity_ftemp2: sensor.cw_ftemp_2
    entity_ftemp3: sensor.cw_ftemp_3
    entity_ftemp4: sensor.cw_ftemp_4
    entity_pop1: sensor.cw_pdp_1
    entity_pop2: sensor.cw_pdp_2
    entity_pop3: sensor.cw_pdp_3
    entity_pop4: sensor.cw_pdp_4
    entity_rain1: sensor.cw_rain_1
    entity_rain2: sensor.cw_rain_2
    entity_rain3: sensor.cw_rain_3
    entity_rain4: sensor.cw_rain_4
    entity_wdn1: sensor.cw_wdn_1
    entity_wdn2: sensor.cw_wdn_2
    entity_wdn3: sensor.cw_wdn_3
    entity_wdn4: sensor.cw_wdn_4
    entity_snow1: sensor.cw_snow_1
    entity_snow2: sensor.cw_snow_2
    entity_snow3: sensor.cw_snow_3
    entity_snow4: sensor.cw_snow_4
  - type: custom:state-switch
    entity: input_boolean.wintertime
    states:
      'on':
        type: custom:simple-thermostat
        entity: climate.living_room_thermostat
        layout:
          mode:
            names: false
            icons: true
            headings: false
          step: column
        control:
          hvac: true
        label:
          temperature: Now
          state: false
        decimals: '1'
        step_size: '0.5'
      'off':
        type: custom:simple-thermostat
        entity: climate.living_room_ac
        layout:
          mode:
            names: false
            icons: true
            headings: false
          step: column
        step_size: '1'
        decimals: '0'
        control:
          hvac:
            heat: false
            fan_only: false
            dry: false
columns: 2
square: false

Anyone knows how to solve this issue?

1 post - 1 participant

Read full topic

Hi everyone,

I am trying to get an Alexa integration via emulated_hue.

Version: Home Assistant Core (version | core-2021.12.8)
Hosting: Unraid - Docker
Network: Ubiquiti - with VLAN (but at the moment with open communication between all VLAN’s)

Hue Emulated Configuration:

host_ip: 192.168.X.X.  <-- my Home Assistant IP
listen_port: 80
expose_by_default: false
exposed_domains:
  - switch
entities:
  switch.on_off_plug_in_unit_3:
    name: Weihnachtsstern
    hidden: false

I can open the following URLs (Also over the same wireless network which Alexa (Echo) use) :
http://192.168.X.X/description.xml with the result:

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.X.X:80/</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>Home Assistant Bridge (192.168.X.X)</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>http://www.philips.com</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2015</modelName>
<modelNumber>BSB002</modelNumber>
<modelURL>http://www.meethue.com</modelURL>
<serialNumber>001788FFFEXXXXXX</serialNumber>
<UDN>uuid:2f402f80-da50-11e1-XXXX-XXXXXXXX</UDN>
</device>
</root>

http://192.168.XX.XX/api/pi/lights with the result:

{"1": {"state": {"on": false, "reachable": true, "mode": "homeautomation"}, "name": "Weihnachtsstern", "uniqueid": "00:02:65:d0:aa:6a:XX:XX-XX", "manufacturername": "Home Assistant", "swversion": "123", "type": "On/Off light", "productname": "On/Off light", "modelid": "HASS321"}}

To me, it looks like emulated hue is configured correctly.
Unfortunately, when I search for a new Hue gateway or light via Alex, no device is found.

Of course, I used the search before but did not find a solution. Does anyone have an idea or a tip for me?

Cheers,
Danny

1 post - 1 participant

Read full topic

Hi,

I’m using pyhydroquebec and my electricity company reset the TOTAL consumption every billing period (about 60 days).

How should I configure HA to reset the stats when the new period starts ?

Now the stats are all wrong because HA thinks that I consume -1500kWh last night… since the sensor went from 1500kWh to 0kWh overnight…

Any ideas ?

1 post - 1 participant

Read full topic

I’ve hooked up a LJ18A3-8-Z/BX-5v to a Sonoff Basis R2 running Tasmota. I’ve set the initial count value with the value of my watermeter, so Tasmota will report my actual meter reading. I would like to create a sensor that’ll show me my hourly water usage but with the utilitymeter integration my hourly usage is an hourly representation of my total daily usage. I would like to have a graph showing me that I’ve used x liter at a time, then severaly hours without usage, then x liters, etc. etc.

this is from my utilitymeter.yaml

waterverbruik_per_uur:
  source: sensor.watermeter_counter_c1
  name: Waterverbruik (per uur)
  cycle: hourly
waterverbruik_dagelijks:
  source: sensor.watermeter_counter_c1
  name: Waterverbruik (dagelijks)
  cycle: daily
waterverbruik_wekelijks:
  source: sensor.watermeter_counter_c1
  name: Waterverbruik (wekelijks)
  cycle: weekly
waterverbruik_maandelijks:
  source: sensor.watermeter_counter_c1
  name: Waterverbruik (maandelijks)
  cycle: monthly

It’ll show me these values and graphs.

I also have the same issue with my gas and electricity graphs.

2 posts - 1 participant

Read full topic

I have an EcoSmart 4 button remote setup with an automation but when I click the trigger button HA just fires off a warning about invalid config.

I also tried these two blue prints with the same result

Error in HA notifications

The logs just show what looks like a snippet of my configuration.yaml

Logger: homeassistant.config
Source: config.py:464
First occurred: 07:59:47 (5 occurrences)
Last logged: 08:06:51

Invalid config for [automation]: Invalid trigger configuration. Got OrderedDict([('logger', {}), ('lock', {}), ('my', {}), ('cloud', {}), ('sun', {}), ('input_datetime', {}), ('ssdp', {}), ('input_boolean', {}), ('person', {}), ('config', {}), ('history', {}), ('updater', {}), ('zeroconf', {}), ('system_health', {}), ('mobile_app', {}), ('zha_toolkit', {}), ('remote_syslog', {}), ('zha', OrderedDict([('custom_quirks_path', '/config/custom_zha_quirks/'), ('zigpy_config', OrderedDict([('ota', OrderedDict([('ikea_provider', True), ('ledvance_provider', True), ('.... (See /config/configuration.yaml, line 212).
Invalid config for [automation]: Invalid trigger configuration. Got OrderedDict([('logger', OrderedDict([('default', 'critical'), ('logs', OrderedDict([('homeassistant.core', 'fatal'), ('homeassistant.components.mqtt', 'error'), ('homeassistant.components.recorder', 'error'), ('homeassistant.components.influxdb', 'error'), ('homeassistant.components.zha', 'debug'), ('bellows.zigbee.application', 'debug'), ('bellows.ezsp', 'debug'), ('zigpy', 'debug'), ('zigpy_deconz.zigbee.application', 'debug'), ('zigpy_deconz.api', 'debug'), ('zigpy_xbee.zigbee.application'.... (See /config/configuration.yaml, line 212).

The Device shows battery percent etc

Here is the automation

alias: EcoSmart Test
description: ''
trigger:
  - event_data:
      command: 'on'
      device_ieee: cc:cc:cc:ff:fe:c2:cd:f3
    event_type: zha_event
    platform: event
  - event_data:
      command: 'off'
      device_ieee: cc:cc:cc:ff:fe:c2:cd:f3
    event_type: zha_event
    platform: event
condition: []
action:
  - service: light.turn_on
    target:
      device_id: 3ad03785f227934004b33cff89ba7dde
mode: single

Any insight or help is greatly appreciated

1 post - 1 participant

Read full topic

Please be kind, I’m very much a noob with programming and such so the learning curve is steep (if not vertical ).

My goal is to use the window_open_external in a Popp 701721 TRV with a Tuya TS0203 door/window sensor. I’ve managed to achieve turning the TRV down/off and on again with the use of a automation based on a blueprint, but it’s probably more elegant to use the window_open_external option.

My thought was to make a template switch in HA, and to use that in the TRV by adding the following to my configuration.yaml.

switch:
  - platform: template
    switches:
      raam_kantoor:
        value_template: "{{ is_state('binary_sensor.raam_kantoor_contact', 'on') }}"
        turn_on:
          service: switch.turn_on
          target:
            entity_id: switch.trv_kantoor_window_open_external
        turn_off:
          service: switch.turn_off
          target:
            entity_id: switch.trv_kantoor_window_open_external

The switch (switch.raam_kantoor) itself is working when I open the window, but switch.trv_kantoor_window_open_external is not responding. If I try to add switch.raam_kantoor to the config of the TRV (under devices) I get the following error:
Entity with this ID is already registered.

Am I thinking in the right direction, or should this be done with Zigbee2MQTT? Could anyone give some pointers?

My system:
HA version 2021.12.10 in a docker on a RPI4
Zigbee2MQTT version 1.22.2 in a docker
Coordinator type zStack3x0 (CC2652RB slae.sh)
Coordinator revision 20211217

1 post - 1 participant

Read full topic

Hi there

I just finished setting this up and it’s working great, but I’m having an issue with my av receiver which is driving me crazy since months. It’s not an issue directly related to HA, but it’s impacting the functionality of an integration so I’d like to know if somebody of you had a similar experience and how you guys fixed it.

Basically what I’ve done is this:

• Setup the Plex assistant and Plex integration
• Setup IFTTT to configure the Google commands
• When I try to say something like “Hey google, play this on plex”, TV turns on, the episode starts and then the AV receiver switch the source to TV instead of the Chromecast source (the HDMI where the Chromecast is plugged into). This is an extremely annoying issue since I have to use then the remote to switch the AV to the right source.
  Does anybody have any idea how I can fix this? Once again, I know this isn’t HA related so if I have to delete this post, I will, but I really hope somebody can help out

1 post - 1 participant

Read full topic