@beeper wrote:

Hello All - I’m very new to Home Assistant, and trying to produce an automation that will trigger a pushbullet alert after a period of time when no motion is detected.
I’ve successfully managed to trigger the alert on motion detection, but really struggling with firing the alert after no motion.

- id: 'xxxx'
  alias: Alert when no motion detected
  description: ''
  trigger:
  - device_id: xxxx
    domain: binary_sensor
    entity_id: binary_sensor.tradfri_motion_sensor
    for:
      hours: 0
      minutes: 0
      seconds: 0
    platform: device
    type: no_motion
  condition: []
  action:
  service: notify.mypushbullet
  data:
    title: "Inactivity Alert"
    message: "No motion detected"

The log is pointing to a config error:

Invalid config for [automation]: [service] is an invalid option for [automation]. Check: automation->service. (See /config/configuration.yaml, line 13).

Can anyone advise me? Is it possible to do what I want to do? Thanks for any help!

Posts: 3

Participants: 2

Read full topic

@DeanLongstaff wrote:

Hi,

I have a tasmota switch which is attatched to my 3D Printer. I want to be able to switch it on and off, but not for it to be accidentaly switched off when it is printing. Is there a way for me to have something popup and say “Are you sure you want to turn this off”?

I know i could do it with a switch template and have 2 different switches but that seems a bit clunky.

Thanks

Posts: 2

Participants: 2

Read full topic

@costy wrote:

After the last update to 0.105.5 I get the following error:

In configuration.yaml I have this:
automation: !include automations.yaml

I need help.
THX

Posts: 3

Participants: 2

Read full topic

@k2v1n58 wrote:

We are many to use tablet or Android devices for our Home Assistant.
Thanks to its development console, Android allows us to access and modify the parameters (hardware and software). Here’s how to access to them and take control of your Android device:

1. ADB over TCP
   The first step is to active the Android Debug Bridge (ADB) over TCP
   See Enabling developer mode on your device from this page https://github.com/hassio-addons/addon-adb.
   If the Network debugging is not available on your device, follow tutorials on internet or connect your device to your computer and with the terminal set this command:

   adb tcpip 5555

2. Install ADB server
   Follow instructions here: https://github.com/hassio-addons/addon-adb/

3. Configure Home Assistant
   Follow instructions here: https://www.home-assistant.io/integrations/androidtv/
   Then, restart and a new media_player should appear

4. Tests and use
   From the androidtv.adb_command service, we can try the different commands. GET commands will display properties in device’s state.
   I give some example here that can be use in automations and scripts:

   • Get screen brightness

     entity_id: media_player.xxx
     command: settings get system screen_brightness

   • Set screen brightness

     entity_id: media_player.xxx
     command: settings put system screen_brightness {value}

     The screen backlight brightness between 0 and 255

   • Get screen brightness mode

     entity_id: media_player.xxx
     command: settings get system screen_brightness_mode

   • Set screen brightness

     entity_id: media_player.xxx
     command: settings put system screen_brightness_mode

     Supported values are 0 for manual and 1 for automatic

   • Get stay on while plugged in

     entity_id: media_player.xxx
     command: global get system stay_on_while_plugged_in

   • Set stay on while plugged in

     entity_id: media_player.xxx
     command: global put system stay_on_while_plugged_in {value}

     Supported values are:

     • 0 to never stay on while plugged in
     • BatteryManager#BATTERY_PLUGGED_AC to stay on for AC charger
     • BatteryManager#BATTERY_PLUGGED_USB to stay on for USB charger
     • BatteryManager#BATTERY_PLUGGED_WIRELESS to stay on for wireless charger

   • Turn off the screen by simulating a press on the Power Button

     entity_id: media_player.xxx
     command: input keyevent 26

   • Start and kill an app (example with Home Assistant Companion for Android)

     entity_id: media_player.xxx
     command: am force-stop io.homeassistant.companion.android

     entity_id: media_player.xxx
     command: monkey -p io.homeassistant.companion.android 1

   • Turn off the screen in case of long press on the Hue remote:

       alias: Screens off after long press
       trigger:
       - entity_id: remote.remote
         platform: state
         to: 4_hold_up
       condition:
       - condition: template
         value_template: '{{ states("media_player.xxx") != "off" }}'
         # check current screen status
       action:
       - data:
           command: input keyevent 26
           entity_id: media_player.xxx
         service: androidtv.adb_command
     

All the ADB commands are accessible from developers Android website (https://developer.android.com/reference/android/provider/Settings.Global).
ADB over TCP offers unlimited possibilities (and for free). You can modify and read all hardware and software properties, and also simulate pressing buttons.

Posts: 2

Participants: 2

Read full topic

@klogg wrote:

I’ve just converted all my custom buttons from using templates to using the quite brilliant lovelace-gen as I thought that would give me more flexibilty. And in some ways it does.

But there is a big drawback in that you can’t pass any states into the button whereas in templates you can access them in the template itself.

It wasn’t a big task to change them so it’s not a big deal to change them back but before I do I just wondered what the panel thought?

Templates or lovelace-gen?

Posts: 10

Participants: 2

Read full topic

@bartus wrote:

The situation
For controlling the temperature in my home I own a couple of Popp-radiator thermostats. These devices are battery-operated Z-wave (not Z-wave-plus) devices and are set to wake up every five minutes.

In my front-end I have a switches for turning the thermostat on and off and sliders that set the temperature for the on and off state (these thermostats only have a temperature setting and no mode-setting).

The problem
All this is working like a charm, with one exception: when I toggle the switch, it will fall back to it’s original setting for the time that it takes for the zwave-device to wake up and receive the set_temperature command.

The question:
Would it be possible to show a notification, or a list of queued commands, or even set a custom ‘waiting’ sensor so that you can see that a command is send/queued to a device (and make it disappear when the command is received)?

What I have done so far:
I was able to set up an automation that listens to call_service event in the climate domain; this then triggers a notification that says that a command is waiting. i have not been able to make it say which entity is targeted or what command is being send to an entity. So basically I am stuck on

1. How to extract the entity_id from the service call (or any information at all)
2. How to match the call_event data with a changed temperature attribute state from the corresponding device.

All this is on a RPI-3 with hass-os and a zwave.me USB-stick.

Posts: 1

Participants: 1

Read full topic

@r100gs wrote:

Hello together,

I´m really a programming noob, but I like to tinker around with those homeautomation things.
I have homeassistant running (hass.io) and a raspberrymatic with my weatherman (stall.biz) connected to. The weatherman (I bought it from stall.biz) sends outside temperature to my raspberrymatic ccu3 as a system variable. The ccu3 is connected to homeassistant. This works great.
I connected some WLED-lights to my homeassistant setup. Now my idea is to read the outside temperature and sent it to wled (cold, warm, hot --> blue, green, red)
But I do not really know how to create a ccu-Sensor containing the temperature and than transfer it to a color and send it to wled.

Maybe it is easier to do in nodeRed?

Do you have some ideas?

Best regards,
Stefan

Posts: 1

Participants: 1

Read full topic

@Jack_Kitley wrote:

Hi All

Ive got a water meter that works on a pulse. For the current state its an int.
I would like to use history stats on water used for the day but im finding it difficult.

Is there any easy way to do this?

Screenshot 2020-02-19 at 16.58.47949×87 10.3 KB

Posts: 3

Participants: 3

Read full topic

@TimothyGaray wrote:

I am considering trying out a Sonoff iFan03 or something similar to control the fan. The only thing is the light control is only on/off from that I see online.

Has anyone implemented anything with that to allow dimming the light fixture? I wasn’t sure how it would work to add a Sonoff dimmer module on top of that.

Thanks!

-Tim

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

have a set of 6 binary_sensors like this:

      birthday_marijn:
        friendly_name: Marijn jarig
        value_template: >-
          {{ is_state('sensor.birthday_marijn','0')}}
        device_class: 'presence'
        entity_picture_template: >
          {{ state_attr('sensor.birthday_marijn','entity_picture')}}
        attribute_templates:
          days: >
            {{ states('sensor.birthday_marijn')}}
          years: >
            {{ state_attr('sensor.birthday_marijn','years')}}
          original_date: >
            {{ state_attr('sensor.birthday_marijn','original_date')}}
          type: >
            {{ state_attr('sensor.birthday_marijn','type')}}
          name: >
            {{ state_attr('sensor.birthday_marijn','persoon')}}
          event: "{{'jarig'}}"

unfortunately they dont update on startup, which is surprising, because the entity_id (sensor.birthday_marijn in this case) on which they are based is clear at all times. Why do I need to add the sensor in the entity_id field of the main config to make them update on startup?

secondly, as you can see I template a few attributes off off the same sensor. Wouldn’t it be nice to be able to set the id in a variable and reference that in the attribute_templates? Since it is one big template, I would have hoped that to be allowed/possible?

        attribute_templates:
          {% set id = 'sensor.birthday_marijn' %}
          days: >
            {{ states(id)}}
          years: >
            {{ state_attr(id,'years')}}
          original_date: >
            {{ state_attr(id,'original_date')}}
          type: >
            {{ state_attr(id,'type')}}
          name: >
            {{ state_attr(id,'persoon')}}
          event: "{{'jarig'}}"

@petro, I promised you a tag…

Posts: 2

Participants: 2

Read full topic

@gts250gamer101 wrote:

Hello everyone! Please bear with the lengthy post, I am completely new to Home Assistant and I would like to get some information from you guys in the community before I dive right in. If there is a better place to ask questions please let me know, I was informed that the Home Assistant community is great so I figured I’d post on here and ask!

So from the top, I am installing Home Assistant on a Ubuntu Server system using a guide I found online. I have a few main goals with Home Assistant, and the main idea here is that I can continue to build onto the system once it is in place, and add/remove/customize items as I see fit.

The first system I have to install is the thermostat, which is the most crucial part of the smart home in my setup. The thermostat in question is the Lennox iComfort S30. It’s basically an Android tablet mounted on the wall that connects via Wi-Fi and is not listed as compatible with Home Assistant in any way, due to its proprietary software. However, it IS compatible with Apple’s HomeKit, and from what I’ve read, HomeKit is compatible with Home Assistant (https://www.home-assistant.io/integrations/homekit_controller/). So I guess my question here is whether or not I can configure the thermostat via HomeKit on an iPhone connected to the local network, and then pair it to the Home Assistant? Theoretically I would like to remove the iPhone from the system entirely once it is integrated, as I have a separate LAN network for my Home Assistant/automation hardware.

Finally, I have one other thing that I would like to integrate, being some IP cameras that I set up on a few Raspberry Pi’s. I use motionEyeOS on the RPis, and a USB camera on one, and Pi-connector camera on the other. They work perfectly fine on their own, but I cannot find any documentation as to how it could be installed into Home Assistant, other than this GitHub page: https://github.com/hassio-addons/addon-motioneye, which claims that local cameras (referring to those connected to the RPis) cannot be used to send images to the Home Assistant software, which would render this entire thing pointless, as the goal here is to have it all managed from one app. There is a streaming URL that is encrypted with a username and password, and it outputs an image that refreshes around 15 times per second, (not 100% sure on that, and it is variable so I could turn it up/down as needed) that I think could be integrated to Home Assistant? For now I am not concerned with motion detection on Home Assistant, because I already have notifications set up in motionEye to send me alerts when motion is detected, but I would like to use some face identification addons in the future.

Finally, the easy parts that I am most excited for is the integration with my home SoundTouch systems – this looks really simple and straightforward, and PERFECT!!

Thank you all in advance for your help! I greatly appreciate it.

Posts: 1

Participants: 1

Read full topic

@fender4645 wrote:

Not sure if this is the right category so I apologize if it isn’t.

I’m currently running HA in a Docker container, managed by docker-compose. My typical workflow to update HA is:

1. docker stop home-assistant
2. docker rm home-assistant
3. docker-compose pull home-assistant
4. docker-compose up -d home-assistant

This gets me the latest HA core however the 3rd party Python dependencies listed in the component’s manifest are not updated to the version listed. For example, the August component has a dependency of py-august==0.14.0 however after pulling the latest image, I’m still only at py-august==0.8.1.

Is this expected behavior? The only reason I noticed this is that there was a bug recently fixed in the August component that also required a change in the 3rd party library.

Posts: 4

Participants: 2

Read full topic

@Bayou-Billy wrote:

Hi- I have two opengarage units monitoring two garages (attached and detached). I installed temperature sensors on both, and HA is retrieving those statistics. The configurations are identical other than the internal IP and the name. I even did a diff check:

Screenshot_20200219-105009_Chrome2773×718 323 KB

The issue is that Lovelace sees one as C and one as F, so they are getting put on different charts. Sometimes. When it does happen, it looks like this’

Screenshot_20200219-105045_Home Assistant1432×1831 291 KB

I also verified the states of the sensors with the dev tools just for good measure.

Screenshot_20200219-105127_Home Assistant1439×1876 314 KB

Screenshot_20200219-105112_Home Assistant1439×1855 328 KB

My HA is set in imperial and I’d like everything shown in F. What is going on that the sensors get treated differently?

Posts: 2

Participants: 2

Read full topic

@Taraman wrote:

Hi,

I’m just starting to setup HA and my first pieces of Hardware already give me headaches.
I configured Zigbee successfully with a CC2531 USB Stick, mosquitto and Zigbee2MQTT.
I Added an IKEA Remote and a OSRAM/Ledvance Wallplug.

To test, I set the remotes on/off button, to toggle the switch.
When press the button, the plug turns on. But when I press it again, it stays on instead of toggling to off.

The Logs show the following:

After first press:

zigbee2mqtt:debug 2020-02-19 17:55:05: Received Zigbee message from 'Ikea Remote', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 26569
zigbee2mqtt:info  2020-02-19 17:55:05: MQTT publish: topic 'zigbee2mqtt/Ikea Remote', payload '{"linkquality":55,"battery":74,"action":"toggle"}'
zigbee2mqtt:info  2020-02-19 17:55:05: MQTT publish: topic 'zigbee2mqtt/Ikea Remote', payload '{"linkquality":55,"battery":74,"action":""}'
zigbee2mqtt:debug 2020-02-19 17:55:05: Received MQTT message on 'zigbee2mqtt/0x7cb03eaa0a07f261/set' with data 'ON'
zigbee2mqtt:debug 2020-02-19 17:55:05: Publishing 'set' 'state' to 'Schalter 1'
zigbee2mqtt:info  2020-02-19 17:55:05: MQTT publish: topic 'zigbee2mqtt/Schalter 1', payload '{"state":"ON","linkquality":68}'
zigbee2mqtt:debug 2020-02-19 17:55:05: Received Zigbee message from 'Schalter 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 3 with groupID 0
zigbee2mqtt:info  2020-02-19 17:55:05: MQTT publish: topic 'zigbee2mqtt/Schalter 1', payload '{"state":"ON","linkquality":76}'

After Second press:

zigbee2mqtt:debug 2020-02-19 17:55:51: Received Zigbee message from 'Ikea Remote', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 26569
zigbee2mqtt:info  2020-02-19 17:55:51: MQTT publish: topic 'zigbee2mqtt/Ikea Remote', payload '{"linkquality":21,"battery":74,"action":"toggle"}'
zigbee2mqtt:info  2020-02-19 17:55:51: MQTT publish: topic 'zigbee2mqtt/Ikea Remote', payload '{"linkquality":21,"battery":74,"action":""}'
zigbee2mqtt:debug 2020-02-19 17:55:51: Received MQTT message on 'zigbee2mqtt/0x7cb03eaa0a07f261/set' with data 'ON'
zigbee2mqtt:debug 2020-02-19 17:55:51: Publishing 'set' 'state' to 'Schalter 1'
zigbee2mqtt:info  2020-02-19 17:55:51: MQTT publish: topic 'zigbee2mqtt/Schalter 1', payload '{"state":"ON","linkquality":76}'

When I turn the plug off with the switch on it’s side:

zigbee2mqtt:debug 2020-02-19 17:57:11: Received Zigbee message from 'Schalter 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 3 with groupID 0
zigbee2mqtt:info  2020-02-19 17:57:11: MQTT publish: topic 'zigbee2mqtt/Schalter 1', payload '{"state":"OFF","linkquality":73}'

So somehow, after toggling it to on, the state does not seem to be saved, although the device reports correctly.

Am I missing something obvious?

Posts: 1

Participants: 1

Read full topic

@eric-radiant wrote:

I put hacs in where I think it should be:

~/docker/homeassistant$ ls
automations.yaml  configuration.yaml  custom_components  deps  groups.yaml  home-assistant_v2.db  scenes.yaml  scripts.yaml  secrets.yaml  tts
~/docker/homeassistant$ ls custom_components/
hacs

I restarted (both with the UI and restarting the docker container)

The UI doesn’t list the integration, so I added it to configuration by hand.

but get:

"Setup failed for hacs: Integration not found."

Posts: 1

Participants: 1

Read full topic

@stuiow wrote:

OK,
Dipping my toe into Home Assistant from Domoticz.

I have moved 2 z-wave devices over to home assistant, a z-wave motion sensor and a z-wave fibaro dimmer 2 relay.
What i need is to sort out an automation where 30 mins after sunset and 30 minutes before, if motion is detected on the PIR, activated the dimmer relay at 5% power and keep that on until motion has stopped for 2 minutes.

How would i achieve this in home assistant?
I’m not seeing any examples of this with light levels, i am seeing on and off.

Must say, i have only moved over 2 nodes so far to the z-wave and its so smooth, so far!
Stil have 90 odd nodes to move over, if i get this automation working well.

Posts: 4

Participants: 2

Read full topic

@Chapter wrote:

Hi,

I’m using a custom card but the following template is not working

        entity_picture: >
          [[[
            if (states['sensor.netatmo_rain'] <= 0)
              return `/local/icons/weather_icons/animated/day.svg`
            else
              return `/local/icons/weather_icons/animated/rainy-6.svg`
          ]]]

although the value of the sensor is 0 it shows always the “else” picture

Posts: 1

Participants: 1

Read full topic

@Stooovie wrote:

Hi, I have a chandelier with two yeelight bulbs. They’re grouped together for a simple wall switch to toggle it on/off.

There’s a second control - a Xiaomi button that’s set up for warm (single click), cool (double click) and turn off (hold).

Problem: I want to be able to control a single bulb (for super dim lighting) with triple click BUT it always triggers the second bulb as well. How to avoid this? I set the automation to specifically switch off the other bulb but it turns on anyway. The triple click is triggered correctly according to zigbee2mqtt. It is not limited to automations - when I toggle a single bulb manually, the other one toggles as well. I CAN control the bulbs independently via the Yeelight app so this is a HA problem.

Any tips?

Posts: 2

Participants: 2

Read full topic

@boneheadfraggle wrote:

is it possible to…

1. automatically refresh the gui when there is a newer version (instead of getting the notification “A new version of the frontend is available. RELOAD”
   and/or
2. setup a sensor that indicates when a reload is necessary - then I could trigger on that and reload the screen over mqtt (using https://github.com/thanksmister/wallpanel-android)
   the use case is for my dashboards where I use semi-broken cellphones as wallpanels. it’s hard to press reload without a working touchscreen

Posts: 1

Participants: 1

Read full topic

@xion2000 wrote:

Can I damage a plug or bulb by setting the wrong configuration in a template setup through TasmoAdmin.

I’ve recently flashed a selection of ESP chip based plugs using Tuya-Convert and I’ve just noticed that both avatar AWP14H plugs were not lighting the LED on the button but everything else was working OK. I’d copied the template from

So I’ve done some trial and error adjusting and now have one working, but not the other?
strange I thought as they appear identical and were bought together.
Anyway, possibly a bit late it dawned on me that I could have damaged the LED on the plug when I was changing settings. Is that possible?

Posts: 1

Participants: 1

Read full topic