Hello,
I have several switches. Some I have created switch groups for. One example is turning my PC and monitors off and on. I would like, however, a delay before the monitors are turned off. This way I can monitor the shutdown, ensuring all is well.

Here is my current code:

      desktoppc_and_monitors:
        turn_on:
          service: switch.turn_on
          data:
            entity_id: 
              - switch.1_monitors
              - switch.desktoppc
        turn_off:
          service: switch.turn_off
          data:
            entity_id: 
              - switch.desktoppc
              - delay: 00:00:30
              - switch.1_monitors

In this configuration the switch group does not work at all. If I remove the delay then it’s fine.

Does anyone know if it’s possible to get a delay working in this scenario?

Much appreciate any support.

Thank you

2 posts - 2 participants

Read full topic

My goal is to set up one D1 Mini with tasmota 8.1.3 to have the following:

-1 real relay to turn on/off porch light

-3 physical touch sensors working as switches. One switch would control the real relay, and the other two switches would control two remote relays via rules

-1 hall sensor set up as a switch to monitor door open/close

-1 buzzer.

-Once all set up, I would like to be able to longpress the two remote switches, to create a hold and use that to disarm the alarm.

So far I’ve got everything working except for the two ghost switches (the ones that control remote relays). At one point I had it all working except the longpress part. I tried using buttons instead of switches and all hell broke lose. When ever I try to play with buttons instead of switches my tasmotas end up being reset. Supposedly it is feature of tasmota but only if I hold for more than 40 seconds which I haven’t done.

Screenshot from 2020-07-19 19-41-15402×770 48.1 KB

That is my current setup

Relay1i is the real relay

Switch4 is touch sensor ghost switch to control remote living room lights (switchmode 3)

Switch3 is the hall sensor monitoring the door (switchmode 2)

Relay2 is not a physical relay. When turned “on” it provides the 3.3v to the buzzer

Switch1 is a touch sensor used to toggle Relay1i

Switch5 is a touch sensor ghost switch to control remote livingroom fan (switchmode 3)

Switch2 is a dummy switch, nothing connected to the pin. I had to create the dummy switch because door switch (switch 3) was turning buzzer on and off. Buzzer will be controlled 100% via HA.

This is my console info, after I set up the rule;

01:35:23 MQT: stat/tasmota_553DDB/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Length":62,"Free":449,"Rules":"on SWITCH4#state DO publish SalaMiriam/cmnd/POWER TOGGLE endon"}
01:35:45 MQT: cmnd/tasmota_553DDB/POWER4 = ON
01:35:45 MQT: stat/tasmota_553DDB/SWITCH4 = {"STATE":"ON"}
01:35:45 MQT: stat/tasmota_553DDB/RESULT = {"Command":"Error"}
01:35:46 MQT: cmnd/tasmota_553DDB/POWER4 = ON
01:35:46 MQT: stat/tasmota_553DDB/SWITCH4 = {"STATE":"ON"}
01:35:46 MQT: stat/tasmota_553DDB/RESULT = {"Command":"Error"}
01:35:52 MQT: cmnd/tasmota_553DDB/POWER4 = ON
01:35:52 MQT: stat/tasmota_553DDB/SWITCH4 = {"STATE":"ON"}
01:35:52 MQT: stat/tasmota_553DDB/RESULT = {"Command":"Error"}

If you notice I am using SalaMiriam/cmnd/POWER TOGGLE, but instructions have cmnd/SalaMiriam/… but when I did have it working a couple of days ago, I am 95% sure it was with SalaMiriam frist. But just to verify here is with the info swapped.

01:36:49 CMD: rule1 on SWITCH4#state do publish cmnd/SalaMiriam/POWER TOGGLE endon
01:36:49 RUL: Stored uncompressed, would compress from 62 to 48 (-23%)
01:36:49 MQT: stat/tasmota_553DDB/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Length":62,"Free":449,"Rules":"on SWITCH4#state do publish cmnd/SalaMiriam/POWER TOGGLE endon"}
01:36:58 MQT: cmnd/tasmota_553DDB/POWER4 = ON
01:36:58 MQT: stat/tasmota_553DDB/SWITCH4 = {"STATE":"ON"}
01:36:58 MQT: stat/tasmota_553DDB/RESULT = {"Command":"Error"}
01:37:00 MQT: cmnd/tasmota_553DDB/POWER4 = ON
01:37:00 MQT: stat/tasmota_553DDB/SWITCH4 = {"STATE":"ON"}
01:37:00 MQT: stat/tasmota_553DDB/RESULT = {"Command":"Error"}

Like I said, this morning I had everything working as I wanted. The only thing I was playing with was being able to hold down two sensors/switches for 4 seconds to put both on hold to trigger an automation to disarm the alarm. I switched the two ghosts switches to buttons, rebooted and after a couple of presses my tasmota got reset. Yesterday it did the same thing with another tasmota setup I was playing with.

For what it is worth. When I had it working this morning the setup was a bit different. I had 5 relays and 4 switches set up. Out of the 5 relays, relay1 was a real relay, relay2, 3 and 4 were dummy relays, and relay5 was the one used for the buzzer. SW1 was for Relay1, SW2 and SW3 were working with rules to toggle living room lights and fan, and SW4 was the door sensor. I didn’t have to list a SW5 to get relay5 to work.

Since I had to start from scratch I figured I would switch the switch numbers around as to not have to create so many dummy relays.

All that said, could someone be kind enough to help me first get the rules working for switches 4 and 5 so they can control the remote relays. Then help me with the hold feature, which I know I would have to switch them to switchmode 5 since switchmode3 doesn’t allow long press.

One last thing, I do have switchtopic set to 1

1 post - 1 participant

Read full topic

I am using this plugin and have created some garbage reminders. Now, I want to create a reminder to charge my keyboard every 25 days. I’ve added this code, but the sensor do not show up after a reboot. Can someone correct my mistakes?

  - name: 'Charge Keyboard'
    frequency: 'every-n-days'
    first_date: '2020-07-20'
    period: 25
    icon_normal: mdi:keyboard
    verbose_state: true
    verbose_format: '{days} days'

1 post - 1 participant

Read full topic

I cannot for the life of me remember how to add a new device. My TP-Link integration has been working fine for ages (and I’m sure I’ve even done this before), but the new HS100 switches that I finally got round to opening won’t show up in HA.

They work fine in the Kasa app, and Alexa found them immediately through its Kasa skill, so why won’t HA?

I can’t find any reference to a setting for auto-discovery of new devices or how to force the integration to scan for new devices on the network. Am I missing something obvious? I’m on the latest HassOS 4.11 and there are no pending updates to Home Assistant, so I assume I’m on the latest there too.

1 post - 1 participant

Read full topic

Curious for those of you how upgraded to a HP T620 quad core, what is the largest SSD drive you have successfully installed? HP specs show a max of 64GB. Has anyone gone larger?

1 post - 1 participant

Read full topic

Hello, I have an error in automation but I can’t find it:

alias: "doorbell_automation"
trigger:
 - platform: state
   entity_id: binary_sensor.doorbell_contact
   to: 'off'
action:
 - service: media_player.turn_on
   entity_id: media_player.desktop_pc_thierry
   
 - service: media_player.turn_on
   entity_id: media_player.xbr_49x800e
   
 - service: media_player.volume_set
   data:
      entity_id: media_player.sony_xbr_55x800h
      volume_level: 0.6
      
 - service: media_player.volume_set
   data:
      entity_id: media_player.desktop_pc_thierry 
      volume_level: 0.6
      
 - service: media_player.volume_set
   data:
      entity_id: media_player..xbr_49x800e 
      volume_level: 0.6
      
 - service: media_player.play_media   
   entity_id: media_player.desktop_pc_thierry
   data:
       media_content_id: 'http://192.168.1.106:8123/local/mp3/doorbell.mp3'
       media_content_type: audio/mp4
   
 - service: media_player.play_media   
   entity_id: media_player.sony_xbr_55x800h
   data:
       media_content_id: 'http://192.168.1.106:8123/local/mp3/doorbell.mp3'
       media_content_type: audio/mp4
       
 - service: media_player.play_media
   entity_id: media_player.xbr_49x800e
   data:
      media_content_id: http://192.168.1.106:8123/local/mp3/doorbell.mp3
      media_content_type: 'audio/mp4'
      
 - service: notify.pushbullet
   data:
        title: 'Home assistant warning'
        message: 'On sonne à la porte !'

 - service: notify.email
   data:
       title: "Home assistant warning"
       message: "On sonne à la porte"        

The error in the log is:
doorbell_automation: Error executing script. Invalid data for call_service at pos 6: not a valid value for dictionary value @ data[‘entity_id’]

what does pos 6 means ?

Many thanks for your help, very apreciated.

Best regards

2 posts - 2 participants

Read full topic

I’ve had Home assistant running on my pi4B for a few months now, but in my experience, SD cards are just a massive failure waiting to happen at anytime. My HA monitors and controls over 75 devices and stores a lot of data as well.

I’d like to switch off my SD as soon as possible (if possible).

I’ve been doing some research on the forums and it seems a direct boot from the ssd isn’t fully operational just yet, or it lacks support in some areas. I’m fine with just the OS running on the SD but I’d like all my HA data managed, controlled, and stored on the SSD.

This is where I’m getting lost with the many topics posted about this — there’s a lot. Could someone point me in the right direction to have the most stable instance of home assistant running (full install), either fully off my SSD, or boot to the SD and everything else off the SSD?

Also, something I’ve noticed is, many people are taking about SATA cables from USB. Is there a reason a direct USB external SSD drive wouldn’t work? Is it a power issue?

Thanks.

1 post - 1 participant

Read full topic

Hello,

I have an automation to turn on my driveway lights when motion is detected on a couple of ring cameras. In the YAML I’m using two different methods to trigger the action.

Can someone explain why the first is working but not the second?

entity_id: binary_sensor.stable_motion
from: 'off'
platform: state
to: 'on'

device_id: bc6f1721f71b44ef9d9452b908e39a09
domain: binary_sensor
entity_id: binary_sensor.gate_motion
platform: device
type: motion

2 posts - 2 participants

Read full topic

I have a couple of greeting automations, but they’ve been giving me some issues. First off, for a device tracker, I have both the android app, and also wifi presence detection using asuswrt. I know there’s been an issue with the asuswrt integration lately, but I’ve manually updated asuswrt to 1.2.7 so it functions. Both device trackers are assigned to person.d34dc3n73r

The issue I’m having is that the automation action happens pretty much any time I open the door. I have a couple of wait conditions in the action that should prevent this, but it doesn’t seem to be working as rock-solid as I’d like. Can anyone point out the issue to me, or think of a better way to accomplish what I’m trying to do here?

- id: '1577515982557'
  alias: Say Hi
  trigger:
  - entity_id: binary_sensor.garage_entry
    platform: state
    to: 'on'
  action:
  - continue_on_timeout: 'false'
    timeout: 00:03:00
    wait_template: '{{ (as_timestamp(states.sensor.time.last_changed) - as_timestamp(states.person.d34dc3n73r.last_changed)) < 180 }}'
  - continue_on_timeout: 'false'
    timeout: 00:03:00
    wait_template: '{{ is_state(''person.d34dc3n73r'', ''home'') }}'
  - delay: 00:00:08
  - data_template:
      message: '{{ (''Sup bro'', ''Welcome home'', ''Hey dude hows it goin'', ''Whats shakin bacon'', ''Whats crackalackin'', ''whats-up buttercup'')|random }}'
    entity_id: media_player.kitchen_display
    service: tts.google_cloud_say

1 post - 1 participant

Read full topic

I have three heat pumps, two controlled by Broadlink with the smartir component (awesome) and the one in the lounge has been added to my Harmony remote. While they all work well, they are Home Assistant unaware as HA does not know if they are actually on. This creates a problem is someone turns on/off the heat pump with the remote.

I’ve added a Sonoff POW R2 with Tasmota inline with the lounge heat pump and now want to change my template switch so that power more than 5w is on otherwise off. Not quite sure how to do that though. I have these two sensors and the code for the harmony based climate follows that. If anyone can point me in the right direction, that would be appreciated.

## LOUNGE ##    
binary_sensor:
  - platform: template
    sensors:
      hvac_lounge_power_state:
        friendly_name: "HVAC Lounge Running"
        device_class: heat
        value_template: "{{ states('sensor.hvac_lounge_power')|float > 5 }}"

sensor:
## Sonoff POW R2 under house near heat pump ##
  - platform: mqtt
    name: "HVAC Lounge Power"
    state_topic: "tele/hvac_lounge/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Power"] }}'
    unit_of_measurement: "W" 

And here the the template switch that is integrated into the Generic Thermostat that I’m looking to modify.

switch:
  - platform: template
    switches:
      lounge_heat_pump:
        value_template: "{{ is_state('input_boolean.lounge_heat_pump', 'on') }}"
        turn_on:
          - service: input_boolean.turn_on
            entity_id: input_boolean.lounge_heat_pump
          - service: script.lounge_aircon_on
        turn_off:
          - service: input_boolean.turn_off
            entity_id: input_boolean.lounge_heat_pump
          - service: script.lounge_aircon_off

I tried replacing the value_template with "{{ is_state('binary_sensor.hvac_lounge_power_state', 'on') }}" but that did not work.

2 posts - 2 participants

Read full topic

Hey community,

Is it possible to override device type when exposing to Google assistant ?

For example i have Daikin AC which is used via Daikin integration.
So all Climate entities get exposed as action.devices.types.THERMOSTAT is it possible to
export my specific Daikin entity as action.devices.types.AC_UNIT instead?

I had similar problem with my coffee maker which currently exposes as a switch

Regards,

1 post - 1 participant

Read full topic

Hi folks, I have a similar request for help per this thread > Automation with DeepStack And Motions Sensors had in that I’m trying to fire deepstack object detection when my Arlo cameras detect motion.

I can’t seem to get my object detection to operate consistently. It worked okay yesterday with one camera, I applied the same automation to two other camera’s then my HA became unresponsive when I walked around the house to test it out. Perhaps it was a little too much for my poor old NUC?
In any case it’s just not working anymore… Any clues.
My approach:
I’m using this excellent integration:

and this:

my config.yaml snippet:

### ARLO SIDE (ARLO 4)
  - platform: local_file
    name: aarlo4snapshot
    file_path: /config/snapshots/arlo4/aarlo4snapshot.jpg
    
  - platform: local_file
    name: aarlo4deepstack
    file_path: /config/snapshots/arlo4/sideyard_latest.jpg
### Side Yard
  - platform: deepstack_object
    ip_address: 192.168.X.YY
    port: 5000
    api_key: randomstuffhere
    save_file_folder: /config/snapshots/arlo4
    show_boxes: true
    roi_x_max: 0.8
    roi_y_max: 0.8
    targets:
      - person
    source:
      - entity_id: camera.aarlo4snapshot
        name: sideyard

My automation:

- id: '1595199677892'
  alias: Arlo Detection Side
  description: ''
  trigger:
  - entity_id: binary_sensor.aarlo_motion_arlo4
    platform: state
    to: 'on'
### THIS WAS 'true' just changed it
  condition:
  - condition: state
    entity_id: alarm_control_panel.aarlo_doukiarlohub
    state: armed_away
  action:
  - data:
      entity_id: camera.aarlo_arlo4
      filename: /config/snapshots/arlo4/aarlo4snapshot.jpg
    service: aarlo.camera_request_snapshot_to_file
  - delay: 00:00:30
  - data: {}
    entity_id: image_processing.sideyard
    service: image_processing.scan
  - delay: 00:00:05
  - data:
      data:
        attachment:
          content-type: jpeg
        entity_id: camera.aarlo4deepstack
        push:
          category: camera
      message: Side Motion Detected Of Type {{ state_attr('image_processing.sideyard','summary')
        }} {{now().strftime("%H:%M:%S %d-%m-%Y")}}.
    service: notify.mobile_app_my_iphone

aarlo4snapshot.jpg is being written into the /config/snapshots/arlo4 folder okay (and subsequent camera.aarlo4snapshot is being created, image appears fine from the camera).

But the sideyard_latest.jpg isn’t being generated.
(nor is it for the other three Arlo’s anymore).

I’m sure it’s a simple issue, but can’t see it anymore…

When I run the image through deepstack via curl cli I get “success”:true… Processing takes about 1-2 seconds. the image sizes from the Arlo are ~80-100kb and are in .jpeg format okay.

What silly mistakes am I making?!

Thanks in advance,

1 post - 1 participant

Read full topic

Dear All,

I am trying to configure Certificate Expiry to monitor some of my server’s certificate’s expiration.

These servers are remote, not on the same local network as my HA. I am using Cloudflare to ‘protect’ the websites hosted on these servers and set up Strict SSL for them (with proxying DNS). This means that the HTTPS connection is terminated on CF’s server and another is created from CF to my server. I am looking for the certificate expiration for the second connection.

If I enter the original hostname, HA would show the expiration for the certificate from CF and not my certificate.

A solution would be to configure Certificate Expiry with the IP address, but it results in an error: IP address mismatch, certificate is not valid for ‘123.123.123.123’.
Is there any way to work around this? I did not see any option to override these type of errors.

Thanks,

David

1 post - 1 participant

Read full topic

Hi, I have a strange problem where my automation triggers when a sensor becomes unavailable even though the trigger config is set to only fire when the state goes from off to on.

  trigger:
    - platform: state
      entity_id: binary_sensor.door
      from: 'off'
      to: 'on'

When looking at the state history for the sensor I cannot see any state history that is ‘on’ but the automation fired when going from ‘off’ to ‘unavailable’. This should not happen with the config above, right?! Any thoughts?

1 post - 1 participant

Read full topic

Hi all,

I’ve been gradually migrating all of my Tuya devices over to Tasmota, with the intention of using them in conjunction with Home Assistant Cloud to make my house less dependent on third-party services (i.e. SmartLife!). So far, it’s been a huge success and I remain in awe of the quality of both Home Assistant and Tasmota to make a really robust platform.

I’ve hit one slightly annoying bug though, which I can’t figure out and I’m hoping someone here can help.

I have a few bulbs that are RGBW (i.e. RGB + cold white) that, after a bit of mucking about, are correctly mapped in HA. I can open the entity and set the colour and also, more importantly, control the white channel. So when asking for red from the HA UI, the Tasmota console correctly reports that the right RGBW value is being requested:

321×665

11:30:51 MQT: stat/kitchentablelamp/RESULT = {"POWER":"ON","Dimmer":100,"Color":"255,0,0,0","HSBColor":"0,100,100","White":0,"Channel":[100,0,0,0]}

…and when asking for white, it correctly turns off the RGB channels and just enables the W channel at 100%:

323×672

11:32:40 MQT: stat/kitchentablelamp/RESULT = {"POWER":"ON","Dimmer":100,"Color":"0,0,0,255","HSBColor":"0,0,0","White":100,"Channel":[0,0,0,100]}

These colours are also correctly displayed on the lamp.

The problem I have is that when I ask Google Assistant to “set lamp to white”, as I would previously have done with SmartLife, it only triggers a regular RGB value to be configured on the bulb. e.g.

326×671

11:37:36 MQT: stat/kitchentablelamp/RESULT = {"POWER":"ON","Dimmer":100,"Color":"255,221,172,0","HSBColor":"35,33,100","White":0,"Channel":[100,87,67,0]}

This results in a rather dim, muddy colour on the bulb rather than the normal, bright-white that the bulb should put out. This also happens if you ask for “bright white” (which sets the RBG to #FFFFFF, but still doesn’t set the white channel).

It looks like the HA / GA integration isn’t correctly advertising the capability of the bulb to Google, but I’m somewhat stumped as to how to fix this.

Suggestions welcomed!

1 post - 1 participant

Read full topic

I added two template fans some time ago to HomeAssistant (controlled via Broadlink remotes):

fan:
  - platform: template
    fans:
      living_room_fan:
        friendly_name: "Living Room Fan"
        value_template: "{{ states('input_boolean.living_room_fan_power') }}"
        speed_template: "{{ states('input_text.living_room_fan_speed') }}"
        turn_on: 
          - service: script.living_room_fan_on
        turn_off:
          - service: script.living_room_fan_off
        set_speed:
          - service: script.living_room_fan_set_speed
            data_template:
              speed: "{{ speed }}"
        set_direction:
          - service: script.living_room_fan_reverse
        speeds:
          - '0'
          - '1'
          - '2'
          - '3'
          - '4'
          - '5'

The fans are exposed to Google Assistant through Nabu Casa and all worked correctly.

As of this morning, I’ve noticed that both fans are permanently shown as ‘On’ in Google Home.
They are still represented correctly in Google Home.

Is anyone else seeing the same?

1 post - 1 participant

Read full topic

Hi All,

I have recently installed Mosquitto Broker and Paradox IP150 MQTT Adapter after which I was able to configure them to get a view on my lovelace with Paradox alarm status

Problem is every 10-15 sec the virtual keyboard flashes for 1-2 secs on lovelace, on web and app.

I can only see the DISARM button but it doesnt do anything when pressed

My entity view shows the Filter state for [alarm_control_panel.house_paradox] shows as unavailable but again every 10-15sec it would flash to unknown state

My Entities page :

Entities Page1646×208 7.3 KB

I hope looking at the above someone is able to provide some direction?

Moreover I can share my logs if that helps as well

Here are some logs

Paradox IP150 MQTT Adapter

    byte = self._sock_recv(1)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 660, in _sock_recv
    return self._sock.recv(bufsize)
AttributeError: 'NoneType' object has no attribute 'recv'
Traceback (most recent call last):
  File "ip150_mqtt.py", line 140, in <module>
    ip_mqtt.loop_forever()
  File "ip150_mqtt.py", line 133, in loop_forever
    mqc.loop_forever()
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1782, in loop_forever
    rc = self.loop(timeout, max_packets)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1177, in loop
    rc = self.loop_read(max_packets)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1568, in loop_read
    rc = self._packet_read()
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 2271, in _packet_read
    byte = self._sock_recv(1)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 660, in _sock_recv
    return self._sock.recv(bufsize)
AttributeError: 'NoneType' object has no attribute 'recv'
Traceback (most recent call last):
  File "ip150_mqtt.py", line 140, in <module>
    ip_mqtt.loop_forever()
  File "ip150_mqtt.py", line 133, in loop_forever
    mqc.loop_forever()
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1782, in loop_forever
    rc = self.loop(timeout, max_packets)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1177, in loop
    rc = self.loop_read(max_packets)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1568, in loop_read
    rc = self._packet_read()
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 2271, in _packet_read
    byte = self._sock_recv(1)
  File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 660, in _sock_recv
    return self._sock.recv(bufsize)

Mosquitto broker

1595242856: Client auto-2F98261D-0D3C-9769-0E38-8103295BD11E disconnected.
1595242881: New connection from 172.30.33.3 on port 1883.
1595242881: New client connected from 172.30.33.3 as auto-C1EF3631-3A09-D950-A7F3-4CE1EA521AC5 (p2, c1, k60, u'MQTTuser').
1595242882: Client auto-C1EF3631-3A09-D950-A7F3-4CE1EA521AC5 disconnected.
1595242907: New connection from 172.30.33.3 on port 1883.
1595242907: New client connected from 172.30.33.3 as auto-14735070-1FAA-91EB-A29B-75D532B5F2B3 (p2, c1, k60, u'MQTTuser').
1595242908: Client auto-14735070-1FAA-91EB-A29B-75D532B5F2B3 disconnected.
1595242933: New connection from 172.30.33.3 on port 1883.
1595242933: New client connected from 172.30.33.3 as auto-836129A9-EF04-6CAE-9701-8878C76E41A8 (p2, c1, k60, u'MQTTuser').
1595242934: Client auto-836129A9-EF04-6CAE-9701-8878C76E41A8 disconnected.
1595242958: New connection from 172.30.33.3 on port 1883.
[INFO] found MQTTuser on local database
1595242960: New client connected from 172.30.33.3 as auto-F87A336B-4E52-22D5-DEDF-1E6B6C23B274 (p2, c1, k60, u'MQTTuser').
1595242961: Client auto-F87A336B-4E52-22D5-DEDF-1E6B6C23B274 disconnected.
1595242986: New connection from 172.30.33.3 on port 1883.

2 posts - 1 participant

Read full topic

Hi All,

Can someone help me out? I think I can’t see the problem anymore. This part of automation is not woking
When automation has been triggered after 10 seconds the script is going on. It won’t wait for the wait part that the front door has been status ‘on’

entity

friendly_name: Fibaro Frontdoor
device_class: door
templates:
  icon_color: >-
    if (state === 'on') return 'rgba(251,214,67,1)'; return
    'rgba(71,116,157,1)';
icon_color: 'rgba(71,116,157,1)'

state

on

automation part

  action:
    - wait_template: >-
        {{ (states("binary_sensor.fibaro_frontdoor_custom_sensor") == 'on') }}
    - delay: "00:00:10"

full automation:

###########################################################################################
# NOTIFY and GREETS PERSON WHO WENT HOME
###########################################################################################

- alias: "Notify - Greets People Home"
  trigger:

    - platform: state
      entity_id:
        - input_boolean.peter_home_manual
        - input_boolean.kay_home_manual
      from: "off"
      to: "on"

  action:
    - wait_template: >-
        {{ (states("binary_sensor.fibaro_frontdoor_custom_sensor") == 'true') }}

    - delay: "00:00:10"

      ###########################################################################################
      # GROUP.ARRIVING is created in create_arrive_group.yaml
      ###########################################################################################
    - service: script.engine_say
      data_template:
        personarriving: >-
          {% set person = expand('group.arriving')|map(attribute='name')|join(' and ') %}
          {% set peoplecount = expand('group.arriving') | count %}
          {% if peoplecount == 1 %}
            {% set is_are = ' is ' %}
          {% else %}
            {% set is_are = ' are ' %}
          {% endif %}

          {%- macro greeting_sentence(person, is_are) -%}
          {{ [
            "Welcome back home " ~ person,
            "You had me at hello " ~ person,
            "Guess who is home? " ~ person ~ is_are ,
            "The wifi just got a little more crowded.  Welcome Home " ~ person,
            "Welcome Home " ~ person + ".  We have missed you. Or at least Molly did.",
            "Our home is now complete, Rest your head and relax your feet! Welcome Back " ~ person,
            "Life is like a song, you’re back where you belong. Welcome home " ~ person,
            "Hey there " ~ person + " Welcome Home!",
            "Knock Knock. Who is There? "   ~ person  ~ is_are ,
            "The front door just told me that " ~ person  ~ is_are +" home.",
            "I know a secret! "  ~ person  ~ is_are +" home!",
            "Hey "  ~ person +". Your arrival has been recorded by the Smartest house on the block.",
            "Take note Molly! "  ~ person  ~ is_are +" home.",
            "I am sensing a disturbance in the force. "  ~ person +" must be home!",
            "And the house becomes a home. Welcome back " ~ person,
            "Just a quick announcement. " ~ person +" has arrived!",
            "Hey " ~ person + "! High Five! Glad you are finally home.",
            "Pardon the interruption but " ~ person ~ is_are +" home!",
            "My systems are picking up the presence of additional humans. " ~ person  ~ is_are +" being identified as home.",
            "Welcome home "~person + "! It is nice to see you again! Let me turn on the lights. ",
            "It looks like "~person ~ is_are + " finally home! I will get the house ready for you. ",
            person  ~ is_are + " now in the house.",
            person + " can not hide from the system. Welcome home.",
            person ~ "! You are home!",
            person  ~ is_are + " now here.  Hash tag Welcome Home.",
            person  ~ is_are + " now here.  Hash tag Home.",
            person  ~ is_are + " now here.  Hash tag Smart Home."
          ] | random }}
          {%- endmacro -%}
          {{greeting_sentence(person, is_are)}}

    - service: group.set
      data_template:
        object_id: "arriving"
        entities: []

6 posts - 2 participants

Read full topic

Hi,

Hope someone can help me out with this annoying configuration issue.
It used to work fine, but it looks like since 0.112 this issue started to appear.

I use the custom vertical stack in card inside the horizontal stack to make a grid with buttons in the center of a Lovelace view.
Problem is that right now it does not stay in the center.
I used th fix that by using the gap card on top to space out from the top.
It used to look like this:

Screenshot 2020-07-20 at 14.10.332126×688 152 KB

Screenshot 2020-07-20 at 14.10.082104×1050 237 KB

cards:
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:office-building'
        show_name: false
        show_state: false
        tap_action:
          action: navigate
          navigation_path: /hub-panel/office
        template: template_office
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.window_sensor_office
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:window-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:window-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: media_player.sonos_kantoor
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:speaker'
                value: playing
              - color: '#8C8C8C'
                icon: 'mdi:speaker-off'
                value: paused
              - color: '#8C8C8C'
                icon: 'mdi:speaker-off'
                value: idle
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
        align: center
    type: 'custom:vertical-stack-in-card'
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:shower'
        show_name: false
        show_state: false
        tap_action:
          action: navigate
          navigation_path: /hub-panel/bathroom
        template: template_bathroom
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.motion_sensor_bathroom
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:run'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:walk'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: media_player.sonos_badkamer
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:speaker'
                value: playing
              - color: '#8C8C8C'
                icon: 'mdi:speaker-off'
                value: paused
              - color: '#8C8C8C'
                icon: 'mdi:speaker-off'
                value: idle
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    style: |
      ha-card {
        font-variant: small-caps;
        --paper-card-background-color: rgba(34, 34, 34, .2);
        background-repeat: no-repeat;
        background-color: rgba(50,50,50,0.3);
        background-size: 100% 68px;
        border-radius: 5px;
        }
      .card-header {
        font-size: 20px;
      }
    type: 'custom:vertical-stack-in-card'
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:washing-machine'
        show_name: false
        show_state: false
        styles:
          card:
            - border-radius: 0px
            - font-variant: small-caps
            - background-color: 'rgba(50,50,50,0.3)'
            - background-size: 100% 68px
        tap_action:
          action: navigate
          navigation_path: /hub-panel/attic
        template: template_attic
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.d1_mini_pir_attic
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:run'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:walk'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            entity: binary_sensor.door_sensor_attic_door
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:door-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:door-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.window_sensor_attic
            icon: 'mdi:window-open'
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:window-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:window-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    style: |
      ha-card {
        font-variant: small-caps;
        --paper-card-background-color: rgba(34, 34, 34, .2);
        background-repeat: no-repeat;
        background-color: rgba(50,50,50,0.3);
        background-size: 100% 68px;
        border-radius: 5px;
        }
      .card-header {
        font-size: 20px;
      }
    type: 'custom:vertical-stack-in-card'
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:flower-tulip-outline'
        show_name: false
        show_state: false
        tap_action:
          action: navigate
          navigation_path: /hub-panel/garden
        template: template_back_garden
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.door_sensor_back_door
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:door-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:door-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            entity: sensor.outside_temperature
            show_name: false
            show_state: true
            styles:
              card:
                - padding: 11px 0px
                - font-size: 10px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: light.achtertuin_gevel
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:coach-lamp'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:coach-lamp'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    type: 'custom:vertical-stack-in-card'
type: horizontal-stack

and

cards:
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:door'
        show_name: false
        show_state: false
        styles:
          card:
            - border-radius: 0px
            - font-variant: small-caps
            - background-color: 'rgba(50,50,50,0.3)'
            - background-size: 100% 68px
        tap_action:
          action: navigate
          navigation_path: /hub-panel/hallway
        template: template_hallway
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.motion_sensor_hallway
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:run'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:walk'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.door_sensor_front_door
            icon: 'mdi:door'
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:door-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:door-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: switch.socket_relay_hallway
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:coach-lamp'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:coach-lamp'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    style: |
      ha-card {
        font-variant: small-caps;
        --paper-card-background-color: rgba(34, 34, 34, .2);
        background-repeat: no-repeat;
        background-color: rgba(50,50,50,0.3);
        background-size: 100% 68px;
        border-radius: 5px;
        }
      .card-header {
        font-size: 20px;
      }
    type: 'custom:stack-in-card'
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:stairs'
        show_name: false
        show_state: false
        styles:
          card:
            - border-radius: 0px
            - font-variant: small-caps
            - background-color: 'rgba(50,50,50,0.3)'
            - background-size: 100% 68px
        tap_action:
          action: navigate
          navigation_path: /hub-panel/upstairs-hallway
        template: template_upstairs_hallway
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.motion_sensor_upstairs_hallway
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:run'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:walk'
                value: 'off'
            styles:
              card:
                - height: 50px
                - padding: opx px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    style: |
      ha-card {
        font-variant: small-caps;
        --paper-card-background-color: rgba(34, 34, 34, .2);
        background-repeat: no-repeat;
        background-color: rgba(50,50,50,0.3);
        background-size: 100% 68px;
        border-radius: 5px;
        }
      .card-header {
        font-size: 20px;
      }
    type: 'custom:stack-in-card'
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:bed-queen-outline'
        show_name: false
        show_state: false
        styles:
          card:
            - border-radius: 0px
            - font-variant: small-caps
            - background-color: 'rgba(50,50,50,0.3)'
            - background-size: 100% 68px
        tap_action:
          action: navigate
          navigation_path: /hub-panel/bedroom
        template: template_master_bedroom
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            entity: sensor.temperature_master_bedroom
            show_name: false
            show_state: true
            styles:
              card:
                - padding: 12px 0px
                - font-size: 10px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.window_sensor_master_bedroom
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:window-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:window-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    style: |
      ha-card {
        font-variant: small-caps;
        --paper-card-background-color: rgba(34, 34, 34, .2);
        background-repeat: no-repeat;
        background-color: rgba(50,50,50,0.3);
        background-size: 100% 68px;
        border-radius: 5px;
        }
      .card-header {
        font-size: 20px;
      }
    type: 'custom:stack-in-card'
  - cards:
      - aspect_ratio: 3/2
        color_type: icon
        icon: 'mdi:tshirt-crew-outline'
        show_name: false
        show_state: false
        tap_action:
          action: navigate
          navigation_path: /hub-panel/walk-in-closet
        template: template_walk_in_closet
        type: 'custom:button-card'
      - cards:
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.motion_walk_in_closet
            icon: 'mdi:run'
            show_name: false
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:run'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:walk'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            color_type: null
            template: template_security
            type: 'custom:button-card'
          - aspect_ratio: 3/3
            color: auto
            entity: binary_sensor.window_sensor_walk_in_closet
            icon: 'mdi:window-open'
            name: ' '
            show_state: false
            state:
              - color: '#216491'
                icon: 'mdi:window-open'
                value: 'on'
              - color: '#8C8C8C'
                icon: 'mdi:window-closed'
                value: 'off'
            styles:
              card:
                - height: 50px
            template: template_security
            type: 'custom:button-card'
        type: horizontal-stack
    style: |
      ha-card {
        font-variant: small-caps;
        --paper-card-background-color: rgba(34, 34, 34, .2);
        background-repeat: no-repeat;
        background-color: rgba(50,50,50,0.3);
        background-size: 100% 68px;
        border-radius: 5px;
        }
      .card-header {
        font-size: 20px;
      }
    type: 'custom:stack-in-card'
type: horizontal-stack

Maybe I can fix this by a trick to force the cards to stay in the center. If there is one, I’d love to know.
Otherwise I’d like to combine both cards into one so this layout issue will not appear.

Maybe a long post, but I hope someone can help me. Thank you in advance!

1 post - 1 participant

Read full topic

I recently removed some LIFX bulbs from my smart home. I deleted them in the LIFX app but they remain in Home Assistant and I’m not sure how to remove them. HA shows 8 devices while the LIFX app correctly shows 5.

1 post - 1 participant

Read full topic