@jjross wrote:

Is anyone else using the “recollect_waste” platform? I set up the sensor per the docs and it’s getting the information correctly (which is great); the issue is that it doesn’t seem to refresh regularly unless I restart HA.

When I first start up the data is correct but it keeps the current garbage day in the sensor until I restart again. The docs don’t mention having to call a service to get it to update so I think it might be broken. Can anyone confirm?

Posts: 1

Participants: 1

Read full topic

@finity wrote:

In the vein of the recent “PSA’s” I thought I would add one based on my experience trying to help someone out in another thread.

I’m cross posting it here to call attention to this inconsistent behavior to warn others and to figure out if I had done something wrong as the reason it didn’t work.

in that thread the other user was trying to use their old scripts but also create new scripts in the UI editor.

So to help out I changed my config to have it point to my existing scripts folder using “script old:” and then using "script: " to point to scripts.yaml.

Everything went well and it all worked even after manually adding a script to (previously empty) scripts.yaml file. But then when I added a script using the UI editor suddenly all of my existing manually created scripts were no longer accessible in HA.

Here is the bottom line from that thread:

Well…I made some assumptions that the automation editor and script editor work flow would be the same.

That assumption was completely incorrect!

Apparently the way the script editor works is different than the way the automation editor works when related to the old existing stuff in your config.

The docs for the automation editor says you can keep your old existing automations separately from your automations created by the editor by adding an “extender” name onto the existing “automation:” entry. the docs recommend adding “old” onto it like “automation old:”.

But that doesn’t work at all for the script entry for scripts added using the UI scripts editor.

I just tested adding a script in the UI editor and using the equivalent config for the one recommended for automations and it ended up killing all of my old scripts.

So, yeah, the bottom line is don’t do that.

What’s strange is that you can add the “script old:” entry and it will still reference all of the included files in the “script old:” and also in the “script:” locations just fine.

BUT as soon as you create a script in the UI editor that then gets added to your “scripts.yaml” file then none of the scripts located in the “script old:” location are recognized any more.

Reloading scripts or restarting HA won’t fix it either. The only way I could get my old scripts back was to remove the “script: !include scripts.yaml” entry and point it to my old scripts again using “script: !include_dir_merge_named scripts/” and after a restart everything was back to normal again.

Did I do something wrong there, is this a bug that needs reported or is this one of those “design features”?

It doesn’t effect me at all since I never use the UI editor but it might effect others trying to do the same thing later.

Posts: 1

Participants: 1

Read full topic

@arvage wrote:

Hello all!
I implemented HA in my office and now I have an RFID for all my employees and it is working great.
there is a small problem where I can’t log people using the app to unlock the door when they don’t have their badge on them. so, is there any way to track who opened the door? like tracking a user/person interacting with a switch or light through the iOS app?

Thank you

Posts: 11

Participants: 5

Read full topic

@Cludch wrote:

Hey,

I was trying to set up a second home-assistant instance along my production one.
What I did, was to change the http.server_port to an unused port.
However, I cannot start the second instance due to a port already being used.

2020-02-20 19:22:44 INFO (MainThread) [homeassistant.setup] Setting up logger
hadev                 | Exception in thread Thread-3:
hadev                 | Traceback (most recent call last):
hadev                 |   File "/usr/local/lib/python3.7/threading.py", line 926, in _bootstrap_inner
hadev                 |     self.run()
hadev                 |   File "/usr/local/lib/python3.7/site-packages/pysonos/events.py", line 307, in run
hadev                 |     listener = EventServer(self.address, EventNotifyHandler)
hadev                 |   File "/usr/local/lib/python3.7/socketserver.py", line 452, in __init__
hadev                 |     self.server_bind()
hadev                 |   File "/usr/local/lib/python3.7/socketserver.py", line 466, in server_bind
hadev                 |     self.socket.bind(self.server_address)
hadev                 | OSError: [Errno 98] Address in use

To me, it seems that the sonos integration tries to create a port bind itself, which might already be used by the main instance?

Or am I missing something else? Is this a bad idea at all?
I am just trying to create an instance to experiment with my new lovelace configuration.

Thanks in advance,
Cludch

Posts: 6

Participants: 4

Read full topic

@henaa wrote:

Hi
I have some issue I create ping request to show if the TV on or off
I used esp8226 with tasmosta and Broadlink
In the configuration.yaml this my code

binary_sensor:
  - platform: ping
    name: "living room tv state"
    host: 192.168.1.38
    count: 1
    scan_interval: 5

I create some Good night automation

- id: '1578133636557'
  alias: Good Night
  description: ''
  trigger:
  - entity_id: binary_sensor.switch_158d00027bf8e8
    from: 'off'
    platform: state
    to: 'on'
  condition: []
  action:
  - data:
      entity_id: switch.living_room_tv_fused
    service: switch.turn_off

The problem if the TV turn on its wotk good but if the TV is turn off and i used the automation its turn on the TV

what you suggest to fix this isuue?

Posts: 1

Participants: 1

Read full topic

@skycryer wrote:

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

Posts: 1

Participants: 1

Read full topic

@superm1 wrote:

A few days ago I installed a Kwikset 914 (zwave). I set up some automations related to locking the door at bedtime and when we leave the house and unlocking when we come home.
I’m finding that the battery is going down really fast though. I went from 100% to 70% and it’s been maybe 4 days. I’m a bit worried it’s draining too quick.

I didn’t see any options related to poll rate or anything like that though, so what are my options? It’s around lots of other zwave devices so I would think distance relaying back to the controller would be the problem.

Any thoughts?

Posts: 9

Participants: 3

Read full topic

@steadi wrote:

Hi,

Been working on a binary sensor to show “on” when anyone of the household is at home. My attempts so far haven’t worked.

I have the following code:

- platform: template 
  sensors: 
    house_occupation_status:
      friendly_name: "Occupation status"
      value_template: >-
        {{ is_state('person.pete', 'home') or
        is.state('person.2', 'home') }}

The code above kept showing “on”, so created a simpler, test sensor to test if it actually worked.

- platform: template 
  sensors:
    test_sensor:
      value_template: >-
        {{ is.state('person.pete', 'home') }}

The test sensor is “off” all the time, even though I am at home. And my person is registered showing as home in HA.

I’m new to HA, so am having trouble deciphering where I’m going wrong - any help is appreciated.

Thanks,

Posts: 3

Participants: 2

Read full topic

@Lorant wrote:

Hi

I’ve a sensor who detect if the window is opened, and in that case will ask a Shelly relay to switch off heating, then switch on when window is closed.

I’ve done two automations, I’m interested to know if that can be achieved with only one ?

Automations

  trigger:
  - entity_id: binary_sensor.door_window_sensor_1
    for: '10'
    from: 'off'
    platform: state
    to: 'on'
  condition: []
  action:
  - device_id: 257e0468e7004d109ae999e65d60b
    domain: switch
    entity_id: switch.shellyPM
    type: turn_off

And

  - entity_id: binary_sensor.door_window_sensor_1
    for: '10'
    from: 'on'
    platform: state
    to: 'off'
  condition: []
  action:
  - device_id: 257e0468e7004d109ae999e65d60b
    domain: switch
    entity_id: switch.shellyPM
    type: turn_on

Thanks

Posts: 9

Participants: 2

Read full topic

@belljaf wrote:

I have a z-wave network that comprises a z-wave.me stick running through ZHA with multiple Aeotec nano dimmers. I have recently bought a Nodon Wall switch CWS-3-1-0x to use as a secondary wall switch. I plan to use one switch to control two sonoff lamps through an automation and the other switch to control a nano dimmer.

I have setup the Nodon wall switch using this user guide and I have managed to capture an input to use as a trigger in home assistant in two ways:

• Setting the switch to “scene mode” and using the zwave.scene activated event
• Setting the switch “duo” or “mono” mode and then associating the appropriate group with the controller and using the zwave.node event trigger.

Both of these methods work fine for simple on/off however this adds a delay to the light going on/off and additional points of failure as the message has to go Wall switch -> Zwave.me -> HASS -> Zwave.me -> Nano dimmer. I would rather associate the wall switch directly with the nano dimmer so the message can be Wall switch -> Nano dimmer. Then if Homassistant goes down the light switch will still work.

However when if I set the button 1+3 profile to “duo” (Parameter 1, value 2) and then add the Nano dimmer to association group 6 (Button 1+3 duo controlled nodes) of the Nodon wall switch it doesn’t work.

The OZW logs show the switch waking and then going back to sleep but nothing happens with the dimmer:

2020-02-20 21:14:01.894 Detail, Node009,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x09, 0x02, 0x84, 0x07, 0xcc, 0x00, 0xb5
2020-02-20 21:14:01.894 Detail,
2020-02-20 21:14:01.894 Info, Node009, Received Wakeup Notification from node 9
2020-02-20 21:14:01.895 Info, Node009,   Node 9 has been marked as awake
2020-02-20 21:14:01.895 Detail, Node009, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x84, 0x08, 0x25, 0x56, 0x11
2020-02-20 21:14:01.895 Detail, Node009, Notification: Notification - Node Awake
2020-02-20 21:14:01.918 Detail,
2020-02-20 21:14:01.918 Info, Node009, Sending (WakeUp) message (Callback ID=0x56, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x84, 0x08, 0x25, 0x56, 0x11
2020-02-20 21:14:01.926 Detail, Node009,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-02-20 21:14:01.926 Detail, Node009,   ZW_SEND_DATA delivered to Z-Wave stack
2020-02-20 21:14:06.642 Detail, Node009,   Received: 0x01, 0x18, 0x00, 0x13, 0x56, 0x01, 0x01, 0xd8, 0x00, 0x7f, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x01, 0x07, 0x00, 0x00, 0x00, 0x00, 0x02, 0x07, 0x05, 0x09, 0x0a
2020-02-20 21:14:06.642 Detail, Node009,   ZW_SEND_DATA Request with callback ID 0x56 received (expected 0x56)
2020-02-20 21:14:06.642 Info, Node009, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-02-20 21:14:06.642 Info, Node009,   Node 9 has been marked as asleep
2020-02-20 21:14:06.642 Detail, Node009, Notification: Notification - Node Asleep

Does anyone have any advice on how I get this working? Let me know if I need to share any more details of my config.

Thanks

Posts: 1

Participants: 1

Read full topic

@Saturnus wrote:

Example automation:

- id: '011'
  alias: Toilet door open > Toilet lamp toggle off
  trigger:

This results in entity id automation.toilet_door_open_toilet_lamp_toggle_off

Before 0.105 you could change the alias, and this would automatically change the entity id. In other words, alias and entity_id were in sync.

After 0.105 this sync is gone. At least, this only applies when you are using ‘id’, which I do/did.

I guess ‘the sync’ is impossible from now on?

Posts: 1

Participants: 1

Read full topic

@LKent wrote:

For example, the user and password of the android_ip_webcam:

Posts: 2

Participants: 2

Read full topic

@TheDarthFather wrote:

Hello,
I installed HA on a Synology NAS using the HA docker image.
I am testing an Aotec Multisensor 6 in 1.
I paired it succesfully and HA receives data every 1h.
However for motion detection I need real time data.

So, using a guide from HA, I’ve tried setup the Aotect node “Command Options” to “Binary Sensor Report”.
It seems is saved … but it does not seem to detect anything.
I tried an automation from the standard ones … Turn On The Light when motion is detected … but I dont have any available trigger so I assume something is not ok.

Is there any way to debug this to make sure I am not missing anything ?

Thank you!

Posts: 1

Participants: 1

Read full topic

@Marius82 wrote:

Hi,

I try to setup an automation wich groups Sonos speaker together:

- id: '1582236119964'
  alias: sonos_ueberall
  description: ''
  trigger:
  - platform: webhook
    webhook_id: sonos_ueberall
  condition: []
  action:
  - entity_id: media_player.wohnzimmer, media_player.schlafzimmer, media_player.kuche,
      media_player.bad
    service: sonos.unjoin
  - delay: 00:00:03
  - data_template:
      master: '{{ trigger.json.entity_id }}'
      entity_id: media_player.wohnzimmer, media_player.schlafzimmer, media_player.kuche, media_player.bad
    service: sonos.join

Then I get this error:

voluptuous.error.MultipleInvalid: Entity ID {{ trigger.json.entity_id }} is an invalid entity id for dictionary value @ data[‘master’]

What is wrong with the '{{ trigger.json.entity_id }}'´?

Posts: 1

Participants: 1

Read full topic

@dshanaghy wrote:

I have a zwave device that created some sensors which i used in a template binary sensor to indicate motion.

I would like to attach my template binary sensor to the zwave device so it shows up when i look at that device from the integration page. Is that possible at all?

I recall seeing somewhere in the docs that a ‘device’ section could be added to an entity but can’t for the life of me find that section again now…

Posts: 3

Participants: 1

Read full topic

@bigverm23 wrote:

I have done the following:

1. generated a token with all selections described in instructions
2. added integration via HA
3. get prompted to install HA app inside of SmartThings
4. go to ST app > add a smartapp > my apps > only thing that shows up is Home Assistant Home via Nabu Casa

obviously clicking that does not work. what now?

Posts: 2

Participants: 1

Read full topic

@slhiguera wrote:

why is it that no one is talking about the use of iBeacons anymore? One of the biggest hurdles I feel at the moment is room presence. I understand that not everyone wants to carry their phone with them, but for the number of us who don’t mind I can’t find a good solution. Ble monitoring just doesn’t have the accuracy and reliability, motion sensors won’t tell you where you are unless you are constantly moving.

I’ve come back to thinking the use of owntracks, with iBeacons in each room, and publishing the zone enter and exit to MQTT would work great. Please explain to me me why I may be wrong here.

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

Lately, I think since HA 105, many of my Ikea lights dont use the last brightness setting when turned on (either by the motion sensor/switch or Ha interface) in the morning. They now turn on with brightness 0%… which is really annoying when you expect your bathroom to be safely lit ;-((

I am completely puzzled, since I havent changed anything in my Ha settings, and don’t believe the Ikea hub/software has changed settings on this functionality.

Could it be HA changed something when turning off lights? Could it be somehow now HA sets brightness to 0% when turning off, making the last recorded brightness 0% when turning on again?

for full disclosure, this is my script I use when set to sleep mode:

slapen_lighting:
  alias: Slapen lighting
  sequence:
    service: light.turn_off
    data_template:
      entity_id: >
        {% if states('group.h') == 'not_home' %} group.all_inside_lights
        {% else %} group.all_main_inside_lights, group.plafond_spots_woonkamer
        {% endif %}
      transition: 6

would it make a difference if I used this scene instead:

- name: Slapen
  entities:
    group.all_inside_lights: off

Sorry for the long topic title, but I would hope this to catch best what is happening. If anyone has a useful tip, Id appreciate it. Thanks!

edit

just thinking, could it be that the transition to ‘off’ makes the lights record the last brightness to be 0%? I used to have the transition in the scenes, but since that functionality unfortunately was taken from us, had to rewrite all my scene into scripts with transition.

Posts: 20

Participants: 3

Read full topic

@Woutch wrote:

Dear all,

I have a problem with mqtt items from my DSRM meter monitor program. It pushes the current power usage from my electricity meter to my mqtt broker.

I have configured these items in my config files:

- platform: mqtt
    state_topic: "dsmr/reading/electricity_currently_returned"
    unit_of_measurement: "KW"
    name: DSMR Returned
    device_class: power

  - platform: mqtt
    state_topic: "dsmr/reading/electricity_currently_delivered"
    unit_of_measurement: "KW"
    name: DSMR Delivered
    device_class: power

The problem is that a value of 0 does not work? If I restart home assistant and it connects it uses values bigger than 0 immediately, but topics that have a value of 0 stay on unknow until it changes and then the sensor picks it up.

Also, if my installation is returning power to the grid (for example 1KW). And i put something on like a electric heater, the delivered value shoots up. And in MQTT returned goes immediately to 0. But the sensor does not pick the 0 up and thus stays on 1KW returning while the other sensor says 2KW delivered for instance.

Could this be a problem in my home assistant config, or the way my dsmr monitor pushed values to MQTT?

Many thanks for any hint.

Best regards,
Wouter

Posts: 3

Participants: 2

Read full topic

@devitus wrote:

Hi everyone,

I hope you can help me with the following.

I’ve got an automatioon that turns off garage lights (via Sonoff 2-channel light switch) after a certain period of time, however current logic is flawed.

There are two triggers in the automation that turns on the garage lights:

1. Via contact sensor on the garage back door (binary_sensor.garage_back_door)
2. Via motion sensor in the garage (binary_sensor.garage_motion)

Code below for the automation that turns on the lights (ID values scrapped just in case, not sure if those should be shared):

- id: '123123123123123'
  alias: Garage Lights On
  description: ''
  trigger:
  - entity_id: binary_sensor.garage_back_door
    from: 'off'
    platform: state
    to: 'on'
  - entity_id: binary_sensor.garage_motion
    from: 'off'
    platform: state
    to: 'on'
  condition: []
  action:
  - entity_id: switch.sonoff_1000884e8a_1
    service: switch.turn_on
  - delay: 00:00:01
  - entity_id: switch.sonoff_1000884e8a_2
    service: switch.turn_on

And this is the automation that turns the lights off:

- id: '123123123123123'
  alias: Garage Lights Off
  description: ''
  trigger:
  - entity_id: binary_sensor.garage_motion
    from: 'on'
    platform: state
    to: 'off'
    for: 0:00:30
  condition: []
  action:
  - entity_id: switch.sonoff_1000884e8a_1
    service: switch.turn_off
  - delay: 00:00:01
  - entity_id: switch.sonoff_1000884e8a_2
    service: switch.turn_off

The problem is that this automation is only triggered when the motion sensor’s (binary_sensor.garage_motion) status changes from “on” to “off” (I have another automation that switches it to “off” state in 5 seconds from coming to “on”). So if the lights had been turned on via sensor on the garage back door (binary_sensor.garage_back_door), or manually via the switch without ever setting off the motion sensor, then the 30 second countdown would never start, and the lights would remain on indefinitely.

Ideally, I’d like any time the lights are turned on to trigger a 30-second coundown, and for every subsequent “turn on” even to reset that countdown back to 30 seconds every time. However, as far as I know, automations can only be triggered by a changed state (“on” to “off”, or “off” to “on”), so sending a new “on” request to a device that’s already “on” would effectively do nothing.

What’s would be the most efficient way of achieving the above?

Thanks in advance for your help!

Posts: 3

Participants: 2

Read full topic