@euromem wrote:

Hi Folks,
I don’t know how it happened or how to resolve it. I think it may be due to me changing the friendly name to something different for my iPhone entity, but my logs keep showing me the error “Found duplicate device name XXX iPhone X.”
When I go to Integrations > Mobile App I see my phone listed twice with the actual name from Settings > General > About and another entity with the friendly name I entered in Lovelace or somewhere, but there is not an option to disable one of the entities
I do also have UniFi controller running but I have relabeled entities in UniFi to have “unifi” after the name so I know it’s not the HA iOS app.
Running HA 0.111.1
iOS 13.5
Can anyone help please?
Is it related to me having a Nabu Casa account also?
Thanks

Posts: 1

Participants: 1

Read full topic

@acupofjose wrote:

I have some Ilumin Zwave Light Bulbs (the RGBW ones) that I’m struggling to get fully configured. When set up via the ZWave integration, they show as RGBW lights, but when set up in OpenZWave Beta (which I prefer using) they only show as toggleable lights.

In the ozw_admin panel, I can set the RGBW values manually but that’s not configurable/scriptable as far as I can tell.

Sensor Read:

light.lzw42_multi_color_bulb_level_4
off
node_id: 2
friendly_name: Reading Chair: Level
supported_features: 33

In ozw_admin:

Screen Shot 2020-06-12 at 2.04.08 PM1110×362 72.2 KB

Posts: 1

Participants: 1

Read full topic

@SentryBot2281 wrote:

I’ve been banging my head on this one for a couple of days now. I’ve followed as closely as possible the example code provided in various pages of the documentation part of the website as well as snippets I’ve found here in the forums. But still, no success.

I’ve made two automations that handle the opening of any door or window. One for when someone is home and one for when nobody is home. They both call the same script. Here is the automation for when something opens and family members are home:

- id: '1590342566376'
  alias: Open
  description: ''
  trigger:
  - platform: state
    entity_id:
      - sensor.x_door_virtual
      - sensor.x_door_basement
      - sensor.x_door_bilco
      - sensor.x_door_frontdoor
      - sensor.x_door_garagesidedoor
      - sensor.x_door_patiodoor
      - sensor.x_door_sidedoor
      - sensor.x_door_slidingpatiodoor
      - sensor.x_tilt_garagedoor
      - sensor.x_window_fullbath
      - sensor.x_window_masterbath
    to: 'Open'
  condition:
  - above: 0
    condition: numeric_state
    entity_id: input_number.whoishome
  action:
  - data_template:
      payload: macro=1&text={{ trigger.to_state.attributes.friendly_name }} {{ trigger.to_state.state }}
      topic: BlueIris/admin
    service: mqtt.publish
  - data_template:
      entity_id: script.open{{ trigger.entity_id.split('sensor.x')[-1] }}
    service: script.turn_on
  - data_template:
      data:
        priority: 0
        sound: pushover
      message: "{{ trigger.to_state.attributes.friendly_name }} {{ trigger.to_state.state }}"
      title: Security Notification
    service: notify.dave
  - service: input_text.set_value
    data_template:
      entity_id: input_text.macro1_text
      value: "{{ trigger.to_state.attributes.friendly_name }} {{ trigger.to_state.state }}"
  - service: timer.cancel
    entity_id: timer.macro1

I have similar automations for when something is closed, and they as well, both call the same script. The automations work fine. Calling the scripts works fine as well. I made a virtual door device for testing. The scripts are as follows:

'closed_door_virtual':
  alias: Virtual Door Closed
  sequence:
  - service: mqtt.publish
    data:
      topic: BlueIris/admin
      payload: camera=kitchen&preset=5
  - condition: numeric_state
    entity_id: input_value.whoishome
    above: 0
  - service: light.turn_off
    entity_id: light.unfinished_basement_lights
'open_door_virtual':
  alias: Virtual Door Open
  sequence:
  - service: mqtt.publish
    data:
      topic: BlueIris/admin
      payload: camera=kitchen&preset=2
  - condition: numeric_state
    entity_id: input_value.whoishome
    above: 0
  - service: light.turn_off
    entity_id: light.unfinished_basement_lights

The start of the scripts works as intended - my camera moves to the desired preset. However, even though my input_value helper has a value of 2, the condition doesn’t seem to be recognized and the scripts halt. I’ve tried just about every way I could find to construct the condition as well. What I pasted is one of the very few that seem to pass syntax muster though. Lastly, with the scripts as I pasted them here, there is nothing in my log to indicate an error halting the script.

Lastly, I want the BlueIris part of the script to run regardless of the condition which is why I put it before the condition, but I haven’t found any example scripts like this. Is this something that just won’t work?

Posts: 3

Participants: 2

Read full topic

@Sidioussam wrote:

Home assistant is reporting my Nabu Casa subscription as expired, despite my subscription being active. I’ve obviously restarted home assistant, as well as signing out and back in to nabu casa. I’m currently running hassOS 4.10 and Core 0.111.0 However, Nabu Casa had disconnected prior to my updating from 0.110.

There’s a few things showing in my log,

---

Logger: hass_nabucasa.cloud_api
Source: main.py:356
First occurred: 19:33:19 (231 occurrences)
Last logged: 20:07:30

Fetched https://remote-sni-api.nabucasa.com/snitun_token (400)

Log Details (ERROR)

Logger: hass_nabucasa.remote
Source: main.py:356
First occurred: 19:33:19 (231 occurrences)
Last logged: 20:07:30

Can’t refresh the snitun token

---

I’m running on a RPi 3b

Anyone have any idea what’s going on?

Posts: 1

Participants: 1

Read full topic

@NamCisum wrote:

Hi,

at the end of the day I open 20 blinds using Fibaro Roller Shutter 3. Those regurlarly fail to corectly report back to blind position once they are done (Fibaro specific implementation not fully working with HA), so I integrated a refresh entity action on the group in the automation:

- alias: 'Beschattung abends öffnen'
  trigger:
    platform: time
    at: "20:30:00"
  action:
    - service: cover.set_cover_position
      data:
        entity_id: group.cover_abend_1
        position: 100
    - delay: 00:02:00
    - service: zwave.refresh_entity
      data:
        entity_id: group.cover_abend_1

On the OZW.log I don’t see refresh commands for all nodes on the group.

Question: Should this work or is issuing commands to 5-10 zwave entities with one command simply is not a good idea?

Posts: 1

Participants: 1

Read full topic

@kkniffin wrote:

I have some questions for any Zensys Z-Wave PC Controller Gurus out there.

First off I am new to Home Assistant so bear with me if some of my questions are basic.

I ran into some issues joining my Z-wave light switches and had a lot of phantom devices with unknown/incomplete joins. I read online to install the Zensys Z-Wave PC Controller 5 software and remove them there. While I was in there I decided to try adding those troublesome devices, and wallah, it worked perfectly the first time. I then connected the USB Adapter back to the Home Assistant and it recognized them. Since I happen to have a windows surface tablet laying around, I was hoping I could just put the USB adapter in that, use the Zensys tools and go around and add all my device easily and come back, plug it into HomeAssistant and let it discover them.

My only problem with that is I don’t understand how to install my Z-wave network key that is setup in Home Assistant and do a secure join for locks and such in the Zensys software. Does anyone know how to, or if it can be done?

The adapter I have is: HUSBZB-1 Zwave/Zigbee Combo Adapter

The lights I ran into issues with come up as:

manufacturer name ACT
product name Unknown: type=4457, id=3230

One other note is that each problem child light initially seems to come in as the same name and only one light entity gets created. I find that if I rename them and restart Home Assistant then the light entities get created for the additional lights. Not sure if that helps in anyway.

Appreciate the help with this.

Posts: 1

Participants: 1

Read full topic

@hjggioasdjd wrote:

Hello!

I would like to use MQTT for a media player.

I am using shairport to airplay music in a whole-home audio solution. Shairport supports MQTT, and I am able to get shairport to publish topics for status. I am also able to control Shairport via MQTT.

I found the “Universal Media Player” Configuration in the documentation (https://www.home-assistant.io/integrations/universal/) that might do what I’m looking for.

If I were to use Universal media player, I imagine it would look something like:

media_player:
  - platform: universal
    name: Shairport
    commands:
      volume_down:
        service: mqtt.publish
        data: 
          topic: shairport-sync/snapcast/remote
          payload: "volumedown"
          qos: 2
          retain: false
...

Would that be possible or am I totally off on how to implement this?

Posts: 1

Participants: 1

Read full topic

@ulesin wrote:

Hi all!! I need help. I want to put this URL image into my configuration but it doesn´t work. I have tried the same as other images I have but nothing:

  - platform: generic
    still_image_url: https://my.meteoblue.com/visimage/meteogram_web_hd?look=KILOMETER_PER_HOUR%2CCELSIUS%2CMILLIMETER&apikey=5838a18e295d&temperature=C&windspeed=kmh&precipitationamount=mm&winddirection=3char&city=Sevilla&iso2=es&lat=37.382801&lon=-5.973170&asl=16&tz=Europe%2FMadrid&lang=es&sig=8499e593de98aff7660828b162489ae7
    name: Previsión 5 días
    content_type: 'image/png'

And with this too:

content_type: 'image/svg+xml'

What´s the problem in this URL? Does anyone know? Thanks for your time.

Posts: 1

Participants: 1

Read full topic

@bturrie wrote:

There are lots of posts about how to address the issues with windows 10 and samba and I tried several of them including enabling smb1 on the Windows machine. Only the one here worked for me:

https://devanswers.co/discover-ubuntu-machines-samba-shares-windows-10-network/

I used it on two Ubuntu 18.04 machines and it did the trick. I haven’t tried it on hass.io yet. Frankly I’m a bit reluctant to do so. I can still see my hass.io systems from linux so I’ll probably wait until the fix incorporated in a future update.

Posts: 1

Participants: 1

Read full topic

Thanks a lot for including Guardian integration with HA, I was waiting for this for some time.

After updating HA 227, I restarted both HA and Guardian valve and try to add them from the integration tab, but each time it was giving me the unknown error.’

I used the local IP that is permanent for Guardian valve ( 192.168.0.61) and the default port 7777

Kindly share your experience. I am not able to find error logs for this, if you find the error log please share with the owner in Github I create an issue but without the logs it is not possible for them to reproduce.

I can ping Gurardian it works as normal. from the app i can control the valve and new firmware is updated as well.

Elexa Guardian
Unknown error occurred
Configure a local Elexa Guardian device.

IP Address
192.168.0.61

Port
7777

1 post - 1 participant

Read full topic

Is it just me or is the card a little too smooth? Example here:

829×351 17.6 KB

Secondary questions: Can I get the X and Y labels to be a bit better? Can I add a label specifically to the number you see that is labeled 0kW in the screenshot? I want it to say “Current power: 0kW”.

Thirdly, if you have any suggestions to make this look better, I would appreciate it. Very new to Lovelace UI.

1 post - 1 participant

Read full topic

Hi!
I would like to control 1 relay with 4 xiaomi opening sensors.
“if you open a sensor then open the relay too, if all sensors are closed then close the relay as well”
how can i automate this. thanks

1 post - 1 participant

Read full topic

Running HA in Docker on top of Ubuntu 18 LTS. modem manager has purged

Also running HA addin for Deconz on a conbee II channel 25.

Added Elelabs stick.

Can see it in HA Hardware

Added by the Integration, found the new serial port, did not detect the radio automatically, added it, set the baudrate at 115200, successfully added the integration.

Restart HA

Can’t add any devices.

Anyone help on this one please?

1 post - 1 participant

Read full topic

I have created a dimmer for some led lights using ESPhome and the monochrome light component.

The problem I have is that the LEDs only dim to 30% before they go off.

I would some how like to remap this so 30%=0%dimming level and 100%=100%

Can this be done.

1 post - 1 participant

Read full topic

Hello There,

I am running HA for about 2 months now, but the last 2 weeks my AEONLABS usb zwave is not responding to close my shutter.
When i power off my PI and turn it on again it works for about 1 day and then it stop again.

I was thinking about a hardware failure, but when i place the usb stick in my old domticz server it does respond.

I have some logs of zwave below here, hope someone can help me fix this.

Thanks.
‘’’
2020-06-13 09:02:56.470 Info, Node002, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-06-13 09:02:56.470 Warning, Node002, WARNING: Device is not a sleeping node.
2020-06-13 09:02:56.470 Error, Node002, ERROR: node presumed dead
2020-06-13 09:02:56.470 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2020-06-13 09:02:56.470 Warning, CheckCompletedNodeQueries all=1, deadFound=1 sleepingOnly=1
2020-06-13 09:02:56.470 Info, Node query processing complete except for dead nodes.
2020-06-13 09:02:56.470 Info, Node002, QueryStageRetry stage CacheLoad requested stage CacheLoad max 3 retries 2 pending 1
2020-06-13 09:02:56.470 Detail, Node001, Expected callbackId was received
2020-06-13 09:02:56.470 Detail, Node001, Expected reply was received
2020-06-13 09:02:56.470 Detail, Node001, Message transaction complete
2020-06-13 09:02:56.470 Detail,
2020-06-13 09:02:56.470 Detail, Node002, Removing current message
2020-06-13 09:02:56.470 Detail, Node002, Notification: Notification - NoOperation
2020-06-13 09:02:56.472 Detail, contrlr, Notification: AllNodesQueriedSomeDead
2020-06-13 09:02:56.474 Detail, Node002, Notification: Notification - Node Dead
2020-06-13 09:02:56.476 Detail, Node002, Query Stage Complete (CacheLoad)
2020-06-13 09:02:56.476 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=CacheLoad live=0
2020-06-13 09:04:05.654 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Open - 1 - 1 - false
2020-06-13 09:04:05.655 Info, Node003, SwitchMultilevel::StopLevelChange - Stopping the level change
2020-06-13 09:04:05.655 Detail, Node003, Queuing (Send) SwitchMultilevelCmd_StopLevelChange (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x26, 0x05, 0x25, 0x10, 0xf2
2020-06-13 09:04:05.655 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x11, 0xf7
2020-06-13 09:04:05.655 Detail, Node003, Queuing (Send) SwitchMultilevelCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x26, 0x02, 0x25, 0x12, 0xf7
2020-06-13 09:04:05.655 Detail, Node003, Queuing (Send) IndicatorCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x87, 0x02, 0x25, 0x13, 0x57
2020-06-13 09:04:05.655 Error, Node003, ERROR: Dropping command because node is presumed dead
2020-06-13 09:04:05.655 Detail, Node003, Removing current message
2020-06-13 09:04:05.655 Error, Node003, ERROR: Dropping command because node is presumed dead
2020-06-13 09:04:05.655 Detail, Node003, Removing current message
2020-06-13 09:04:05.655 Error, Node003, ERROR: Dropping command because node is presumed dead
2020-06-13 09:04:05.656 Detail, Node003, Removing current message
2020-06-13 09:04:05.656 Error, Node003, ERROR: Dropping command because node is presumed dead
2020-06-13 09:04:05.656 Detail, Node003, Removing current message
2020-06-13 09:04:07.153 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Close - 2 - 1 - true
2020-06-13 09:04:07.153 Info, Node003, SwitchMultilevel::StartLevelChange - Starting a level change
2020-06-13 09:04:07.153 Info, Node003, Direction: Down
2020-06-13 09:04:07.154 Info, Node003, Ignore Start Level: True
2020-06-13 09:04:07.154 Info, Node003, Start Level: 0
2020-06-13 09:04:07.154 Info, Node003, Duration: 255
2020-06-13 09:04:07.154 Detail, Node003, Queuing (Send) SwitchMultilevelCmd_StartLevelChange (Node=3): 0x01, 0x0c, 0x00, 0x13, 0x03, 0x05, 0x26, 0x04, 0x60, 0x00, 0xff, 0x25, 0x14, 0x6a
2020-06-13 09:04:07.154 Error, Node003, ERROR: Dropping command because node is presumed dead
2020-06-13 09:04:07.154 Detail, Node003, Removing current message
‘’’

1 post - 1 participant

Read full topic

Hi,

for some time I’ve been looking into options to create a virtual lock in HA for my shutters. I have 3 kids, the youngest still being a toddler. The latter is obsessed with the wall switches and he keeps rolling my shutters up and down. After giving this a thought for sometime, today I came to think that instead of adding logic in the front-end the key could be the fibaro device itself instead. And luckily enough, it turns out that Fibaro ships a local control that could be leveraged for this purpose.

Screen Shot 2020-06-13 at 09.04.32649×577 31.9 KB

Anybody knows how do send module control parameters from the front-end??

many thanks!!

1 post - 1 participant

Read full topic

Hi all. My first noob post! Any help would be appreciated.

I’ve installed Hass in a FreeBSD jail. Aside from this one issue everything’s working perfectly and I’m desperately looking for some help.

I recently added a Nue Smart Plug to control a light via Hass. The smart plug shows up in the hue bridge, Hue app and Hue Essentials, but doesn’t show up in Hass.

Not seeing any issues in the logs. Everything’s been restarted just for good measure.

Not sure how to troubleshoot this because I can’t ssh to the hue bridge.

The smart plug shows up as a light in the hue app.

Any ideas??

All the best
Marty

1 post - 1 participant

Read full topic

Hey,
Logbook performance is poor for me. I click on it and it takes a minute or two to come back.

I’ve got about 10 days in there, and log about 4,000 entries per day. At what time do I move to an external DB? Is now the time?

I’m happy to give it a crack, but hopefully someone else has hit this problem and either found that it works or it’s a waste of time.

Thank you.

2 posts - 1 participant

Read full topic

Ok, loosing the will to not tear the stupid bloody door sensors off and throw them at the sea to wage war on Poseidon. But that would be nuts, and besides, I think some roman already did that.

Ok, so I got all excited and went off and bought some Tuya door sensors. So I’ve had a steep learning curve. Based on the time invested I could of hired bouncers to just stand next to the doors, but I keep perservering!

No combination of the bloody Tuya integration works for me. UK code: 44

I can’t change the firmware, that option was the one that made me come here and basically ask for directions, my macho is more nacho now.

Tuya app on phone drives me insane with “THE DOOR IS OPEN” pinging every second, so used the Smart Life app, ended up now with sensors on both to keep trying different combinations.

I have it on Alexa, “Is the Front Door Sensor Open?” …“The Front Door Is Closed” I get back, hurrah…

But how do I get that into a sensor item in HA, it’s not a switch, I’ve followed just about evey idea/example on the internet I could find, but nope.

I just want to know if that stupid blinking door is open…or I’ll jolly well go and buy an expensive one that will probably frustrate me even more!..

You have been warned.

Oh if you could help, that’d be great, I think I’ve lost it a little in lock down…

Can I read out sensor states that Alexa knows from HA?

if (alexa.tuya.front_door_sensor == 'open')

2 posts - 2 participants

Read full topic

I have the below code that seems to be triggering the iOS notification randomly.
It triggers at 08.30 which I understand, however it then seems to randomly trigger through the day at no real schedule that I can work out.
As a side, it also doesn’t trigger when it should.

Does anyone have any idea why this may be happening?

- alias: Send alert when washing machine finished
  trigger:
    - platform: state
      entity_id: input_select.washing_machine_status
      to: Clean
    - platform: time
      at: '08:30:00'
    - platform: state
      entity_id: device_tracker.bens_iphone
      to: 'home'
      for:
        minutes: 10
    - platform: state
      entity_id: device_tracker.lucys_iphone
      to: 'home'
      for:
        minutes: 10
  condition:
    condition: and
    conditions:
      - condition: time
        before: '22:30:00'
        after: '08:29:00'
      - condition: state
        entity_id: group.people
        state: 'home'
      - condition: state
        entity_id: input_select.washing_machine_status
        state: Clean
      # Don't send this alert if it was last triggered less than 30 minutes ago (1,800 seconds)
      - condition: template
        value_template: >
          {% if states.automation.send_alert_when_washing_machine_finished.last_triggered is not none %}
            {% if as_timestamp(now()) | int   -  as_timestamp(states.automation.send_alert_when_washing_machine_finished.attributes.last_triggered) | int > 3600 %} true {% else %} false
            {% endif %}
          {% else %}
          false
          {% endif %}
  action:
    - service_template: >
        {% if (is_state('device_tracker.bens_iphone', 'home')) and (is_state('device_tracker.lucys_iphone', 'home'))  %}
          notify.ben_and_lucy
        {% elif is_state('device_tracker.bens_iphone', 'home') %}
          notify.ben
        {% elif is_state('device_tracker.lucys_iphone', 'home') %}
          notify.lucy
        {% endif %}
      data:
        message: 'Hey, the washing machine has finished and is ready to be emptied'
        title: 'Washer Update' 

1 post - 1 participant

Read full topic