@Peter_West wrote:

Hi,

I’ve recently configured the recently added media card to display content that has been added to a Kodi installation.

All is working fine except it’s not display either the fantart or the poster images.

The data for the sensor looks fine and it includes http adddresses for the various images. Opening these in a browser prompts for credentials, but providing the credentials for the sensor then displays the images without issue.

Anyone got any clues on why the images aren’t being displayed please?

Thanks

Pete

Posts: 1

Participants: 1

Read full topic

@henry8866 wrote:

I found HA has many of myQ log like below, and it is not responding when I try to open/close it from HA. It works fine from myQ its own app.

2020-04-12 14:20:40 WARNING (MainThread) [pymyq.api] Device update failed; trying again in 5 seconds
2020-04-12 14:20:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of cover.door1main is taking over 10 seconds

Anyone else experiencing this? How to solve this?

Posts: 1

Participants: 1

Read full topic

@topse wrote:

Hi,
I have a question. Home Assistant tells me, it has discovered a new Device “Philips Hue” and if I want to configure it, but it is already configure, see the picture:

homeassistant_hue677×555 29.7 KB

Can somebody give me an advice, first what is happening and second – what should I do?

Best Regards,
Tobias

Posts: 2

Participants: 2

Read full topic

@wakeskate wrote:

Just updated to 108.3 but before I did it I ran a snapshot complete and it
only took 4 seconds to run and the file size is very small.
Full snapshot (6.8 MB)
Sunday, Apr 12, 2020, 12:28 PM

Checked back on one of my old ones and it was 81 MB.

Does anyone know if their is a known issue with the Snapshot service
Just want to make sure they are good in case my SD card craps out.

EDIT:
Found this in the logs not sure what it means.

20-04-12 19:28:32 WARNING (SyncWorker_1) [supervisor.snapshots.snapshot] Can’t snapshot folder homeassistant: [Errno 2] No such file or directory: ‘/data/homeassistant/home-assistant_v2.db-shm’

Posts: 1

Participants: 1

Read full topic

@gekomax wrote:

Hello folks,

I have a strange code, I can’t make it work.
This is the code:

- platform: template
  sensors:
    qualita_aria_floated:
      value_template: '{{ ((states.sensor.luftdaten_34405_p1.state)) | round(0, "ceil") }}'
      entity_id: sensor.luftdaten_34405_p1
    qualita_aria:
      value_template: >-
        {% if states.sensor.qualita_aria_floated.state >= '0' and states.sensor.qualita_aria_floated.state <= '49' %}
          buona
        {% elif states.sensor.qualita_aria_floated.state >= '50' and states.sensor.qualita_aria_floated.state <= '100' %}
          moderata
        {% elif states.sensor.qualita_aria_floated.state >= '101' and states.sensor.qualita_aria_floated.state <= '150' %}
          malsana per gruppi sensibili
        {% elif states.sensor.qualita_aria_floated.state >= '151' and states.sensor.qualita_aria_floated.state <= '200' %}
          malsana
        {% elif states.sensor.qualita_aria_floated.state >= '201' and states.sensor.qualita_aria_floated.state <= '300' %}
          molto malsana
        {% elif states.sensor.qualita_aria_floated.state >= '301' and states.sensor.qualita_aria_floated.state <= '500' %}
          pericolosa
        {% else %}
          sconosciuta
        {% endif %}
      entity_id: sensor.luftdaten_34405_p1

If I use the tempate editor in HAS,:

       {% if states.sensor.qualita_aria_floated.state >= '0' and states.sensor.qualita_aria_floated.state <= '49' %}
          buona
        {% elif states.sensor.qualita_aria_floated.state >= '50' and states.sensor.qualita_aria_floated.state <= '100' %}
          moderata
        {% elif states.sensor.qualita_aria_floated.state >= '101' and states.sensor.qualita_aria_floated.state <= '150' %}
          malsana per gruppi sensibili
        {% elif states.sensor.qualita_aria_floated.state >= '151' and states.sensor.qualita_aria_floated.state <= '200' %}
          malsana
        {% elif states.sensor.qualita_aria_floated.state >= '201' and states.sensor.qualita_aria_floated.state <= '300' %}
          molto malsana
        {% elif states.sensor.qualita_aria_floated.state >= '301' and states.sensor.qualita_aria_floated.state <= '500' %}
          pericolosa
        {% else %}
          sconosciuta
        {% endif %}
        
        {{ states.sensor.qualita_aria_floated.state  }}
        {{ ((states.sensor.luftdaten_34405_p1.state ) ) | round(0, "ceil") }}`

got this:

pericolosa

    5
    5

(on lovelace got the same)

That it’s completely illogical… or am I wrong?

I’m sorry this is written in italian but I think it’s in understandable…

Any suggestion?
Thanks!
Bye
Gekomax

Posts: 2

Participants: 2

Read full topic

@Mariusthvdb wrote:

somehow my history and logbook are without data. 100%

Schermafbeelding 2020-04-12 om 21.41.221238×288 13.2 KB

showing this on all entities in recorder:

Schermafbeelding 2020-04-12 om 21.47.16730×368 18.5 KB

I haven’t changed my settings for MariaDb at all, since forever… I did update to 107.5 several days ago. did anyone else notice loss of connection the DB?

No errors in the logs regarding to the DB

only this ‘warning’

Schermafbeelding 2020-04-12 om 21.52.48864×462 43.3 KB

Must confess my HA instance is super fast now, so that’s an improvement ;-). Still I need the history, so hope anyone would have a hint where to look

Posts: 1

Participants: 1

Read full topic

@Jdruwe wrote:

Today I decided to add Google Assistant integration, all but one things seems to work fine. I am under the impression that the room attribute of for example a light will put the device automatically in a room that can be found in the Google Home app but I cant seem to get it working. Here my config:

...
  entity_config:
    light.livingroom:
      name: leefkamer
      room: Leefkamer
      aliases:
        - salon
...

As you can see I specified Leefkamer as a room. When the room wasn’t created automatically I created it manually but that didn’t help. Here are some screenshots:

93491908_217247456273962_8806143709537107968_n1080×2280 60 KB

92664881_544887616462730_647514930311856128_n1080×2280 77.2 KB

93078196_586591925546268_4901702637117767680_n1080×2280 32.9 KB

It shows my ‘Leefkamer’ (which is a group of lights created by Deconz zigbee integration) under the list of ‘Linked to you. 24 devices not I a home’. Am I doing something wrong? Why isn’t the entity getting added to my Leefkamer room. Note that I asked google to sync me devices and that it succesfuly did so. I also refreshed in the Google Home app by swiping down.

Posts: 1

Participants: 1

Read full topic

@eBoon wrote:

I am currently running Homeassistant inside docker on Ubunto 18.04. Yesterday, I did an upgrade from 0.107.7 to 0.108.3 and I have been down ever since. The upgrade seemed to hang and long story short, I ended up just giving up and restoring from my nightly full backup. I followed the guide (under PREPARATION) so install the base Homeassistant and then installed the Google Drive Backup addon to restore my snapshot. This seemed to mostly work - until I restart HomeAssistant. After a restart, the HA UI never comes back. When I look at the Supervisor log (ha su logs) I see something like this:

20-04-12 20:27:14 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:19 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:19 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:24 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:24 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:24 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:29 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:29 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:34 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:34 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:39 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:39 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:39 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:44 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:44 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:44 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-12 20:27:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-12 20:27:49 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-04-12 20:27:49 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

Not sure what is going on, but I’m guessing that there is a problem with the Docker setup. Looks to me like it’s expecting to HA at 172.30.32.1:8123 but it’s not finding it there? I don’t know - I’m certainly no Docker expert!!

Any advice for me - looking at the containers from within Portainer looks normal to me:

image2217×537 84.6 KB

Thanks in advance for any help you can give me to steer me in the right direction!

Tom

Posts: 1

Participants: 1

Read full topic

@jeremyowens wrote:

I’m experiencing an issue with Alexa that I’m hoping that someone can help me with. I’m currently running HASS.IO (or whatever it’s called now) v108.3 in a VM on ESXi.

Background: I’ve recently moved to a new place. Prior to moving, I excluded all my z-wave devices from my network. Most, but not all, are GE light, dimmers and fan switches. Once settled into my new place, I added back the switches, gave them all the appropriate names, and went on my way.

Then, I went to setup Alexa to work with the new devices. I went into my account and “forgot everything”. Then I went to “Discover Devices”. When it discovered the devices, they all still had the old names. What gives…?

So I went through troubleshooting, and went so far as to rebuild the VM that’s running HA. I’ve reset my Z-Stick, which gave me a new Z-Wave network ID. I’ve re-run the configuration/naming process again, and even the Z-Wave IDs are different for each device. Yet when I tell Alexa to rediscover devices, it still finds the old names.

Is there a way to get Alexa to discover the correct names, and stop discovering names that don’t exist? Or is this an Amazon account issue?

Posts: 1

Participants: 1

Read full topic

@dgoepp wrote:

I’m trying to connect smartthings, and am getting an error when entering my personal token.

Screen Shot 2020-04-12 at 6.18.23 PM1224×530 38.6 KB

Most of the information I’ve found regarding this is pretty outdated. Has anyone setup smarttings successfully recently?

I’m running Home Assistant 0.108.3.

Posts: 1

Participants: 1

Read full topic

@danielgroenbek wrote:

Hi

I have moved from Pi3+ to a fresh HA install on Pi4, and in this process removed the Deconz integration on the Pi3 and moved the Conbee USB stick to the new Pi4. When installing this the first time I initially got the gateway up on the screen, but i could not complete the API integration to HA. I uninstalled, and rebooted, and then installed Deconz again. I’ve done this over an over, but the gateway (in the GUI) is gone when I navigate to the Gateway page (see image below).

Yes - i can access the GUI of Deconz but I dont see the gateway. I have tried changing the device without luck ("/dev/ttyUSB0", “/dev/ttyAMA0” and “/dev/ttyACM0”), and don’t seam to find any direction in the logs.

I didn’t add to the config.txt in my first installation, and therefore hasn’t done that on this one either
enable_uart=1
dtoverlay=pi3-miniuart-bt

image1312×844 15.1 KB

Log: https://pastebin.pl/view/68295465

Do you have any good tips?

Posts: 1

Participants: 1

Read full topic

@membersound wrote:

I’d like to keep the default overview where new entities are automatically added, cards are automatically created by HA etc.

Additionally, I’d like to have a custom overview where I’d configure only my own cards. Like Map Card History etc.

Is that possible (retain autogenerated overview, while adding a custom in addition)? And if yes: can I link that overview to a specific user only?

Posts: 2

Participants: 2

Read full topic

@fra wrote:

Hello, someone could point me to the right direction on how to increase the width of the “left sidebar”?
Specially in mobile phone i need that the sidebar width is 100%, the same behaviour of notifications.

Thanks a lot.

Best regards

Posts: 1

Participants: 1

Read full topic

@ltoolio wrote:

Argh!

Had my Zwave rock solid, upgraded to 0.108.3 and now my Zwave config is all messed up.

Running Home Assistant via Docker with an Aeotec stick. Upon querying the Zwave log, it’s filled with the messages below. I downgraded to 0.107.3 and the issue remains.

I’ve read in other posts with similar error messages that this is often happened when another process is also querying the Zwave stick, but I’ve not installed anything that access it and I don’t think that I have multiple instances of Home-Assistant running.

I did recently install a Sonoff Tasmota switch, but that’s via MQTT and I wouldn’t think that would be the issue.

Any ideas? I’m at a complete loss.

2020-04-12 19:16:43.169 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:43.169 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:43.169 Warning, WARNING: Out of frame flow! (0x73).  Sending NAK.
2020-04-12 19:16:43.170 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:53.021 Error, Node045, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-04-12 19:16:53.021 Detail, Node045, Removing current message
2020-04-12 19:16:53.021 Detail, Node045, Notification: Notification - TimeOut
2020-04-12 19:16:53.023 Detail, Node045, Query Stage Complete (Session)
2020-04-12 19:16:53.023 Detail, Node045, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2020-04-12 19:16:53.023 Detail, Node045, QueryStage_Dynamic
2020-04-12 19:16:53.023 Detail, Node045, Queuing (Send) SwitchBinaryCmd_Get (Node=45): 0x01, 0x09, 0x00, 0x13, 0x2d, 0x02, 0x25, 0x02, 0x25, 0xea, 0x22
2020-04-12 19:16:53.023 Info, Node045, CentralScene RequestState: 4
2020-04-12 19:16:53.023 Info, Node045, CentralScene: Not a StaticRequest
2020-04-12 19:16:53.023 Detail, Node045, Queuing (Query) Query Stage Complete (Dynamic)
2020-04-12 19:16:53.023 Detail,
2020-04-12 19:16:53.023 Info, Node045, Sending (Send) message (Callback ID=0xea, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=45): 0x01, 0x09, 0x00, 0x13, 0x2d, 0x02, 0x25, 0x02, 0x25, 0xea, 0x22
2020-04-12 19:16:53.531 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-04-12 19:16:53.531 Warning, WARNING: Out of frame flow! (0xe8).  Sending NAK.
2020-04-12 19:16:53.531 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:53.531 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:53.532 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:54.032 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-04-12 19:16:54.032 Detail, Node045,   Received: 0x01, 0x01, 0x01
2020-04-12 19:16:54.032 Warning, Node045, WARNING: Checksum incorrect - sending NAK
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x14).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x0e).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x32).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x7c).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:56.815 Warning, WARNING: Out of frame flow! (0x05).  Sending NAK.
2020-04-12 19:16:56.816 Warning, WARNING: Out of frame flow! (0x4e).  Sending NAK.
2020-04-12 19:16:56.816 Warning, WARNING: Out of frame flow! (0x14).  Sending NAK.
2020-04-12 19:16:56.816 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:56.816 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:56.816 Warning, WARNING: Out of frame flow! (0x0e).  Sending NAK.
2020-04-12 19:16:56.816 Warning, WARNING: Out of frame flow! (0x32).  Sending NAK.
2020-04-12 19:16:56.817 Warning, WARNING: Out of frame flow! (0x21).  Sending NAK.
2020-04-12 19:16:56.817 Warning, WARNING: Out of frame flow! (0x05).  Sending NAK.
2020-04-12 19:16:56.817 Warning, WARNING: Out of frame flow! (0x56).  Sending NAK.
2020-04-12 19:16:56.817 Warning, WARNING: Out of frame flow! (0xd4).  Sending NAK.
2020-04-12 19:16:56.817 Warning, WARNING: Out of frame flow! (0x05).  Sending NAK.
2020-04-12 19:16:56.817 Warning, WARNING: Out of frame flow! (0x4e).  Sending NAK.
2020-04-12 19:16:56.818 Warning, WARNING: Out of frame flow! (0x14).  Sending NAK.
2020-04-12 19:16:56.818 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:56.818 Warning, WARNING: Out of frame flow! (0x0e).  Sending NAK.
2020-04-12 19:16:56.818 Warning, WARNING: Out of frame flow! (0x21).  Sending NAK.
2020-04-12 19:16:56.818 Warning, WARNING: Out of frame flow! (0x05).  Sending NAK.
2020-04-12 19:16:56.818 Warning, WARNING: Out of frame flow! (0x56).  Sending NAK.
2020-04-12 19:16:56.819 Warning, WARNING: Out of frame flow! (0xd4).  Sending NAK.
2020-04-12 19:16:56.819 Warning, WARNING: Out of frame flow! (0x4e).  Sending NAK.
2020-04-12 19:16:56.819 Warning, WARNING: Out of frame flow! (0x14).  Sending NAK.
2020-04-12 19:16:56.819 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x07).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x32).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x02).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x56).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x7c).  Sending NAK.
2020-04-12 19:16:56.820 Warning, WARNING: Out of frame flow! (0x4e).  Sending NAK.
2020-04-12 19:16:56.905 Detail, Node045,   Received: 0x01, 0x10, 0x0a, 0x32, 0x02, 0x00, 0x02, 0x00, 0x00, 0x00, 0x01, 0x10, 0x00, 0x04, 0x00, 0x07, 0x02, 0x21
2020-04-12 19:16:56.905 Warning, Node045, WARNING: Checksum incorrect - sending NAK
2020-04-12 19:16:56.908 Detail, Node033,   Received: 0x01, 0x10, 0x00, 0x04, 0x07, 0x21, 0x74, 0x00, 0x02, 0x00, 0x00, 0x00, 0x01, 0x04, 0x00, 0x0a, 0x02, 0x21
2020-04-12 19:16:56.908 Warning, Node033, WARNING: Checksum incorrect - sending NAK
2020-04-12 19:16:56.958 Warning, WARNING: 50ms passed without finding the length byte...aborting frame read

Posts: 5

Participants: 4

Read full topic

@PPatou wrote:

Hello
I am currently using version 0.108.
I wanted to experiment with custom header kiosk mode but did it on the admin user.
Now i am stuck in kiosk mode and cannot access the normal front-end anymore.
I found 1 post about this problem where the solution proposed is to use the following adres in the browser : http://192.168.1.21:8123/lovelace/0?disable_cch
Unfortunately this does not work and it stays in kiosk mode
Can somebody help ?
Thanks in advance
Patou

Posts: 4

Participants: 2

Read full topic

@SylvainGa wrote:

Probably through AppDaemon but I haven’t learned how to use it yet but until then, is there a better way of doing the following in scripts?

I have a fan that I control through a Tasmota device. It has one push button that goes from High, Medium, Low, Off (in that order) and the Tasmota device toggles de button for 0.5 sec. I defined an input_number variable called ventilateur_salon_speed and 4 scripts. This is the script for Max speed but they are the same, except the number they stop at (0 for Off, 1 for Low, 2 for Medium and 3 for High). The script goes through 3 main actions: Test if already at its required value and if it is, stop the script. If not, turn on the button and decrement the variable. If it reaches 0, start back at 3 then delay so it has time to toggle before continuing. Since it can take 3 iterations (ie, push the button 3 times) to reach the requested speed, it repeat this action 3 times (hence why 3 main actions).

'1586725146435':
  alias: VentilateurSalonSpeedMax
  sequence:
  - condition: template
    value_template: >
      {% if states.input_number.ventilateur_salon_speed.state | float == 3.0 %}false{% else %}true{% endif %}
  - data: {}
    entity_id: switch.ventilateursalonalimentation
    service: switch.turn_on
  - data_template:
      value: '{% if states.input_number.ventilateur_salon_speed.state | float < 1.0 %}3.0{% else
        %}{{ states.input_number.ventilateur_salon_speed.state | float - 1.0 }}{% endif %}'
    entity_id: input_number.ventilateur_salon_speed
    service: input_number.set_value
  - condition: template
    value_template: >
      {% if states.input_number.ventilateur_salon_speed.state | float == 3.0 %}false{% else %}true{% endif %}
  - delay: 00:00:01
  - data: {}
    entity_id: switch.ventilateursalonalimentation
    service: switch.turn_on
  - data_template:
      value: '{% if states.input_number.ventilateur_salon_speed.state | float < 1.0 %}3.0{% else
        %}{{ states.input_number.ventilateur_salon_speed.state | float - 1.0 }}{% endif %}'
    entity_id: input_number.ventilateur_salon_speed
    service: input_number.set_value
  - condition: template
    value_template: >
      {% if states.input_number.ventilateur_salon_speed.state | float == 3.0 %}false{% else %}true{% endif %}
  - delay: 00:00:01
  - data: {}
    entity_id: switch.ventilateursalonalimentation
    service: switch.turn_on
  - data_template:
      value: '{% if states.input_number.ventilateur_salon_speed.state | float < 1.0 %}3.0{% else
        %}{{ states.input_number.ventilateur_salon_speed.state | float - 1.0 }}{% endif %}'
    entity_id: input_number.ventilateur_salon_speed
    service: input_number.set_value

What do you think? Can you improve it? Make it more efficient or fix possible pitfalls?

Edit : forgot to say the scripts are called by Alexa.

Thanks.

Posts: 1

Participants: 1

Read full topic

@WeldFire wrote:

Hello,

Is there a way to add state to an existing broadlink switch or create a new switch containing state that calls the original switch?

I have a broadlink IR Blaster with which I’m controlling my TV and I would like to track whether it is on before sending as the command for my TV is a toggle command.

I don’t see any way to add the current state of the TV from the documentation that I see here:

I’ve done something similar before with a command line platform and would like to do something like this:

- platform: broadlink
    host: !secret ip-broadlink-ir_blaster
    switches:
      tv:
        friendly_name: "Samsung TV Power"
        command_on: !secret living_room-samsung_tv-power
        command_off: !secret living_room-samsung_tv-power
        # command_state: "wget --spider --server-response --tries=1 --timeout=5 http://192.168.1.5:8000 2>&1 | grep '200\ OK'"

Best Regards,
WeldFire

Posts: 1

Participants: 1

Read full topic

@bleep-io wrote:

I’m following the docs and trying to create a script to set a datetime input to the current date/time but it’s giving me an error:

  - service: input_datetime.set_datetime
    entity_id: input_datetime.date_and_time
    data_template:
      datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"

Failed to call service input_datetime/set_datetime. Invalid datetime specified: {{ now().strftime('%Y-%m-%d %H:%M:%S') }} for dictionary value @ data['datetime']

Posts: 4

Participants: 4

Read full topic

@Tomac84 wrote:

Hey,

i had a time-based automation. For some reason i want to start the automation “by hand” by clicking a switch on my lovelace panel. I know how to start the automation bei service, but i have no idea, how to put this into a switch…

Can someone help me?

Posts: 1

Participants: 1

Read full topic

@xefil wrote:

Hello,

I’ve updated my HA on docker from 102.3 to latest yesterday.
After resolving some issues on mqtt (loop connections on mqtt broker, resolved removing the client-id from config), I’ve noticed a strange thing about my zigbeee devices controlled via zigbee2mqtt.
First of all, I’ve not updated zigbee2mqtt so seems not related in there.
I’ve noticed that my zigbee devices now appears on HA with its “friendly_name” as id, and not more with it’s original ID.
After renaming the device on zigbee2mqtt some weeks ago all went well on HA, even after HA restarts. HA has updated only the friendly name and maintained the id. After this last update I’ve lost those devices and found they are registered with its friendly name, not more with it’s zigbee address and friendly name as description. This deletes my history. I don’t know it’s related to the mqtt issues I had, but shouldn’t.
I.e. I can find a light into ‘core.restore_state’ twice: one with original name:

"entity_id": "light.0x000d6ffffe17ea41_light"

and the other with it’s new wrong name:

"entity_id": "light.luce_corridoio_light"

Something changed with this update?

Is there a way to recover them?

Thanks!

Simon

Posts: 3

Participants: 2

Read full topic