@Bobbles wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@david1 wrote:

Trying to get ahold of these “cards” concept

resources:
  - url: /local/custom-lovelace/upcoming-media-card/upcoming-media-card.js
    type: js
  - url: /local/layout-card.js
    type: module
  - url: /local/text-element.js
    type: js


views:
  - cards:
    - cards:
        - type: weather-forecast
          entity: weather.home
        - type: thermostat
          entity: climate.main_floor 
      type: vertical-stack

    - cards:
        - type: sensor
          entity: sensor.sabnzbd_status
        - type: sensor
          entity: sensor.sabnzbd_queue 

        - type: picture-elements 
          image: /local/plexbanner.jpeg
          elements:
            - type: custom:text-element
              text: "<b style='color: orange; font-size: 16px'>Total </b>"
              style: {left: 20%, top: 14%}
            - type: state-label
              entity: sensor.plex_sf_network
              style: {color: white, font-size: 16px, left: 20%, top: 26%}
              
            - type: custom:text-element
              text: "<b style='color: orange; font-size: 16px'>Direct play </b>"
              style: {left: 55%, top: 14%}                  
            - type: state-label
              # prefix: 'Direct play: '
              entity: sensor.tautulli_direct_plays
              style: {color: white, font-size: 16px, left: 55%, top: 26%}    

            - type: custom:text-element
              text: "<b style='color: orange; font-size: 16px'>Direct stream </b>"
              style: {left: 20%, top: 44%}               
            - type: state-label
              entity: sensor.tautulli_direct_streams
              style: {color: white, font-size: 16px, left: 20%, top: 56%}    

            - type: custom:text-element
              text: "<b style='color: orange; font-size: 16px'>Transcode </b>"
              style: {text-align: left,left: 55%, top: 44%}             
            - type: state-label
              entity: sensor.tautulli_count_transcode
              style: {color: white, font-size: 16px, left: 55%, top: 56%}    

            - type: custom:text-element
              text: "<b style='color: orange; font-size: 16px'>LAN bandwidth </b>"
              style: {left: 20%, top: 74%}               
            - type: state-label
              entity: sensor.tautulli_lan_bandwidth
              style: {color: white, font-size: 16px, left: 20%, top: 86%}      

            - type: custom:text-element
              text: "<b text-align: left, style='color: orange; font-size: 16px'>WAN bandwidth </b>"
              style: {left: 55%, top: 74%}             
            - type: state-label
              entity: sensor.tautulli_wan_bandwidth
              style: {color: white, font-size: 16px, left: 55%, top: 86%}
      type: vertical-stack


    - cards:
        - type: custom:upcoming-media-card
          entity: sensor.plex_recently_added
          image_style: fanart
      type: vertical-stack

    - cards:
        - type: custom:upcoming-media-card
          entity: sensor.plex_recently_added
          image_style: fanart
      type: vertical-stack

The fourth card i want to have its own column, but instead it just drops underneath my thermostat

Posts: 7

Participants: 3

Read full topic

@NIVO wrote:

Hi,

I have a setup of two Home Assistant instances, one a Raspberry Pi (Secondary) and the second on a NUC (Primary).
On the secondary HA I have a number of switches and sensors. I want to get all devices over to the primary. On the primary I have to use Node-Red to control the switches. I have tried the plug-in from Lukas. This seems to be a great plug-in, but when the automation kicks in it often misses to turn on the light. In the log on the primary is says “Unable to find referenced entities switch.%prefix%.switchname”. But when I manually trigger the switches on the primary that is linked to the secondary it always works.
I does not matter to me if I must go over to mqtt, but I have a hard time understanding the concept of bi-directional communication.
All help is appreciated.
Thanks!

Posts: 4

Participants: 2

Read full topic

@mrhaugland wrote:

I currently have Home Assistant up and running on my NUC and want to swap my HDD with a SSD. I dont need my NUC for anything other than Home Assistant.

I have Home Assistant Core 0.106.2 as of right now, with Add-on store and Supervisor 209. This is running on Ubuntu 18.04 desktop version. I also use the community store (HACS).
Does this mean I have Home Assitant Supervised?

I have Portainer, so perhaps I did the previous installation using Docker…

image1168×128 14.8 KB

This looks familiar: Absolute Beginners guide to installing HA on Intel NUC using Docker

I have been reading up on different installation methods, and watched some Youtube-videos, but I am still not sure what would be the best way to reinstall everything. If its possible to reload my entire config like it is today, that would be sweet. I am not sure if restoring a snapshot does this, especially with secured devices like door locks? I also would like to do an installation that is as future proof as can be, in the direction that Home Assistant is taking.

I have little to none experience with Linux, and need to Google everything i do.

If I have understood this correctly I can either go with Docker installation or VM? I just cant wrap my head around how to install the image for NUC on my NUC without Docker or VM

Could anyone here try to unwrap my mind just a bit, and help me get started?

Posts: 2

Participants: 2

Read full topic

@fredd589 wrote:

Hi guys, I’m trying to make a trigger for when a light switch is pressed to switch on something else. In my automation setup, under trigger type, I can choose the switch but for the Trigger itself I’m getting the message ‘Unknown trigger;’

This is appearing for all devices, ie Hue bulbs etc…

Any ideas appreciated!

Posts: 2

Participants: 2

Read full topic

@pirpy wrote:

Hello
I’m trying to receive data string from my powermeter in my hassio with serial sensor

the power meter sends this string

490.74,235.27,3.05,0.68, 726.72,233.05,3.67,0.85, 208.93,235.24,1.14,0.78, 17864.96,84042.15
every second

  - platform: serial
    serial_port: /dev/ttyUSB0
    baudrate: 115200

  - platform: template
    sensors:

      my_powermeter_sensor_l1w:
        friendly_name: L1_W
        unit_of_measurement: "W"
        value_template: "{{ states('sensor.serial_sensor').split(',')[1] | float }}"
      my_powermeter_sensor_l1v:
        friendly_name: L1_V
        unit_of_measurement: "V"
        value_template: "{{ states('sensor.serial_sensor').split(',')[2] | float }}"
      my_powermeter_sensor_l1a:
        friendly_name: L1_A
        unit_of_measurement: "A"
        value_template: "{{ states('sensor.serial_sensor').split(',')[3] | float }}"
      my_powermeter_sensor_l1cosphi:
        friendly_name: L1_cosphi
        unit_of_measurement: "Q"
        value_template: "{{ states('sensor.serial_sensor').split(',')[4] | float }}"   
      my_powermeter_sensor_l2w:
        friendly_name: L2_W
        unit_of_measurement: "W"
        value_template: "{{ states('sensor.serial_sensor').split(',')[5] | float }}"
      my_powermeter_sensor_l2v:
        friendly_name: L2_V
        unit_of_measurement: "V"
        value_template: "{{ states('sensor.serial_sensor').split(',')[6] | float }}"
      my_powermeter_sensor_l2a:
        friendly_name: L2_A
        unit_of_measurement: "A"
        value_template: "{{ states('sensor.serial_sensor').split(',')[7] | float }}"
      my_powermeter_sensor_l2cosphi:
        friendly_name: L2_cosphi
        unit_of_measurement: "Q"
        value_template: "{{ states('sensor.serial_sensor').split(',')[8] | float }}"        
      my_powermeter_sensor_l3w:
        friendly_name: L3_W
        unit_of_measurement: "W"
        value_template: "{{ states('sensor.serial_sensor').split(',')[9] | float }}"
      my_powermeter_sensor_l3v:
        friendly_name: L3_V
        unit_of_measurement: "V"
        value_template: "{{ states('sensor.serial_sensor').split(',')[10] | float }}"
      my_powermeter_sensor_l3a:
        friendly_name: L3_A
        unit_of_measurement: "A"
        value_template: "{{ states('sensor.serial_sensor').split(',')[11] | float }}"
      my_powermeter_sensor_l3cosphi:
        friendly_name: L3_cosphi
        unit_of_measurement: "Q"
        value_template: "{{ states('sensor.serial_sensor').split(',')[12] | float }}" 
      my_powermeter_sensor_whout:
        friendly_name: WH_out
        unit_of_measurement: "Wh"
        value_template: "{{ states('sensor.serial_sensor').split(',')[13] | float }}"
      my_powermeter_sensor_whin:
        friendly_name: Wh_in
        unit_of_measurement: "Wh"
        value_template: "{{ states('sensor.serial_sensor').split(',')[14] | float }}"  

but in the states all I get is an unavailable
log:
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L2_A: UndefinedError: list object has no element 7
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template Wh_in: UndefinedError: list object has no element 14
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L2_cosphi: UndefinedError: list object has no element 8
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L3_W: UndefinedError: list object has no element 9
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L1_A: UndefinedError: list object has no element 3
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L1_W: UndefinedError: list object has no element 1
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L3_V: UndefinedError: list object has no element 10
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L3_A: UndefinedError: list object has no element 11
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L1_cosphi: UndefinedError: list object has no element 4
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L2_W: UndefinedError: list object has no element 5
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L3_cosphi: UndefinedError: list object has no element 12
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template WH_out: UndefinedError: list object has no element 13
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L2_V: UndefinedError: list object has no element 6
2020-03-26 15:58:10 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template L1_V: UndefinedError: list object has no element 2

thank you

Posts: 8

Participants: 4

Read full topic

@koQuarium wrote:

Hi,

I am trying to configure blutooth tracking and have a question about that.

I have configured config.yaml according to https://www.home-assistant.io/integrations/bluetooth_tracker/.

HA boots up without a problem but I don’t see any BT devices in known_devices.yaml.

Probably because pybluez is not installed on my rpi.
If I ssh to the rpi I cannot install the package.

.

I found this clue on the Inernet “In hassio there is no such thing as apt-get. you can’t do this! If you want this, you have to use raspbian or a virtual environment. Hassio is a device. ’

How do I get “pybluez” installed on my rpi?

Thanks in advance.

Regards, Ko

Posts: 7

Participants: 2

Read full topic

@hlalayan wrote:

Hi

Need help

Environment: pi4 hassio 0.107.7

I have generic_termostat, and manual alarm panel,

After power off/on the pi, the last states not restoring

Thank you

Posts: 6

Participants: 4

Read full topic

@Marius82 wrote:

Hi!
I have changed my internet provider. And now I’m connected over DS-Lite with an IPv6 adress.
I have some questions to to get external access to home assistant without the nabu casa cloud solution.

Do I only need run the Duckdns Hass.io addon? Or also the Duckdns DynDNS entry in my router (Fritzbox)?

Or is there no need for duckdns because of IPv6?

Thank you

Posts: 1

Participants: 1

Read full topic

@chris4 wrote:

HI, after the 107.7 update has received fail.
What could it be?
Thanks.

HA Fail2318×1660 63.9 KB

HA Fail22318×1660 86.2 KB

Posts: 2

Participants: 2

Read full topic

@Hany_Wahba wrote:

i am trying to connect norklmes zigbee light switch. it gets discovered as light not a switch. when added to lovelace clicking the button does not turn the light on or off and it does not get updated with the real state when turning on the switch manually.

[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]
Ignoring message (b’09100200c20101000101’) on cluster 61184: unknown endpoint or cluster id: ‘No cluster ID 0xef00 on (ec:1b:bd:ff:fe:0c:16:10, 1)’
Ignoring message (b’09110200c30101000100’) on cluster 61184: unknown endpoint or cluster id: ‘No cluster ID 0xef00 on (ec:1b:bd:ff:fe:0c:16:10, 1)’
Ignoring message (b’09120200c40101000101’) on cluster 61184: unknown endpoint or cluster id: ‘No cluster ID 0xef00 on (ec:1b:bd:ff:fe:0c:16:10, 1)’
Ignoring message (b’09130200c50101000100’) on cluster 61184: unknown endpoint or cluster id: ‘No cluster ID 0xef00 on (ec:1b:bd:ff:fe:0c:16:10, 1)’
Ignoring message (b’09140200c60101000101’) on cluster 61184: unknown endpoint or cluster id: ‘No cluster ID 0xef00 on (ec:1b:bd:ff:fe:0c:16:10, 1)’
Ignoring message (b’09150200c70101000100’) on cluster 61184: unknown endpoint or cluster id: ‘No cluster ID 0xef00 on (ec:1b:bd:ff:fe:0c:16:10, 1)’
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0xaf3a (ec:1b:bd:ff:fe:0c:16:10) left the network
Device 0x6eb8 (ec:1b:bd:ff:fe:0c:16:10) joined the network
Device ec:1b:bd:ff:fe:0c:16:10 changed id (0xaf3a => 0x6eb8)
[0x6eb8:zdo] ZDO request 0x0013: [0x6eb8, ec:1b:bd:ff:fe:0c:16:10, 142]
Checking quirks for _TYST11_7tdtqgwv tdtqgwv (ec:1b:bd:ff:fe:0c:16:10)
Considering <class ‘bellows.zigbee.application.EZSPCoordinator’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.gledopto.soposhgu10.SoposhGU10’>
Fail because endpoint list mismatch: {11, 13} {1}
Considering <class ‘zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2’>
Fail because profile_id mismatch on at least one endpoint
Considering <class ‘zhaquirks.netvox.z308e3ed.Z308E3ED’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.osram.a19twhite.A19TunableWhite’>
Fail because endpoint list mismatch: {3} {1}
Considering <class ‘zhaquirks.philips.rom001.PhilipsROM001’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.philips.rwl021.PhilipsRWL021’>
Fail because endpoint list mismatch: {1, 2} {1}
Considering <class ‘zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.smartthings.tag_v4.SmartThingsTagV4’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.xbee.xbee3_io.XBee3Sensor’>
Fail because endpoint list mismatch: {232, 230} {1}
Considering <class ‘zhaquirks.xbee.xbee_io.XBeeSensor’>
Fail because endpoint list mismatch: {232, 230} {1}
Considering <class ‘zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor’>
Fail because device_type mismatch on at least one endpoint
device - 28344:ec:1b:bd:ff:fe:0c:16:10 entering async_device_initialized - is_new_join: False
device - 28344:ec:1b:bd:ff:fe:0c:16:10 has been reset and re-added or its nwk address changed
skipping discovery for previously discovered device - 28344:ec:1b:bd:ff:fe:0c:16:10
28344: started configuration
28344:ZDO: ‘async_configure’ stage succeeded
28344: started initialization
28344:ZDO: ‘async_initialize’ stage succeeded
[28344:1:0x0006]: bound ‘on_off’ cluster: Status.SUCCESS
[28344:1:0x0000]: bound ‘basic’ cluster: Status.SUCCESS
[28344:1:0x0000]: finished channel configuration
[0x6eb8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=59 command_id=Command.Default_Response>
[0x6eb8:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=61 command_id=Command.Read_Attributes_rsp>
[0x6eb8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=57 command_id=Command.Read_Attributes_rsp>
[28344:1:0x0006]: reporting ‘on_off’ attr on ‘on_off’ cluster: 0/900/1: Result: ‘[6, <Status.UNSUP_GENERAL_COMMAND: 130>]’
[28344:1:0x0006]: finished channel configuration
[28344:1:0x0000]: initializing channel: from_cache: False
[28344:1:0x0006]: initializing channel: from_cache: False
[28344:1:0x0006]: ‘async_configure’ stage succeeded
[28344:1:0x0000]: ‘async_configure’ stage succeeded
28344: completed configuration
28344: stored in registry: ZhaDeviceEntry(name=’_TYST11_7tdtqgwv tdtqgwv’, ieee=‘ec:1b:bd:ff:fe:0c:16:10’, last_seen=1585244317.4645543)
[0x6eb8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=63 command_id=Command.Read_Attributes_rsp>
[0x6eb8:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=65 command_id=Command.Read_Attributes_rsp>
[0x6eb8:1:0x0003] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=67 command_id=Command.Default_Response>
[28344:1:0x0000]: initializing channel: from_cache: False
[28344:1:0x0003]: executed ‘trigger_effect’ command with args: ‘(2, 0)’ kwargs: ‘{}’ result: [64, <Status.SUCCESS: 0>]
[28344:1:0x0006]: ‘async_initialize’ stage succeeded
[28344:1:0x0000]: ‘async_initialize’ stage succeeded
28344: power source: Mains
28344: completed initialization
[0x6eb8:1:0x0000] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=22 command_id=Command.Report_Attributes>
[0x6eb8:1:0x0000] ZCL request 0x000a: [[<Attribute attrid=1 value=>]]
[0x6eb8:1:0x0000] Attribute report received: app_version=73
[0x5c10:1:0x0402] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=205 command_id=Command.Report_Attributes>
[0x5c10:1:0x0402] ZCL request 0x000a: [[<Attribute attrid=0 value=>]]
[0x5c10:1:0x0402] Attribute report received: measured_value=1770
[0x5c10:1:0x0405] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=206 command_id=Command.Report_Attributes>
[0x5c10:1:0x0405] ZCL request 0x000a: [[<Attribute attrid=0 value=>]]
[0x5c10:1:0x0405] Attribute report received: measured_value=4492
[0x5c10:1:0x0403] ZCL deserialize: <ZCLHeader frame_control= manufacturer=None tsn=207 command_id=Command.Report_Attributes>
[0x5c10:1:0x0403] ZCL request 0x000a: [[<Attribute attrid=0 value=>, <Attribute attrid=20 value=>, <Attribute attrid=16 value=>]]
[0x5c10:1:0x0403] Attribute report received: measured_value=1003, 20=-1, 16=10033

Posts: 1

Participants: 1

Read full topic

@Canedje wrote:

I try to connect my old Homey by a MQTT connection to HA.
So I installed Mosquitto broker on HA.
I didn’t use login in the config.
MQTT broker is started and showing up in integration (no connected entities)
In Homey I installed a MQTT client and trying to configure it.
As Ip/DNS I used my https:// myname.duckdns.org I normally use for login to HA
Portnr: 1883
I didn’t select TLS and also not the username and password in the settingspart of my Homey MQTT client part (because I did not fill this in in HA MQTT config).
(Or do I need to fill in here my login of HA?, I tried anyway also without succes)

I did setup a flow to send a message to HA.
After setup Homey there is no (Homey) entity showing up in the integrations part of HA.

What am I doing wrong?

Posts: 5

Participants: 2

Read full topic

@cdikland wrote:

In reading posts here and elsewhere I understand that many people have managed to get the above combination to work by plugging in an unpowered USB2 hub into the Pi and then plugging the zwave stick into the hub.

I just got a usb2 hub but cannot get the Pi 4 to recognize this zwave stick . I have tried every port on the hub as well as every usb port on the PI. I know the hub is working fine because 1) the stick is getting power once I bott the PI . 2) A thumb drive into the hub is recognized by the PI
This is the hub I am using

IMG_20200326_1434361961×3763 533 KB

Is there something I need to do in the PI configuration? Can someone guide me through the process they used to get this to work?

Thanks in advance

The log file clearly shows the stick cant be found

  File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/option.py", line 81, in __init__
    raise ZWaveException(u"Error when retrieving device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: 'Zwave Generic Exception : Error when retrieving device /dev/ttyUSB0 : [\'Traceback (most recent call last):\\n\', \'  File "/srv/homeassistant/lib/python3.7/site-packages/openzwave/option.py", line 78, in __init__\\n    raise ZWaveException(u"Can\\\'t find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))\\n\', \'openzwave.object.ZWaveException: "Zwave Generic Exception : Can\\\'t find device /dev/ttyUSB0 : [\\\'NoneType: None\\\\\\\\n\\\']"\\n\']'

Posts: 1

Participants: 1

Read full topic

@jantinus wrote:

Hello,

Today I bought myself a nice Conbee stick to manage my zigbee devices. Unfortunately it interferes with my AEON zwave stick. The thing is, my Ubuntu Server 18.04 host system randomly assigns serial adresses to the stick (ACM0 or ACM1).

Things I tried:

• Assign the ‘by-id’ address, found on the supervisor–>hardware tab in the Deconz-add-on-settings. (the app doesn’t work when I do this)
• Reflash the home assistant image (aparantly there’s something with the start-up scripts that don’t update)

Up until now nothing worked. What would be a good course of action to let these sticks play nicely together?

Posts: 2

Participants: 1

Read full topic

@antoniod wrote:

Hi everyone! I am a new fan of home automation and I am discovering this world day by day. I have some difficulties that I would like to explain to you. If there is anyone who can help me, I would be hugely grateful.

I installed home assistant 0.107.7 (hassio) on raspberry pi 3. I followed the example described here https://www.juanmtech.com/set-up-the-picture-elements-card-in-home-assistant/ completing the whole tutorial. I can’t do the same job on two or more rooms on the same floor plan using the custom “picture elements” tab. If I add them on the same tab, the second action I create replaces the first and only one works.

here I leave the code used:

elements:
  - entity: switch.led_rosso
    image: /local/custom_ui/floorplan/letto.png
    state_filter:
      'off': brightness (50%)
      'on': brightness (100%)
    style:
      left: 50%
      top: 50%
      width: 100%
    tap_action: none
    type: image
  - entity: switch.led_rosso
    icon: 'mdi: ceiling-light'
    style:
      '--iron-icon-height': 42px
      '--iron-icon-width': 42px
      left: 35%
      top: 66%
    tap_action:
      action: toggle
    type: state-icon
  - entity: switch.led_verde
    image: /local/custom_ui/floorplan/cucina.png
    state_filter:
      'off': brightness (50%)
      'on': brightness (100%)
    style:
      left: 50%
      top: 50%
      width: 100%
    tap_action: none
    type: image
  - entity: switch.led_verde
    icon: 'mdi: ceiling-light'
    style:
      '--iron-icon-height': 42px
      '--iron-icon-width': 42px
      left: 30%
      top: 25%
    tap_action:
      action: toggle
    type: state-icon
image: /local/custom_ui/floorplan/pianta.png
type: picture-elements

Thanks in advance to anyone who can help me out!

Posts: 1

Participants: 1

Read full topic

@Elston_Gunn wrote:

I have some Echo devices and a couple of FireTVs. If I say “Alexa, Announce Hello World”, all the echo devices speak the phrase AND the FireTVs turn themselves on. I would like use this behavior in a HA script, but I’m having a problem.

I’m using the Alexa Media Player integration. I specify the echo device and the fire TV entities in my script, but only the echo speaks the phrase. I expect the FireTV to turn on as it does when responding to voice commands, but it doesn’t. Here’s my syntax, what am I doing wrong? Or maybe FireTV isn’t supported for “announce” in the HA Integration? Thanks in advance for clues or alternative methods to achieve the desired result.

test_bedroom_tv_on:
  sequence:
    - service: notify.alexa_media
      data:
        target:
          - media_player.bedroom_firetv
          - media_player.bedroom_dot
        data:
          type: announce
        message: "Hello World"

Posts: 1

Participants: 1

Read full topic

@TheFax wrote:

Hello friends,
I have a script in my hassio that:

1. turns on a fan
2. wait some time (30…120 minutes, depends by a slider)
3. then turn off the fan.

What I expect is: when I start the script via the related switch on the Lovelace interface, the switch goes to ON position and remains ON until the script is terminated and the fan turn off.

The probelm is when I turn on the switch, it returns to off after some seconds, but the script is not yet terminated and the fan is active. If I update the Home Assistant webpage (pressing F5 for example), the switch returns to on position as expected.

It’s a strange behaviour.

Could you help me?

This is the source of the script:

ventilazione_forzata:
  alias: "Ventilazione a tempo"
  sequence:
    - data:
        entity_id: switch.ventola
      service: switch.turn_on
    - delay:
        minutes: "{{ states('input_number.slider_fan') | int }}"
    - data:
        entity_id: switch.ventola
      service: switch.turn_off

My hassio is latest version (107.x), and it is installed into a Raspberry.
I have it since version 0.94, and this issue has always been present.
The fan is connected to a Sonoff with Tasmota firmware, but I think this is not useful, because the problem seems related to the script itself.

Posts: 3

Participants: 3

Read full topic

@fsp wrote:

Hello!

I’ve just gotten started with Home Assistant: installed it on my Raspberry Pi 3 with the pre-cooked VM image on an SD card (version 0.107.6). First of all, kudos to the developers, maintainers, and community. Home Assistant is quite impressive!

I have 5 RF-controlled (433 MHz) plugs distributed in my apartment, each controlling a light, which I switch on and off with a transceiver connected to the GPIO pins of my Raspberry Pi. The following lines in my configuration.yaml do the magic, e.g.:

switch:
  - platform: rpi_rf
    gpio: 17
    switches:
        # 1 in the remote control
        llum_peu_tele:
            code_on:  XXXXXXX # Actual number here...
            code_off: XXXXXXX # Actual number here...
            pulselength:  170
            signal_repetitions: 15

Works beautifully. The only annoying problem is that when I reboot the Raspberry Pi, the state is gone: all switches reset to off.

After searching left and right in the forum, I have the following alternative (maintaining the switch lines above):

input_boolean:
    testbool:
        name: Test1
        icon: mdi:floor-lamp

automation:
    - alias: 'Test input_boolean'
      trigger:
        platform: state
        entity_id: input_boolean.testbool
        to: 'on'
      action:
        service: switch.turn_on
        entity_id: switch.llum_peu_tele

With this scheme I can turn the light on/off and, additionally, the input_boolean maintains the state after reboots (the switch does not).

I could add one such block for every switch (power plug) and every trigger (on/off), but it strikes me as too cumbersome. Also, with this scheme I see both the input boolean and the switch in my Lovelace interface, but that’s a minor issue (and can probably be solved easily once I have a bit more experience).

Is there a straightforward way to add the input_boolean functionality to a switch so as to retain its state under reboots? Is the input_boolean my only hope?

Many thanks in advance for any pointer you may provide!

PS: I’ve searched extensively in the forum and did not manage to find an obvious solution. Apologies in advance in case I failed to find the right post.

Posts: 1

Participants: 1

Read full topic

@matt666 wrote:

I’ve got a set of Ikea bulbs and plugs in my lounge which is controlled by an Ikea remote switch. I’ve also got another light that is controlled by a standard IR remote.

I have a broadlink RM pro, I’m wondering if it’s possible to use hassio in some way to trigger the broadlink to send an IR command to turn the light on when I press the Tradfri remote switch?

Posts: 1

Participants: 1

Read full topic

@rzulian wrote:

Hey!
I’m testing the connection to KNX.
Reading values is working fine, but I’m struggling trying to write values.
This is an example:

knx:
  expose:
    - type: '1byte_unsigned'
      address: '0/0/5'
      entity_id: 'sensor.hencozona1_forzamodo'

sensor:
  - platform: knx
    name: HencoZona1.ForzaModo
    state_address: '0/0/5'
    type: '1byte_unsigned'

When I try to set the state from the dev tool, I’m getting this error on the log

2020-03-26 21:09:02 ERROR (MainThread) [xknx.log] Error while processing telegram <CouldNotParseTelegram description="payload invalid" device_name="HencoZona1.ForzaModo" group_address="0/0/5" payload="<DPTBinary value="0" />"/>

Can you help me? What am I doing wrong?
Thanks
R

Posts: 1

Participants: 1

Read full topic