@mkjustuk wrote:

I have two Tuya shutter switches (via the Tuya platform, running stock firmware). They have an up, stop and down button. The switches show fine and automation can control them without issue.

The problem I have is that as they are stateless, I can’t open or close them from the interface, the up and down buttons are greyed out.

I’ve added a position of 50 in the configuration.yaml as I found on other threads covering this, but despite the file being checked as valid, the buttons remain grey - is there anything else I can try or something I missed on the entry?

cover:
  - platform: template
    covers:
      patio_door:
        friendly_name: "Patio Door"
        position_template: "50"

Posts: 2

Participants: 2

Read full topic

@drivin wrote:

Hello, I am currently trying to have a script triggered by a button. Only I need here service_template or similar. This seems not to work directly on the button. The script should definitely not be outsourced. Does anyone have an idea?

type: button
tap_action:
  action: call-service
  service: climate.set_temperature
  service_data:
    entity_id: climate.hz_ankleidezimmer_group
    temperature: >-
      {{ state_attr('climate.hz_ankleidezimmer_group', 'temperature') | float +
      0.5 | float }}

hold_action:
  action: more-info
show_icon: true
show_name: true
entity: climate.hz_ankleidezimmer_group

As soon as I use service_template instead of service_data I get the error message: Fehler beim Aufrufen des Service climate/set_temperature. must contain at least one of temperature, target_temp_high, target_temp_low.

Posts: 1

Participants: 1

Read full topic

@Wes93 wrote:

Hello to everyone, i need some help if is possible…
i want to change the icon of the device_class window with this icon window-closed-variant how can i do?
i have many sensors so for me is more seimple to change the class instead of the icon (with on and off change) of all sensors.
There is also a way to add more device_class? like add gate class with different icon.
Thanks a lot
Stefano

Posts: 5

Participants: 2

Read full topic

@WinterCold wrote:

Hi guys,

I have the following error with the SSH:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] cli: applying... 
[fix-attrs.d] cli: exited 0.
[fix-attrs.d] profile: applying... 
[fix-attrs.d] profile: exited 0.
[fix-attrs.d] ssh: applying... 
[fix-attrs.d] ssh: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] keygen.sh: executing... 
[05:38:09] INFO: Restoring host keys...
cp: can't stat '/data/host_keys/*': No such file or directory
[cont-init.d] keygen.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

I am unable to start SSH at all with the default configuration or with my own config as follows:

authorized_keys:
    ssh-rsa XXX..... rsa-key-20190209
password: ''

Hassio Ver: 109.3 (Fresh Install on a SD card)
Hardware: Rpi4
Please help!

Posts: 1

Participants: 1

Read full topic

@Thomas.dmm wrote:

Hello Every Body
I have two instance onf Home assistant one on Raspberry pi4 (server 1 10.0.0.72)and one other on docker Nas Synology (serveur 2 10.0.0.70)
My goal is to get the information about sensor (Zigbee on Deconz) on server 1 to the server 2. I found this integration :

I have make 3 tests
On server 1 i have this sensor : sensor.couloir_temp zigbee device xiami Temperatur and Humidity in this case sensor for temperatur
On Server 2 I have add this code in the Configuration.yaml

   ############################################################
   ##                                                                                                                ##
   ##                     Sensor rest home assitant Pi                                             ##
   ##                                                                                                                ##
   ############################################################ 
    
  - platform: rest
    resource: http://10.0.0.72:8123/api/states/sensor.couloir_temp
    username: (login of session on server1)
    password:  (password of session on server1)
    name: test1
    value_template: '{{ value_json.state }}'
    unit_of_measurement: "°C"
    
  - platform: rest
    resource: http://10.0.0.72:8123/api/states/sensor.couloir_temp
    name: test2
    value_template: '{{ value_json.state }}'
    unit_of_measurement: "°C"   

  - platform: rest
    resource: http://10.0.0.72:5000/sensor
    username: (login of session on server1)
    password: (password of session on server1)
    authentication: basic
    headers:
      User-Agent: Home Assistant
      Content-Type: application/json

On server 2 I have two sensor (sensor.test1 and sensor.test2 with value unknow)

On server1 I have this notify :
Login attempt failed
Login attempt or request with invalid authentication from 10.0.0.70

When I restart server 1 value of sensor in server 2 change from “unknow” to “unavailable”

Some one can help me ?

Posts: 1

Participants: 1

Read full topic

@uphillbattle wrote:

I would like to set two dates (April 1 and November 1 for the time being) to indicate transitions between two different seasons (let’s say, summer and winter). The dates should be adjustable, so I’m thinking input_datetime although they’re likely to stay the same for a few years. I therefore would like NOT to enter the year.

I haven’t found a way to make the input_datetime omit the year. I could, of course, define two input_number per date - for month and day - but it’s not quite as elegant as I would like.

Any ideas?

Posts: 3

Participants: 3

Read full topic

@HansDR wrote:

Hello everybody,

Until this morning, I had a working MySensors integration on Home Assistant using the MQTTGateway. This morning, I upgraded my host-system to Ubuntu 20.04 LTS, and although Home Assistant itself is running perfectly, I can’t seem to get the MySensors integration part working again. I am not completely sure this is related to the upgrade, but it would be a very unlucky coincidence

My configuration is still quite simple, with 2 remote sensors, one publishing the temperature based on a Dallas sensor, the other publishing both TEMP/HUM based on a DHT22. The configuration.yaml looks like this:

mysensors:
  gateways:
    - device: mqtt
      persistence_file: '/tmp/mysensors.json'
      topic_in_prefix: 'MySensorsOut'
      topic_out_prefix: 'MySensorsIn'

Now, the problem is in my opinion easily pinpointed to the MySensors integration, as the MQTTGateway has always continued writing sensor-values to the Queue, but since the update, no entities are created anymore.

image1476×892 53.9 KB

In the logs, we can see that the Home Assistant plugin is loaded correctly, and that a subscription is successfully done.

2020-05-04 14:11:16 INFO (MainThread) [homeassistant.setup] Setting up mysensors
2020-05-04 14:11:16 DEBUG (SyncWorker_9) [mysensors.persistence] Loading sensors from persistence file /tmp/mysensors.json
2020-05-04 14:11:16 DEBUG (SyncWorker_2) [mysensors.persistence] Saving sensors to persistence file /tmp/mysensors.json
2020-05-04 14:11:16 INFO (SyncWorker_4) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
2020-05-04 14:11:16 INFO (MainThread) [homeassistant.setup] Setting up tts
2020-05-04 14:11:16 INFO (MainThread) [homeassistant.setup] Setup of domain mysensors took 0.1 seconds.
2020-05-04 14:11:16 INFO (MainThread) [mysensors.gateway_mqtt] Setting up initial MQTT topic subscription
2020-05-04 14:11:16 DEBUG (MainThread) [mysensors.gateway_mqtt] Subscribing to: MySensorsOut/+/+/0/+/+, qos: 0
2020-05-04 14:11:16 DEBUG (MainThread) [mysensors.gateway_mqtt] Subscribing to: MySensorsOut/+/+/3/+/+, qos: 0
2020-05-04 14:11:16 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.0 seconds.
2020-05-04 14:11:16 INFO (MainThread) [homeassistant.setup] Setting up hassio
2020-05-04 14:11:16 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.0 seconds.
2020-05-04 14:11:17 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 9.94s
2020-05-04 14:11:17 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2020-05-04 14:11:17 INFO (SyncWorker_3) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2020-05-04 14:11:17 INFO (MainThread) [homeassistant.core] Timer:starting

I also know this subscription works well, because creating a manual topic causes the system to react. Publishing MySensorsOut/3/0/0/0/0 causes the following item in the logs:

2020-05-04 14:16:22 DEBUG (MainThread) [mysensors.gateway_mqtt] Receiving 3;0;0;0;0;20
2020-05-04 14:16:22 WARNING (MainThread) [mysensors] Node 3 is unknown
2020-05-04 14:16:22 ERROR (MainThread) [mysensors.handler] Node 3 is unknown, will not add child 0

Things that I have allready tried:

• restore of a snapshot from when MQTT was still working. Both with Restore and Restore & Wipe = no luck
• disabling and re-enabling of the Mysensors-integration = no luck
• disabling the persistance-part in the config = no luck.
• restarting the MQTTGateway = no luck.
• restarting almost everything else including emptying the MQTT-queue= no luck
• update to 0.109 = no luck.

Does anybody have an idea what could be causing this issue?

Many thanks & Stay healthy!
Hans.

Posts: 1

Participants: 1

Read full topic

@whoismoses wrote:

I’m having trouble with the fold-entity-row. It works, but I can’t get the formatting correct.

  - title: Office
    path: office2
    icon: mdi:desktop-mac
    cards:
        # The markdown card will render markdown text.
      - type: markdown
        content: >
          ## Office
      - type: custom:fold-entity-row
        head:
          type: section
          label: Lights
        open: true
        entities:
          - entity: group.basement_desk_lamps
            name: Lamps
            icon: mdi:lamp
          - type: custom:slider-entity-row
            entity: light.basement_office_backlight
            name: Backlight
            icon: mdi:lamp
            toggle: true
            step: 5

Produces

image1052×460 15.4 KB

It functions correctly, however I can’t seem to get it to show the card background like below or like the examples on github.

image1030×436 15.1 KB

Posts: 1

Participants: 1

Read full topic

@Daniel-san wrote:

Hi guys,

I ran Hassio on UNraid for over a year now without any real problems. I recently purchase a used NUC to dedicate to HA only, but I ended up installing ESXi 6.7 on it and running Hassio as it’s only VM.

Downloaded the VMDK from this site, and restored by latest snapshot. HA is working OK now… but,

Here are my issues so far:

1. I can’t do snapshots when the VM is turned on. it tells me the file is locked. (works when the VM is off)
2. I can’t grow the disk (even if it’s powered off) it says “Failed to reconfigure virtual machine Hassio3. Invalid operation for device ‘1’.”

Here are the ESXi logs:

2020-05-02T16:48:33.341Z| vmx| I125: Log for VMware ESX pid=2099610 version=6.7.0 build=build-8169922 option=Release
2020-05-02T16:48:33.341Z| vmx| I125: The process is 64-bit.
2020-05-02T16:48:33.341Z| vmx| I125: Host codepage=UTF-8 encoding=UTF-8
2020-05-02T16:48:33.341Z| vmx| I125: Host is VMkernel 6.7.0
2020-05-02T16:48:33.320Z| vmx| I125: VTHREAD 37369047040 "vmx" wid 2099610
2020-05-02T16:48:33.320Z| vmx| I125: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL
2020-05-02T16:48:33.320Z| vmx| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2020-05-02T16:48:33.320Z| vmx| I125: ConfigDB: Failed to load /usr/lib/vmware/config
2020-05-02T16:48:33.320Z| vmx| I125: DictionaryLoad: Cannot open file "//.vmware/config": No such file or directory.
2020-05-02T16:48:33.320Z| vmx| I125: ConfigDB: Failed to load ~/.vmware/config
2020-05-02T16:48:33.330Z| vmx| I125: OBJLIB-LIB: ObjLibPlugins_Load: Loading plugin directory '/usr/lib64/vmware/plugin/objLib'
2020-05-02T16:48:33.330Z| vmx| I125: OBJLIB-LIB: ObjLibLoadPlugin: Loading plugin 'objLib/vsanObjBE.so'
2020-05-02T16:48:33.332Z| vmx| I125: PluginLdr_Load: Loaded plugin 'objLib/vsanObjBE.so' from '/usr/lib64/vmware/plugin/objLib/vsanObjBE.so'
2020-05-02T16:48:33.332Z| vmx| I125: ObjLibPluginInit: Initialized plugin
2020-05-02T16:48:33.332Z| vmx| I125: VsanBackend_GetAPI: Received request for API com.vmware.plugin.objlib.backend.api@1.0
2020-05-02T16:48:33.332Z| vmx| I125: OBJLIB-LIB: ObjLib_RegisterDynamicBE: Back-end 'vsan' found and registered as type 3
2020-05-02T16:48:33.332Z| vmx| I125: 2099610:VVOLLIB : VVolLib_IpcInit:208: IPC timeouts set to: connect = 30 sec, send = 30 sec, receive = 200 sec
2020-05-02T16:48:33.332Z| vmx| I125: 2099610:VVOLLIB : VVolLib_GetSoapContext:379: Using 30 secs for soap connect timeout.
2020-05-02T16:48:33.332Z| vmx| I125: 2099610:VVOLLIB : VVolLib_GetSoapContext:380: Using 200 secs for soap receive timeout.
2020-05-02T16:48:33.332Z| vmx| I125: OBJLIB-LIB: Objlib initialized.
2020-05-02T16:48:33.332Z| vmx| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2020-05-02T16:48:33.332Z| vmx| I125: DictionaryLoad: Cannot open file "//.vmware/config": No such file or directory.
2020-05-02T16:48:33.332Z| vmx| I125: DictionaryLoad: Cannot open file "//.vmware/preferences": No such file or directory.
2020-05-02T16:48:33.340Z| vmx| I125: lib/ssl: OpenSSL using FIPS_drbg for RAND
2020-05-02T16:48:33.340Z| vmx| I125: lib/ssl: protocol list tls1.2
2020-05-02T16:48:33.340Z| vmx| I125: lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)
2020-05-02T16:48:33.340Z| vmx| I125: lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES
2020-05-02T16:48:33.341Z| vmx| I125: FILE: FileCreateDirectoryEx: Failed to create /tmp. Error = 17
2020-05-02T16:48:33.341Z| vmx| I125: FILE: FileCreateDirectoryEx: Failed to create /tmp/vmware-root. Error = 17

it looks like some config files are missing.

When you download the VMDK from here, it doesn’t come with the VMX file that’s needed to register the VM. so you have to create one… I’m wondering if this is where things went wrong.

Posts: 3

Participants: 3

Read full topic

@ausserirdischegesund wrote:

I am just starting out to use automations in earnest, so I am basically at a blank slate. I have not tried this yet, but it is my gut feeling, that I want my house to have several “modes”:
Away/somebody is home
Holiday mode (everybody is away for more than 2 days or so)
workday/sunday
“baby is seleeping mode” (lights are dimmed somewhat and faded in slowly, music turned down)
Alarm mode (e.g. smoke alarm went off: All lights full power, all hot appliances off, all speakers playing alarm sound)

What do you use? Or is this a flawed idea that does not work in the long run? Technically I read that most people represent this with input booleans, which seems about right, this should make it easy to include in automations?

Posts: 2

Participants: 2

Read full topic

@dkagedal wrote:

Using https://www.home-assistant.io/integrations/light.switch/ is a simple way to turn a dumb switch into something that will appear as a light to HA (and to Google Assistant etc).

To configure it, you write something like:

light:
  - platform: switch
    name: Kontorsvägg
    entity_id: switch.nexa_7

This will create an entity with a name that is derived from the name you provide. I just wish that it wouldn’t conflate the entity name with the name I want to show in the Lovelace UI. If I want to tweak the “friendly” name to improve the UX, that will also rename the entity name, breaking anything that depends on it.

And can you tell what the entity name for the above example is? In case you wonder, it’s light.kontorsvagg which is not so pretty.

This is probably a commen theme in entities defined like this. I can see a couple of ways forward:

1. Add a “friendly name” configuration parameter, and let the “name” be the entity id.
2. Integrate this much better into HA so I can configure it in the UI instead and let me tweak the UI description freely.

Posts: 7

Participants: 2

Read full topic

@fchiari wrote:

Hi,
After upgrading the system to the latest HA version I’m receiving the following error:
“Invalid config for [group]: [view] is an invalid option for [group]. Check: group->group->default_view->view.”
Since I don’t understand where the issue is, I would really appreciate for your help.
Many thanks.

The groups.yaml file content is:

#Groups
default_view:
  name: Home
  view: yes
  icon: mdi:home-assistant
  entities:
  - sun.sun
  - sensor.Giardino
  - sensor.Salone
  - sensor.Camera
  - sensor.yr_symbol
  - group.home_grate
  - camera.foscam_camera
  - group.home_climatizzazione
  - group.home_servizi
#  - alarm_control_panel.securitas_2348936

home_grate:
  name: Grate
  view: no
  entities:
  - switch.gratecucina
  - switch.gratesalone

home_servizi:
  name: Servizi
  view: no
  control: hidden
  entities:
  - switch.cancello
  - switch.light_faro
  - input_boolean.auto_faro
  - switch.light_lucecancello
  - switch.irr_prato
  
home_climatizzazione:
  name: Climatizzazione
  view: no
  control: hidden
  entities:
  - switch.h2ocaldaiano
  - switch.riscaldamento
  - input_datetime.start_risc

irrigazione:
  name: Irrigazione
  view: yes
  icon: mdi:access-point-network
  control: hidden
  entities:
  - timer.prato_orto
  - timer.veranda
  - timer.cucina
  - timer.balcone
  - sensor.Giardino
  - sensor.Salone
  - sensor.Camera
  - group.irr_prato
  - group.irr_orto
  - group.irr_veranda
  - group.irr_cucina
  - group.irr_balcone
  
irr_prato:
  name: Prato
  view: no
  control: hidden
  entities:
  - input_select.irr_level_prato
  - switch.irr_prato
  - input_number.timer_prato

irr_orto:
  name: Orto
  view: no
  control: hidden
  entities:
  - input_select.irr_level_orto
  - switch.irr_orto
  - input_number.timer_orto

irr_veranda:
  name: Veranda
  view: no
  control: hidden
  entities:
  - input_select.irr_level_veranda
  - switch.irr_veranda
  - input_number.timer_veranda

irr_cucina:
  name: Cucina
  view: no
  control: hidden
  entities:
  - input_select.irr_level_cucina
  - switch.irr_cucina
  - input_number.timer_cucina

irr_balcone:
  name: Balcone
  view: no
  control: hidden
  entities:
  - input_select.irr_level_balcone
  - input_number.timer_balcone

riscaldamento:
  name: Riscaldamento
  view: Yes
  icon: mdi:fire
  control: hidden
  entities:
  - sun.sun
  - sensor.Giardino
  - sensor.Salone
  - sensor.Camera
  - sensor.yr_symbol
  - group.ct_riscaldamento
  - group.ct_h2o_solare


condizionatori:
  name: Condizionatori
  view: Yes
  icon: mdi:air-conditioner
  control: hidden
  entities:
  - sun.sun
  - sensor.Giardino
  - sensor.Salone
  - sensor.Camera
  - sensor.yr_symbol
  - group.ct_condizionamento
  - group.ct_h2o_solare

ct_h2o_solare:
  name: Acqua solare
  view: No
  control: hidden
  entities:
  - climate.H2O_solare
  - switch.h2ocaldaiano
  - switch.resistsolterm

ct_riscaldamento:
  name: Riscaldamento
  view: No
  control: hidden
  entities:
  - input_datetime.start_risc
  - input_datetime.stop_risc
  - climate.piano_terra
  - climate.primo_piano
  - switch.riscaldamento
  - switch.riscpianoterra
  - switch.riscprimopiano
  - switch.risccaldaia

ct_condizionamento:
  name: Condizionamento
  view: No
  control: hidden
  entities:
  - climate.salone
  - climate.camera
  - climate.studio
  
giardino:
  name: Giardino
  view: yes
  icon: mdi:nature-people
  control: hidden
  entities:
  - sun.sun
  - sensor.Giardino
  - sensor.Salone
  - sensor.Camera
  - sensor.yr_symbol
  - camera.foscam_camera
  - group.giardino_servizi
  - group.giardino_sensori

giardino_servizi:
  name: Servizi
  view: no
  control: hidden
  entities:
  - switch.cancello
  - switch.light_faro
  - switch.light_lucegiardino
  - switch.light_lucecancello
  - switch.audiogiardino
  - switch.fontanella
  - switch.antitopi

giardino_sensori:
  name: Sensori vari
  view: no
  control: hidden
  entities:
  - binary_sensor.Asciutto
  - binary_sensor.Luce
  - binary_sensor.Fotovoltaico
  - binary_sensor.Acqua_solare
  
my_home:
  name: Servizi vari
  view: yes
  icon: mdi:home
  control: hidden
  entities:
  - sun.sun
  - sensor.Giardino
  - sensor.Salone
  - sensor.Camera
  - sensor.yr_symbol
  - group.salone_servizi
  - group.camera_servizi

salone_servizi:
  name: Servizi salone
  view: no
  control: hidden
  entities:
  - switch.co2
  - switch.osmosi
  - switch.light_salesalone
  - switch.lavatrice
  - input_number.timer_lavatrice

camera_servizi:
  name: Servizi camera
  view: no
  control: hidden
  entities:
  - switch.vape
  - switch.light_salecamera
  - switch.citofono

ced:
  name: CED
  view: Yes
  control: hidden
  entities:
  - group.ced_power
  - group.ced_network
  - group.ced_synology

ced_power:
  name: Power
  view: no
  control: hidden
  entities:
  - switch.modemtim
  - switch.myhome_1
  - switch.myhome_2

ced_network:
  name: Network
  view: no
  control: hidden
  entities:
  - sensor.speedtest_ping
  - sensor.speedtest_download
  - sensor.speedtest_upload

ced_synology:
  name: Synology
  view: no
  control: hidden
  entities:
  - sensor.synology_dsm_cpu_load_total
  - sensor.synology_dsm_memory_usage_real
  - sensor.synology_dsm_volume_used_volume_1
  - sensor.synology_dsm_status_volume_1
  - sensor.synology_dsm_status_sda
  - sensor.synology_dsm_temperature_sda
  - sensor.synology_dsm_status_sdb
  - sensor.synology_dsm_temperature_sdb

my_timers:
  name: Timers
  view: yes
  control: hidden
  icon: mdi:timer
  entities:
  - timer.irr_auto_off
  - timer.prato_orto
  - timer.veranda
  - timer.cucina
  - timer.balcone
  - timer.faro
  - timer.lavatrice_on
  - timer.lavatrice_off
  - input_number.timer_prato
  - input_number.timer_orto
  - input_number.timer_veranda
  - input_number.timer_cucina
  - input_number.timer_balcone
  - input_number.timer_faro
  - input_number.timer_lavatrice

Posts: 3

Participants: 3

Read full topic

@ThisBytes5 wrote:

I want to be able to send reminders as my calendar events start, few minutes before, so far I haven’t really found a way to do so without any sort of search/filter.

How would I go about getting the next item/event in the calendar, and setting an automation up for X minutes before the event start?

Posts: 1

Participants: 1

Read full topic

@raphaelben55 wrote:

Hello,

I want to trigger a notification using the camera recording state as a condition but I can’t find how.

I tried this but it doesn’t work:

- alias: 'Alert_MotionSensor'
  trigger:
    platform: state
    entity_id: binary_sensor.motionsensor
    to: 'on'
  condition:
      - condition: template
        value_template: "{% if is_state('camera.salon', 'recording') %}true{% endif %}"
  action:
    service: notify.gotify_1
    data:
      title: "Alert"
      message: "Motion Detected[]"

My camera is either showed as “Idle” or “Recording” in home assistant (that part is managed by Synology surveillance station + an IFTT webhook request without any problem)
Before I was using a switch related to the Home Mode on synology SS put it doesn’t work anymore, that’s why I want to use the Camera recording state now.

Thanks in advance for the help.

Posts: 3

Participants: 2

Read full topic

@membersound wrote:

I’m trying to create a trigger based on two sensors. Therefore, I let one of the triggers trigger the automation, and added the 2nd sensor as condition:

trigger:
  platform: numeric_state
  entity_id: sensor.dryer_energy_power
  below: '2'
  for: '00:02:00'
conditions:
  - condition: numeric_state
    entity_id: sensor.dryer_energy_current
    below: '0.1'

Question: how often does this trigger execute? Only once if the power state was exactly 2 minutes below 2W? And if the condition was not met, the trigger is not executed again?
Or will the trigger execute every minute as long as it did not pass the condition?

Thanks

Posts: 6

Participants: 3

Read full topic

@Aephir wrote:

This is to chronicle the issues I have had in moving my home assistant instance from my old computer to an old server i set up. I hoped it would be as simple as copying my old persistent dir/files and restarting Docker containers, but not quite. However, it only took a few hours to get to something that’s usable, so it’s certainly easier than the last few times (e.g. when I switched from RPi2 to RPi3 with HASS v. 0.38, or back when i switched from venv to Docker and RPi to NUC-like computer)!

I’ll update with solutions as I find them, but you should feel more than welcome to chime in if you have any (also if the solutions I’ve found are less than ideal). Hopefully this can serve as a troubleshooting guide of sorts, if anyone else tries this and runs into similar issues.

My install was in Docker, running Home Assistant 0.109.3. Of potential interest, I am also running the following Docker containers (all updated to tag=latest on 2020-05-03):

• acockburn/appdaemon
• linuxserver/letsencrypt
• linuxserver/duckdns
• marthoc/deconz
• trafex/alpine-mosquitto
• mariadb

I am also using the Android and iOS apps/integrations, as well as the integrations listed below.

I started by setting up the new server with the static local IP of the old, and the did an rsync with -aH flags (instead of scp, to retain ownership and permissions) of all my docker containers persistent directories form the old computer to new server.

Below is a list of the issues I found, and the solutions. I’ll update this post as needed:

1. First issue was MariaDB [Solved], where HASS couldn’t connect. But simply deleting the MariaDB persistent docker directory, and restarting the container fixed that.

2. Second issue was that all the Long Lived Access Tokens disappeared [Solved/Mostly solved]. An annoyance, but I re-created new ones, and put them in the relevant places (mostly in my secrets.yaml and a few other config files). It would be nice if I could retain them though (did I do something stupid since they weren’t?).

3. Next is the phone apps.

   3a. The iOS App [SOLVED] couldn’t connect, so I tried resetting the app/connection (in the app). When trying to set it up again, it keept giving “Error: Can't build API URL” when I try to edit the connection. After restarting both HASS and the app, I tried the app. It found my (external DuckDNS) HASS address, but when logging in, I got the error “Error: Response status code was unacceptable: 401”. I am connected to the external address (DuckDNS address) via browser at the same time and that works fine. However, manually entering the local IP during setup works. Well, mostly. It automatically added my local IP as “external URL” in the app, but I could manually change this afterwards, so now both local and DuckDNS address works.

   3b. For the Android App [SOLVED], I have both the official app and the “HA Client” (I’d prefer using the official, but the HAClient is just sooo much faster. Shame it doesn’t support many of the custom cards I’m using, though). I also had issues, and ended up removing the integration from the HASS UI config, and set up again. For the HAClient, it worked from there, for the official app, I needed to force close (well, I rebooted the phone, but should be the same) for it to accept. Fairly painless.

4. Next issue was AppDaemon [SOLVED, but why?]. I changed my long lived access token in “secrets.yaml”, which is referenced in appdaemon.yaml, and left everything else as is. But AppDaemon couldn’t connect to HASS. It could connect to Mosquitto, and deliver its birth payload. For this one, I can’t really be of much help. From yesterday around 22:00 through today at 10:13 the logs kept showing “WARNING HASS: Disconnected from Home Assistant, retrying in 5 seconds”. Then suddenly 5 seconds after the last “warning”, it connected. I have absolutely no idea why, since I wasn’t messing with anything related to AppDaemon at that time. So sorry, no help here if you run into issues.

5. Final issue found so far, integrations [NOT SOLVED]. I can see my integrations via HASS UI config, but only if I’m connecting via local IP! If I’m connecting via. my DuckDNS address, it just shows Nothing configured yet: Seems like you don't have any integrations configured yet. Click on the button below to add your first integration!. If I do click that, it will show Please wait while the integration is being installed. But it will do this forever, while I (simultaneously) can see them when browsing to my local HASS IP.

So any ideas, especially on #5 would be welcomed! Any notes on anything else would also be fine, and I’ll update this as needed.

For a sense of completion, here’s a list of integrations used, that I didn’t change in any way (so far they seem to work fine with after moving, no work required):

• Google Cast
• Certificate Expiry
• deCONZ
• Font Awesome
• HACS
• IFTTT
• Home Assistant iOS
• Life360
• MQTT
• OwnTracks
• Shopping list
• SONOS
• Belkin WeMo
• Z-wave
• Home Connect

Posts: 1

Participants: 1

Read full topic

@Makis wrote:

Something went wrong and I need to reinstall HA. I have install HA following this guide

Since ubuntu is installed, can I just follow the following to reinstall HA or I must (how?) uninstall it first?

Copy each line of the below commands and paste them into a terminal/Putty window, and execute them one at a time.

add-apt-repository universe
sudo -i
apt-get update
apt-get install -y software-properties-common apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
systemctl disable ModemManager
systemctl stop ModemManager
curl -fsSL get.docker.com | sh
Now the machine has everything it needs to run Home Assistant. The following command will download, install and get Home
Assistant - Supervised up and running for you;
curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s

Posts: 2

Participants: 2

Read full topic

@mkanet wrote:

I accidentally created SEVERAL duplicate entities while attempting to register my daughter’s android phone Home Assistant companion app. I didn’t realize it was creating a bunch of duplicate entities in Home Assistant since the interface wasn’t displaying correctly on her tiny phone screen.

I tried rebooting HASSIO several times… and then attempted removing the entities using HA’s GUI under Configuration/Entities… however, HA complains that " Only 0 selected entities can be removed. Entities can only be removed when the integration is no longer providing the entities."

Is there a way to do this via the GUI? If not, then I guess I’ll have to carefully remove the duplicates in the below files (after I stop HASSIO).

 /config/.storage/core.config_entries
 /config/.storage/core.entity_registry

Lastly, I also have some entities created by the Alexa Media Player addon that are showing as “Unavailable” with a red exclamation mark. I can’t remove those either under Configuration/Entities. Would I have to remove these entities via the above files too… or is there a better way to remove these?

Posts: 2

Participants: 2

Read full topic

@poudenes wrote:

Hi All,

Is it possible to change the value in Zwave2MQTT?

Door/Window Open > on
Door/Window Closed > off

Or do I need to change it with a customize part?

Posts: 1

Participants: 1

Read full topic

@spartanunitato wrote:

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

Posts: 1

Participants: 1

Read full topic