@Mariusthvdb wrote:

using a set of fold-entity-rows with embedded markdown cards, I like to set the border to none, and shift the content to the normal margin of the regular entities card. With fold-entity-row we can do the latter using padding: 0, but I can’t get rid of the error in inspector, when I set:

# /include_alias_activities.yaml
type: custom:hui-element
card_type: markdown
style: |
  ha-card {
    box-shadow: none;
    }

content: |
etcetc

the containing card of the markdown is:

type: entities
entities:

  - type: custom:hui-element
    card_type: entities

    entities:
      - type: custom:fold-entity-row
        head:
          type: section
          label: Activities
        padding: 0
        entities:
          - !include /config/lovelace/includes/include_alias_activities.yaml
          - !include etc etc
          - !include etc

the view is alright, and the markdown are placed perfectly. Is just that I keep seeing this:

Schermafbeelding 2020-05-14 om 13.07.281420×258 44.4 KB

Anyone managed to do so?
Should I style the fold-entity-row, and if yes, how? Ive tried the same style, but it isn’t a ha-card so the wont work.

Using custom:hui-markdown-card instead of the new custom:hui-element, card_type: markdown doesn’t error, but often causes the markdown not to load because if non-existing…
what to do?

Posts: 1

Participants: 1

Read full topic

@MartyMcFly wrote:

Hi I have successfully setup my garage door opener using card code provided in another thread - including status icon. But I cannot find what I am doing wrong below - when I click on the icon - the garage is opening. But when I click again - it is not closing the door…what am I missing here?

entity: binary_sensor.sonoff_ABCDE
icon: 'hass:garage'
show_icon: true
show_name: false
state:
  - color: 'rgb(255,0,0)'
    icon: 'hass:garage-open'
    value: 'on'
  - color: 'rgb(68,115,159)'
    type: ''
    value: 'off'
tap_action:
  action: call-service
  service: switch.turn_on
  service_data:
    entity_id: switch.sonoff_ABCDE
type: 'custom:button-card'

Posts: 2

Participants: 2

Read full topic

@heisenberg wrote:

I am using zigbee2mqtt and Mosquitto broker in hassio (HassOS 3.13) and I am having an issue with zigbee devices, because every time I remove one device from Home Assistant (using topic zigbee2mqtt/bridge/config/force_remove) then when I add the device again, zigbee2mqtt recognise it (I can see the message {"type":"pairing","message":"interview_successful","meta":{"friendly_name":"xxxxxxxxxxxx","model":"xxxxxxxx","vendor":"xxxxxx","description":"xxxxxxxxx","supported":true}}) and I can see the messages sent by the device in the zigbee2mqtt log (so pairing is successful), but Home Assistant doesn’t create an entry in the Entities or Devices list for the device.

I already checked the option “Enable newly added entities” is enable within MQTT system options, so I don’t understand why the device is not added to the devices/entities list, is anyone having the same issue? is there any log where I can see why MQTT is not adding the device properly?

Posts: 1

Participants: 1

Read full topic

@mole4food wrote:

Hi,

I’ve been printing with my Ender3 for almost 2 years now and have had a lot of fun with it.
However recently the system falls into error mode every now and than, due to “Thermal Runaway”.

As the machine cuts all power to the hot parts due to the firmware, it also goes into a very annoying “beep” sound that doesn’t stop, only if you kill the power.

I’ve added a Sonoff (w/ Tasmota) in front of the power supply and have a RPi running octopi with MQTT providing me with data and control of the printer.

Today the thermal runaway happend again and I’ve checked my MQTT logs, where I found this:

Topic:
octoPrint/event/Error
Payload:
{"_timestamp": 1589456843, "reason": "firmware", "_event": "Error", "error": "Thermal Runaway, system stopped! Heater_ID: 0 - Printer halted. kill() called!"}

As this message is pushed directly as soon as the system gets into “error” mode I would like to use this to automatically turn of the powersupply.

Currently I’ve got this in my automation.yaml:

- alias: Kill printer on Thermal runaway
  trigger:
  - platform: mqtt
    topic: octoPrint/event/Error
  condition:
    condition: template
    payload_template: "{{ trigger.payload_json['error'] == Thermal Runaway, system stopped! Heater_ID: 0 - Printer halted. kill() called!"}}"  
  action:
  - service: switch.turn_off
    entity_id: switch.stroom_ender3

But this doesn’t work.
Could you maybe help me understand how I should address the "payload_template"?

Thanks in advance!
Guy

Posts: 1

Participants: 1

Read full topic

@alteredstate wrote:

Hello everyone!

Currently on:

~ $ ha info
arch: aarch64
channel: stable
hassos: "3.13"
homeassistant: 0.109.6
hostname: hassio
logging: info
machine: raspberrypi3-64
supervisor: "222"
supported_arch:
- aarch64
- armv7
- armhf

and I have a Z-Wave node that stopped working so I removed the physical node but it still shows up as Ready:

image1157×677 57.9 KB

Just to show that the node is indeed gone I went to Z-Wave Node Management, selected the node and clicked: Test Node. The log shows this operation timed out (because the node does not exist anymore):

2020-05-14 08:34:47.871 Info, Node020, NoOperation::Set - Routing=true
2020-05-14 08:34:47.872 Detail, Node020, Queuing (NoOp) NoOperation_Set (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x00, 0x00, 0x25, 0xe2, 0x34
2020-05-14 08:34:47.872 Detail,
2020-05-14 08:34:47.872 Info, Node020, Sending (NoOp) message (Callback ID=0xe2, Expected Reply=0x13) - NoOperation_Set (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x00, 0x00, 0x25, 0xe2, 0x34
2020-05-14 08:34:57.874 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-05-14 08:34:57.874 Detail, Node020, Removing current message
2020-05-14 08:34:57.874 Detail, Node020, Notification: Notification - TimeOut

I’m also trying to remove the node by selecting the node under: Developer Tools --> STATES and setting the: State attributes (YAML, optional) to: is_failed: true

image383×749 26.3 KB

Then back to Z-Wave Node Management, select the node and click REMOVE FAILED NODE

image975×431 23.2 KB

It does not appear this is working because I see this error in the logs:

2020-05-14 08:49:21.612 Detail, Node020, Queuing (Controller) Remove Failed Node
2020-05-14 08:49:21.613 Info, ControllerCommand_RemoveFailedNode
2020-05-14 08:49:21.613 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x14, 0xe4, 0x6b
2020-05-14 08:49:21.613 Detail, Notification: ControllerCommand - Starting
2020-05-14 08:49:21.615 Detail,
2020-05-14 08:49:21.615 Info, contrlr, Sending (Command) message (Callback ID=0xe4, Expected Reply=0x61) - ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x14, 0xe4, 0x6b
2020-05-14 08:49:22.615 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-05-14 08:49:22.615 Detail, contrlr, Removing current message
2020-05-14 08:49:22.616 Detail, contrlr, Notification: Notification - TimeOut
2020-05-14 08:49:22.622 Detail, Notification: ControllerCommand - Error - Failed

Would anyone know what’s going on and how to correct this? Also, why does the node show up as Ready when it is clearly not even physically present and has long since been buried in a landfill?

Posts: 4

Participants: 2

Read full topic

@Giuseppe-P wrote:

How is it possible that Home Assistant does not have a simple integration with alexa without cloud HA

Posts: 4

Participants: 2

Read full topic

@CNCman wrote:

Hi !

I have hass.io running under docker on Raspbian, and need to install self-signed SSL certificate.
This manual is somewhat ambigous, its not completely clear where to copy certificate files (hass.io and docker listed as separate options).
https://www.home-assistant.io/docs/ecosystem/certificates/tls_self_signed_certificate/

Is this
raspbian host -> /etc/ssl
or
raspbian host -> /usr/share/hassio/home_assistant/ssl
or
docker container -> /etc/ssl

Thanks in advance for any help.

Posts: 1

Participants: 1

Read full topic

@jaymu wrote:

I’ve created a button that, when pressed, executes a command (remote via ssh). I wanted it to be a one-time switch, so when pressed, immediately returning to the off state. What I’ve done is the following:

Create a switch in configuration.yaml:

- platform: command_line
  switches:
    kodi_reboot:
      command_on: ssh -i /config/ssh/id_rsa <IP Address> "systemctl restart kodi"

Then in scripts.yaml:

reboot_button:
  alias: Reboot Kodi
  sequence:
    - service: homeassistant.turn_on
      entity_id: switch.kodi_reboot
    - delay: 00:00:01
    - service: homeassistant.turn_off 
      entity_id: switch.kodi_reboot

And finally in ui-lovelace.yaml:

- type: "custom:button-card"
          entity: script.reboot_button
          name: Reboot Kodi
          icon: mdi:kodi
          tap_action:
            action: call-service
            service: script.turn_on
            service_data:
              entity_id: script.reboot_button

It work, but I can’t believe that this is the most efficient way to build such a button. Are there any shortcuts or better ways to this solution?

Posts: 2

Participants: 2

Read full topic

@Mariusthvdb wrote:

read this disturbing issue at custom-ui https://github.com/andrey-git/home-assistant-custom-ui/issues/184 that HA 110 drops custom-ui option for icon_color…

anyone here on 110, using custom-ui can confirm that?

this would be a major showstopper/breaking change…
@DavidFW1960 , do you see this too? (sorry for the tag, but you’re the only person I am positive about is using ha 110 dev?)

Posts: 3

Participants: 2

Read full topic

@Myztillx wrote:

Does anyone know if you have to have the InfluxDB component set up to use the InfluxDB sensor?

I have data from another source going into an external (from Home Assistant) InfluxDB and want to extract it as a sensor, but don’t really want all of Home Assistant data in my InfluxDB as well.

I get the following error in the log:

2020-05-14 09:50:41 ERROR (MainThread) [homeassistant.setup] Error during setup of component influxdb
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 175, in _async_setup_component
    component.setup, hass, processed_config  # type: ignore
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/influxdb/__init__.py", line 123, in setup
    conf = config[DOMAIN]
KeyError: 'influxdb'

With the below sensor configuration:

platform: influxdb
host: 192.168.2.205
port: 8086
username: !secret influxdb_username
password: !secret influxdb_password
queries:
  - name: Energy Consumption
    unit_of_measurement: kWh
    measurement: '"autogen.rtlamr"'
    where: '"endpoint_id" = ''12345678'''
    database: rtlamr
    group_function: last
    field: consumption

And the query I am trying to imitate is (from Grafana):

SELECT last("consumption")  FROM "autogen"."rtlamr" WHERE ("endpoint_id" = '12345678') AND $timeFilter GROUP BY time($__interval) fill(null)

Posts: 3

Participants: 2

Read full topic

@tasslehawf wrote:

There are currently 6 detected integrations. I disabled the original one because the permission popup kept popping up on the TV even after I clicked to give it permission (multiple times).

Posts: 1

Participants: 1

Read full topic

@dimagoltsman wrote:

A remote control card that can be used with any service!
broadlink, adb server, harmony or anything you want.

image198×794 31.7 KB

Posts: 1

Participants: 1

Read full topic

@cree8 wrote:

I have been searching for the supported light effects for these bulbs to no avail. Looks like there use to be an Osram gateway but that service is being winded down due to sale of the product, and LEDVANCE was created. I am trying to implement the color loop (or any other) effect, but nothing seems to make a difference.
Right now I can simulate a color loop effect by transitioning between the three primary colors, but im sure there are some other neat effects hidden that I am unaware of that can be called with a command.
Any ideas?
Thanks in advance

Posts: 1

Participants: 1

Read full topic

@aming-miyembro wrote:

Howdy,

I’ve recently installed an in-wall Kasa KP200 receptacle – a two outlet device. When added to the configuration.yaml, upon restart Home Assistant finds it, but doesn’t seem to handle the outlet entities properly.

Here’s the configuration.yaml entry for the receptacle:

tplink:
  discovery: false
  strip:
    - host: 192.168.4.10

This is how the entities show up in Home Assistant:

image860×165 10.7 KB

The bottom outlet appears twice:

• the top line with ID “switch.unnamed_device” is functional, but is Read-only, so the description can’t be changed (and I do want to change it); this entry does not appear in core.entity_registry
• the second line with ID “switch.family_room_left_bottom” appears to be the properly recognized entity, but is disabled and non-functional; this entry does appear in core.entity_registry (And what does the red “Restored” symbol mean?)
• the third line “switch.family_room_left_top” is also disabled and non-functional.

How can I fix these to have two fully functional outlets?

Not sure it matters, but my devices all reside on a separate subnet from Home Assistant, so I don’t believe they’re discoverable, and need to be added to configuration.yaml manually.

Thanks.

Posts: 1

Participants: 1

Read full topic

@Eternity_again wrote:

My question is solved. I had a typo in the .yaml

Posts: 1

Participants: 1

Read full topic

@doug987 wrote:

I’ve had the InfluxDB add on within Home Assistant for some time but apart from upgrading it occasionally haven’t really used it. This afternoon in upgrading from 3.5.1 to 3.6.2 I got the error “Failed to install addon, Unknown Error, see logs”. The following was in the Supervisor log. Has anybody else seen this?

Screenshot 2020-05-14 at 17.55.131609×587 54 KB

I have recently (Monday) moved from a rPi3 to a NUC (Ubuntu/Virtualbox) and restored a snapshot. Everything else seems to be working fine although getting zwave stick to present itself to virtualbox was challenging. I’ve tried uninstalling InfluxDB and reinstalling and get the same issue. Other add ons can be installed without issue. Any ideas?
Cheers Doug

Posts: 1

Participants: 1

Read full topic

@poudenes wrote:

Hi All,

I see In my HA folder multiple harmony*.conf files

-rw-r--r--  1 root root     14643 May 14 20:18 harmony_9866324.conf
-rw-r--r--  1 root root     10096 Apr  9 15:10 harmony_logitech_harmony.conf
-rw-r--r--  1 root root     10071 Nov 20 12:10 harmony_harmony_hub.conf

Can I remove the 2 oldest once without problem?
Cheers,

Posts: 3

Participants: 2

Read full topic

@azevenhuizen wrote:

GD all,

I am trying to setup my foscam cameras. I have 2 of them, one is fixed, the other is also ptz.
I can see both video streams on my HA dashboard.
Then I followed https://www.home-assistant.io/integrations/foscam/ to setup the ptz.
However, after that nothing happens.
So I checked the service in the developer tools, and started the service manually, but also nothing.

What could I be misising here?
(sing hass.io 108.9 by the way)

Arno

Posts: 1

Participants: 1

Read full topic

@yonny24 wrote:

I’m looking to pull in custom time frames and calculations on the on/off events of my underfloor heating switches.

So I have this panel with all the heating switches.
The idea is to extract the on/off times from the logbook and have them on another row plus calculations on cost kWh.

My panel looks like this now.

I’ve seen a couple of Gits with projects but would like to hear from people who have done something similar. How do I extract the data from the logbook easily?

Posts: 1

Participants: 1

Read full topic

@brusli009 wrote:

I have 3 wled controllers in my house and i want to control each one individually(i can do that), but i also want to use mqqt to send data to wled so they can turn on a special preset for each one. I knew how to do one but how do i do multiple.It dosent work like that
Here is my configuration file

light:
# Camera
  - platform: mqtt
    name: "WLED Camera"
    command_topic: "wled/camera"
    brightness_command_topic: "wled/camera"
    rgb_command_topic: "wled/camera/col"
    rgb_command_template: "{{ '#%02x%02x%02x' | format(red, green, blue)}}"
    effect_list:
    - "[FX=00] Solid"
    (...)
    - "[FX=82] Halloween Eyes"

input_select1:
  wled_presets:
    options:
      - "[PL=01] Preset 1"
      (...)
      - "[PL=16] Preset 16"

  wled_palette_list1:
    options:
      - "[FP=00] Default"
       (...)
      - "[FP=49] Sakura"

input_number:
  ledspeed1:
    name: Speed
    initial: 0
    min: 0
    max: 255
    step: 1
  ledintensity1:
    name: Intensity
    initial: 0
    min: 0
    max: 255
    step: 1


# Birou
  - platform: mqtt
    name: "WLED Birou"
    command_topic: "wled/birou"
    brightness_command_topic: "wled/birou"
    rgb_command_topic: "wled/birou/col"
    rgb_command_template: "{{ '#%02x%02x%02x' | format(red, green, blue)}}"
    effect_list:
    - "[FX=00] Solid"
    (...)
    - "[FX=82] Halloween Eyes"

input_select:
  wled_presets2:
    options:
      - "[PL=01] Preset 1"
      (...)
      - "[PL=16] Preset 16"

  wled_palette_list2:
    options:
      - "[FP=00] Default"
       (...)
      - "[FP=49] Sakura"

input_number:
  ledspeed2:
    name: Speed
    initial: 0
    min: 0
    max: 255
    step: 1
  ledintensity2:
    name: Intensity
    initial: 0
    min: 0
    max: 255
    step: 1

# Sufragerie
  - platform: mqtt
    name: "WLED Sufragerie"
    command_topic: "wled/sufragerie"
    brightness_command_topic: "wled/sufragerie"
    rgb_command_topic: "wled/sufragerie/col"
    rgb_command_template: "{{ '#%02x%02x%02x' | format(red, green, blue)}}"
    effect_list:
    - "[FX=00] Solid"
    (...)
    - "[FX=82] Halloween Eyes"

input_select:
  wled_presets3:
    options:
      - "[PL=01] Preset 1"
      (...)
      - "[PL=16] Preset 16"

  wled_palette_list3:
    options:
      - "[FP=00] Default"
       (...)
      - "[FP=49] Sakura"

input_number:
  ledspeed3:
    name: Speed
    initial: 0
    min: 0
    max: 255
    step: 1
  ledintensity3:
    name: Intensity
    initial: 0
    min: 0
    max: 255
    step: 1

And my automations folder looks like this

#Camera
  
- id: wled_speed
  alias: wled_speed Camera
  trigger:
  - entity_id: input_number.ledspeed1
    platform: state
  condition: []
  action:
  - data_template:
      topic: wled/camera/api
      payload: SX={{ states('input_number.ledspeed1') | int }}
    service: mqtt.publish

- id: wled_intensity
  alias: wled_intensity Camera
  trigger:
  - entity_id: input_number.ledintensity1
    platform: state
  condition: []
  action:
  - data_template:
      topic: wled/camera/api
      payload: IX={{ states('input_number.ledintensity1') | int }}
    service: mqtt.publish


- id: wled_palette
  alias: WLED Palette Camera
  trigger:
  - platform: state
    entity_id: input_select.wled_palette_list1
  condition: []
  action:
  - service: mqtt.publish
    data_template:
      topic: wled/camera/api
      payload: "{{ states('input_select.wled_palette_list1') }}"


- id: wled_presets
  alias: WLED Presets Camera
  trigger:
  - platform: state
    entity_id: input_select.wled_presets1
  condition: []
  action:
  - service: mqtt.publish
    data_template:
      topic: wled/camera/api
      payload: "{{ states('input_select.wled_presets1') }}"

#birou
  
- id: wled_speed
  alias: wled_speed birou
  trigger:
  - entity_id: input_number.ledspeed2
    platform: state
  condition: []
  action:
  - data_template:
      topic: wled/birou/api
      payload: SX={{ states('input_number.ledspeed2') | int }}
    service: mqtt.publish

- id: wled_intensity
  alias: wled_intensity birou
  trigger:
  - entity_id: input_number.ledintensity2
    platform: state
  condition: []
  action:
  - data_template:
      topic: wled/birou/api
      payload: IX={{ states('input_number.ledintensity2') | int }}
    service: mqtt.publish


- id: wled_palette
  alias: WLED Palette birou
  trigger:
  - platform: state
    entity_id: input_select.wled_palette_list2
  condition: []
  action:
  - service: mqtt.publish
    data_template:
      topic: wled/birou/api
      payload: "{{ states('input_select.wled_palette_list2') }}"


- id: wled_presets
  alias: WLED Presets birou
  trigger:
  - platform: state
    entity_id: input_select.wled_presets2
  condition: []
  action:
  - service: mqtt.publish
    data_template:
      topic: wled/birou/api
      payload: "{{ states('input_select.wled_presets2') }}"

#sufragerie
  
- id: wled_speed
  alias: wled_speed sufragerie
  trigger:
  - entity_id: input_number.ledspeed3
    platform: state
  condition: []
  action:
  - data_template:
      topic: wled/sufragerie/api
      payload: SX={{ states('input_number.ledspeed3') | int }}
    service: mqtt.publish

- id: wled_intensity
  alias: wled_intensity sufragerie
  trigger:
  - entity_id: input_number.ledintensity3
    platform: state
  condition: []
  action:
  - data_template:
      topic: wled/sufragerie/api
      payload: IX={{ states('input_number.ledintensity3') | int }}
    service: mqtt.publish


- id: wled_palette
  alias: WLED Palette sufragerie
  trigger:
  - platform: state
    entity_id: input_select.wled_palette_list3
  condition: []
  action:
  - service: mqtt.publish
    data_template:
      topic: wled/sufragerie/api
      payload: "{{ states('input_select.wled_palette_list3') }}"


- id: wled_presets
  alias: WLED Presets sufragerie
  trigger:
  - platform: state
    entity_id: input_select.wled_presets3
  condition: []
  action:
  - service: mqtt.publish
    data_template:
      topic: wled/sufragerie/api
      payload: "{{ states('input_select.wled_presets3') }}"

Posts: 1

Participants: 1

Read full topic