Installed the Portainer add-on.
Shows only two containers that I set up, but where are the others that are/must be running given that I am using the core lovelace f/e?

Capture1920×900 89.6 KB

Here is a list of running containers :-

daz@Pi:~ $ docker ps --all
CONTAINER ID        IMAGE                                              COMMAND                  CREATED             STATUS              PORTS                                                                    NAMES
b43f28d7e528        hassioaddons/portainer-armv7:1.3.0                 "/init"                  12 minutes ago      Up 12 minutes                                                                                addon_a0d7b954_portainer
44029428159f        gpbenton/engmqttclient:1.0.0                       "/opt/energenie_mqtt…"   3 hours ago         Up 3 hours                                                                                   energenie_mqtt_client
bfb6ff71228c        eclipse-mosquitto                                  "/docker-entrypoint.…"   3 hours ago         Up 3 hours          0.0.0.0:1883->1883/tcp, 0.0.0.0:8883->8883/tcp, 0.0.0.0:9001->9001/tcp   mosquitto
c989f2ef25e9        homeassistant/armv7-addon-ssh:8.10.0               "/init"                  11 hours ago        Up 11 hours                                                                                  addon_core_ssh
830a4266ed05        homeassistant/armv7-addon-configurator:5.2.0       "/init"                  11 hours ago        Up 11 hours                                                                                  addon_core_configurator
ec0367ef00a6        hassioaddons/log-viewer-armv7:0.9.1                "/init"                  11 hours ago        Up 11 hours                                                                                  addon_a0d7b954_logviewer
5a926933c439        homeassistant/raspberrypi3-homeassistant:0.118.4   "/init"                  11 hours ago        Up 2 hours                                                                                   homeassistant
025f25a7fbbf        homeassistant/armv7-hassio-multicast:3             "/init"                  12 hours ago        Up 12 hours                                                                                  hassio_multicast
d0f5f5a3bbdc        homeassistant/armv7-hassio-observer:2020.10.1      "/init"                  12 hours ago        Up 12 hours         0.0.0.0:4357->80/tcp                                                     hassio_observer
160ed4f55ea8        homeassistant/armv7-hassio-cli:2020.10.1           "/init /bin/bash -c …"   12 hours ago        Up 12 hours                                                                                  hassio_cli
2fe8895ad2ba        homeassistant/armv7-hassio-audio:17                "/init"                  12 hours ago        Up 12 hours                                                                                  hassio_audio
243f1478f361        homeassistant/armv7-hassio-dns:2020.11.0           "/init"                  12 hours ago        Up 12 hours                                                                                  hassio_dns
60bd9c9865c2        homeassistant/armv7-hassio-supervisor              "/init"                  12 hours ago        Up 11 hours                                                                                  hassio_supervisor
daz@Pi:~ $

2 posts - 2 participants

Read full topic

I got home assistant connect connect to google home via google_assistant and got the following switches configured.

switch.tv_power_on:
      name: TV Power
      aliases:
        - tv
        - television
      room: Living Room
switch.tv_mute:
      name: TV Mute
      aliases:
        - 'mute tv'
      room: Living Room
light.lounge_dimmer_20:
      name: Lounge Light
      aliases:
        - lounge light
        - tv light

when I ask google to turn off the TV by " ok google turn off the tv", google try to turn off all the switches, I have a feeling google try to search tv keyword out of all the switch names and aliases, is there is a way to avoid that?

1 post - 1 participant

Read full topic

Hello! Still relatively new to all of this, so the plating is something I haven’t really understood yet. I’m trying to set up some input booleans that reset to an “off” state after an “on” trigger, and a period of a few seconds. Ideally I could set up a suffix like _r to the entity name and use that glob for the automation trigger. So thinking out loud, here’s what I want it to do:

id: boolean_reset
alias: Input boolean reset after 5 seconds
description: ''
trigger:
  - platform: state
    entity_id: input_boolean.*_r
    to: 'on'
condition: []
action:
  - delay: '5'
  - service: input_boolean.turn_off
    data: {}
    entity_id: { TRIGGERING ENTITY }
mode: single

As you can see above, I have no idea how to actually reference the input boolean that triggered the automation.

What’s the best way to do this?

If you’re wondering what my use case is:
I use HomeKit and have Apple HomePods throughout the house. It’s possible using HomeKit to activate specific music via automation but it’s a little dumb how you have to do it—in that you have to call a specific album, playlist, etc. So I wanted to be able to set up album or playlist specific input booleans, to then trigger a HomeKit automation to play it.

9 posts - 3 participants

Read full topic

Hi,

I’m using the myenedis integration from HACS in order to replace the Linky integration. With this, I have a sensor with all the different informations like before.

I want to get the daily value using the utility meter in order to have the values for each day (and put everything in a graph) using recorder.

I managed to make the sensor template and for me it works since I have the value in the dev tools:

- platform: template
  sensors:
    daily_power_enedis:
      friendly_name: "Conso journalière Enedis"
      unit_of_measurement: 'kWh'
      value_template: "{{ (state_attr('sensor.myenedis_14851953566977', 'day_1') /1000) | float | round(2)}}"

Now I’m trying to use this sensor in the utility meter :

daily_power_enedis:
  source: sensor.daily_power_enedis
  cycle: daily
  tariffs:
    - peak

The value of the sensor that I’m using are:

attribution: ''
lastSynchro: '2020-12-02T13:59:27.405220'
lastUpdate: '2020-12-02T13:59:27.405211'
timeLastCall: '2020-12-02T13:59:27.405077'
yesterday: 17684
last_week: 113305
day_1: 17684
...

When launching everything, here is the error that I have:

Error adding entities for domain sensor with platform utility_meter
Error while setting up utility_meter platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 530, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/usr/src/homeassistant/homeassistant/components/utility_meter/sensor.py", line 264, in async_added_to_hass
    self._state = Decimal(state.state)
decimal.InvalidOperation: [<class 'decimal.ConversionSyntax'>]

I’m not sure how I can check if the value is a decimal, since in the dev tools I can see that the operation works since I have the correct values.

Anyone can help me out?
Thanks all!

1 post - 1 participant

Read full topic

Summary:

I do not understand how and where the native and HACS-installed (ShellyForHASS) interact.

Background

I was planning to motorize my roller shitters and bought a few months ago, in advance, several Shelly 2.5 devices. I did not have the motorization at that time yet so I set them up “in the void”: I integrated them to my HA (apparently via the HACS-installed integration (see later why this matters)) and measured whether there was appropriate tension on appropriate PINs when “moving the shutters”. It worked and the shellies were left along awaiting for the motorization.

The motorization came and the shellies worked as expected for two or three weeks. I then upgraded their firmware and HACS warned me that I have new versions of some integrations (which, I think, included ShellyForHACS) and I started to see in the logs an error.

I opened a GitHub Issue for the native shelly integration (because I forgot that I used ShellyForHASS) and was told that the issue is with ShellyForHACS (and then @thecode kindly told me how to switch to the native integration).

What I did and what I do not understand

So I uninstalled the ShellyForHACS integration, which was visible in the integration panel as

I rebooted HA. There was no more ShellyForHASS integration in the HASS integration window.

I then added the (what I assume to be) the native shelly integration. To my surprise, the logo on the integration page is still the same. The options for that integration are also the same as before (the ones I had with ShellyForHASS). This is a bit surprising.

The integration found my devices, with generic names. Unfortunately, I started to get another error, this time specifically from the native integration:

2020-12-02 09:26:23 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry shelly for shelly
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 236, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 64, in async_setup_entry
    ip_address = await hass.async_add_executor_job(gethostbyname, entry.data[CONF_HOST])
KeyError: 'host'

Crap, I told myself in French and, on a whim, I just reinstalled via HACS the ShellyForHASS integration from HACS (just installed it, nothing more) and the error above is gone (the one from the GitHub Issue is not there either - which is kind of understandable as I do not use it per se).

My questions

• should the integration logos on the integration page for the native integration and ShellyForHASS be the same?
• is there some kind of relationship between the two integrations above?
• if ShellyForHASS is installed, should I see two possible integrations for shelly on the integration page?

As of now the shutters work fine so this is more to understand the integrations than to fix a specific problem.

1 post - 1 participant

Read full topic

Hi All

Hope there is someone out there to help me with this problem :

1º - My automations dissapear from the UI and i don’t understand why. (but it´s not a big deal since we can create them directly in the yaml)

2º - If i create a fresh automation in UI and save it i get an error in some lines and other times the error below automation :

This is the automation

• id: ‘1606927027961’
  alias: Sunset
  description: ‘’
  trigger:
  • platform: sun
    event: sunset
    condition: []
    action:
  • service: switch.turn_on
    data: {}
    entity_id: switch.sonoff_10002e4fc4
    mode: single

and this is the error HA gives me

extra keys not allowed @ data[‘automation’]

and for what i can see in this error i have extra characters in the configuration.yaml, but when i check everything is okay, i even got compared with other configuration file and it´s the same amount of spaces and characters, the configuraton.yaml is this :

homeassistant:
customize: !include customize.yaml
automation: !include automations.yaml

Can someone help me whit this because i cant see anymore errors on this.

Thanks all.

1 post - 1 participant

Read full topic

Simple question, but finding an answer is hard. Is it somehow possible to register the pressing of a light switch button of a Lovelace card in Node-RED?

I want to register explicitly the pressing of the light button, not just changing of the state. Is that somehow possible? I could of course create an switch with the entity node and put that in Lovelace, but that would remove the ability to change brightness and color and is far too much work, I am afraid.

1 post - 1 participant

Read full topic

Hi all,

I am new here, but been using home assistant for the last couple of months after migrating from OpenHAB. So far I think it is great, but am struggling with my most recent configuration, I wonder if anyone can shed some light on the correct way to progress. Just point me in the right direction, because i believe i might be barking up the wrong tree.

I have a service that pushes data to a webhook (brewfather). From this I have been successful in triggering an automation and passing the payload to that automation (just a notification)

- alias: Capture Ispindel from Brewfather
  trigger: 
  - platform: webhook
    webhook_id: brewfather
  action:
    service: notify.mobile_app_pixel_2
    data:
      message: '{{trigger.json}}'

This passes the raw payload JSON, just so i know i can get at it and the webhook is working.

The JSON contains the following data items:

id:
type:
time:
temp:
sg:
angle:
battery:
rssi:

What ideally want to be able to do is set up a bunch of sensors (or a entity) that I can use to replay this data onto the dashboards (and ultimately log in grafana).

I can’t find how to setup custom sensors or entities in home assistant so i can pass the JSON payload to set their values.

I have trawled through the docs and forums and it looks like templates are the way to go, but it seems that can only be used to map one sensor to another.

What am I missing here?

Cheers in advance.

Mat

1 post - 1 participant

Read full topic

Hey Everyone, I have a question about connecting a device to HA via ESPHome. Currently, I have a MiFlora plant sensor that is connected to my rpi with HA and I have a few ESP32’s around the house for some other sensors. The MiFlora sensor is going to be used out of range from where my rpi is located. Right now, the MiFlora is connected and working.

Here is my code in the configuration.yaml:

sensor:
  - platform: miflora
    mac: 'C4:7C:8D:63:E3:E4'
    name: plant_1
    force_update: true
    median: 3
    go_unavailable_timeout: 43200
    monitored_conditions:
      - moisture
      - light
      - temperature
      - conductivity
      - battery

and

plant:
  plant_1:
    sensors:
      moisture: sensor.plant_1_moisture
      battery: sensor.plant_1_battery
      temperature: sensor.plant_1_temperature
      conductivity: sensor.plant_1_conductivity
      brightness: sensor.plant_1_light
    min_moisture: 15
    max_moisture: 60
    min_battery: 15
    min_temperature: 5
    max_temperature: 35
    min_conductivity: 350
    max_conductivity: 2000
    min_brightness: 3000
    max_brightness: 70000

What I want to know is what do I need to do to connect it to one of the ESP32’s? Do I need to copy the sensor portion of the code to the ESPHome configuration or all of the code? I had originally set it up in ESPHome but I didn’t get any information from it. It was all ‘unknown’.

I thank you in advance for your time and help!

1 post - 1 participant

Read full topic

Using docker, a config default is being created because I have a shared config that is mapped into images via volumes, either my own - or a pull of homeassistant/raspberryPi3-homeassistant . Just one example:

version: '3'
services:
  homeassistant:
    container_name: homeassistant
    image: homeassistant/raspberrypi3-homeassistant:stable
    volumes:
      - /home/ha/HOMEASSISTANT/HASS/CONFIG:/config
    environment:
      - TZ=Europe/London
    restart: always
    network_mode: host
    devices:
      - /dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0
    privileged: true

Just testing various images, and using a a config link:
/home/ha/HOMEASSISTANT/HASS/CONFIG

On my raspbian (linux) box this a symlink to different directories depending on what I’m testing. HA isn’t following symlinks and thinks the config is missing. If I create the CONFIG dir above as a “normal” dir, then all is well.

??

1 post - 1 participant

Read full topic

I have posted this similar problem earlier this year and have yet to find a solution. No matter by which means I try to stop HA server it almost always does a restart. I have used the web interface config/server_control/sop option as well as command ha core stop . I may have to repeat this 5-10 times before the server actually stops.

I can’t be the only person having this problem, am I?

1 post - 1 participant

Read full topic

Hi,

All of a sudden this evening, if I try to install anything from the Addon Store, I get an error “Failed to install addon, Unknown error, see supervisor”. This is a fresh install of HA completed yesterday. Everything is new, pretty much up to date.

Can anyone help me with this ?

ha11311×621 83.1 KB

1 post - 1 participant

Read full topic

I’ve only recently discovered history_stats and I’ve started going bonkers on using it in conjunction with the Harmony remote integration to get stats on gaming/TV time used. The problem is, I’m ending up with loads of repetition which is starting to look a bit unmanageable. For instance, I have this at the moment for the last 24h use:

  - platform: history_stats
    name: Gaming time 24h - Xbox
    entity_id: sensor.harmony_remote_lounge
    state: 'Xbox Series X'
    type: time
    duration: 24h
    end: '{{ now() }}'
    
  - platform: history_stats
    name: Gaming time 24h - PS5
    entity_id: sensor.harmony_remote_lounge
    state: 'PS5'
    duration: 24h
    end: '{{ now() }}'
    
  - platform: history_stats
    name: Gaming time 24h - Switch (docked)
    entity_id: sensor.harmony_remote_lounge
    state: 'Switch'
    type: time
    duration: 24h
    end: '{{ now() }}'
    
  - platform: history_stats
    name: TV time 24h - Netflix
    entity_id: sensor.harmony_remote_lounge
    state: 'Netflix'
    type: time
    duration: 24h
    end: '{{ now() }}'
    
  - platform: history_stats
    name: TV time 24h - Sky
    entity_id: sensor.harmony_remote_lounge
    state: 'Sky Q'
    type: time
    duration: 24h
    end: '{{ now() }}'

… and I’d like to do the same thing for a week duration, and maybe month, which is going to result in a massive load of text which is mostly all the same lines. Is there any way to reduce some of that duplication and bloat?

I was hoping I’d be able to do something like this:

  - platform: history_stats
    type: time
    duration: 24h
    end: '{{ now() }}'
    entities:

      - entity_id: sensor.harmony_remote_lounge
        name: Gaming time 24h - Xbox
        state: 'Xbox Series X'
    
      - entity_id: sensor.harmony_remote_lounge
        name: Gaming time 24h - PS5
        state: 'PS5'
    
      - entity_id: sensor.harmony_remote_lounge
        name: Gaming time 24h - Switch (docked)
        state: 'Switch'
    
      - entity_id: sensor.harmony_remote_lounge
        name: TV time 24h - Netflix
        state: 'Netflix'
    
      - entity_id: sensor.harmony_remote_lounge
        name: TV time 24h - Sky
        state: 'Sky Q'

… but I see that’s not valid. Are there any other options to do the same thing with less lines & repetition?

1 post - 1 participant

Read full topic

I have a total of 25 Shelly switches installed including Shelly 1s, Shelly 1PMs, Shelly 2s and Shelly 2.5s and recently added the native Shelly integration to my 0.118.4 HASS system to support them. I’ve been able to add all 1, 1PM and 2 switches however, none of the Shelly 2.5s are recognized. And, when I attempt to add them the message Failed to connect is returned after about 10 seconds of trying to connect. All of my 2.5s are running the latest 1.9.2 firmware.

Are there any suggestions on where to look to troubleshoot this to get them added?

1 post - 1 participant

Read full topic

Hi,

I’ve setup my stream devices and google assistant, everything works great. I’ve followed that document: Google Cast BlueIris Cameras with Home Assistant!

Now, when I ask Google to show me the camera, I get a Not connected error about Nabu Casa. I would like to be able to stream without Nabu Casa. Is that possible with Home Assistant?

Thanks

4 posts - 3 participants

Read full topic

In this simple card, the state_color: true does not have any effect at all.

The code is:

- type: button
    entity: sensor.av_pa
    show_name: false
    show_state: true
    icon: 'mdi:power'
    icon_height: 70px
    state_color: true
    tap_action:
      action: call-service
      service: climate.turn_on
      service_data:
        entity_id: climate.thermostat_5

How can I make the state_color attribute work (please, no card_mod)?

1 post - 1 participant

Read full topic

Hi,

I just wounder fick the are someway to get my g2h to work on SmartThings. I Will like to se camera streams on samsung tv.

Pekade help

1 post - 1 participant

Read full topic

Hi all,

I am using the Zigbee2MQTT add-on and I have roughly a dozen devices that I have running. They work fine. I am running version 1.15.
My problem now is that I can’t pair new devices. I am trying a Tradfri on/off switch without any luck. I have tried a Xiaomi door & window sensor with no luck and the same for a Xiaomi temperature and humidity sensor. Here is my config, I am lost to be honest (I haven’t tried pairing in a year or so and I updated, so not sure if it is related):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://homeassistant:1883'
  user: mqttuser
  password: pw
serial:
  port: /dev/ttyACM0
  disable_led: true
advanced:
  log_level: info
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

I someone seeing the problem in the config potentially?

1 post - 1 participant

Read full topic

Hi people,
my Z-Wave is very slow, it took 3-6 to the switch turn on/off after I change the stare of the switch in the GUI, showtimes it’s even stuck and do nothing( for example when I turn on the light , the indicator move to on mode and after few second move back to off mode).
I tried to “heal” the network but without any success.
my HA(hassio) run on RPI 3 with zwave stick and all my nodes are from Fibaro (roller shutter 2,double switch 2) .
LOG
Thank you

1 post - 1 participant

Read full topic

hi all,

I’ve looked through the posts on here and found several on how to do just what I am looking for… however, when I tried it with the below script and then activate it, it turns its self off within 3 seconds and I hear nothing… any help on where i may be going wrong please?

my script is as follows

alias: play radio on sonos
sequence:
- service: media_player.volume_set
  data:
    entity_id: media_player.office_sonos
    volume_level: '0.5'
- service: media_player.play_media
  entity_id: media_player.office_sonos
  data:
    media_content_id: https://listen-pureradio.sharp-stream.com/pure_radio.mp3
    media_content_type: 'audio/mp4'

thank you for your time and help.

2 posts - 2 participants

Read full topic