@bphillips921 wrote:

I can see the Hass.io menu tab in my left-hand side menu, but when I click it nothing happens, I just get a white page (192.168.1.111:8123/hassio).

Has anyone else had this issues and solved it?

Posts: 3

Participants: 2

Read full topic

@mattmoo wrote:

Hi all,
I’m just getting into Home Assistant, finding it really interesting so far, but please forgive me if there’s something obvious I’m missing. I’m testing out the system with a USB powered Aeotec Multisensor 6.
I’ve got it working as far as I can see, but I would kind of like it to take far more frequent measurements. If I set the Wakeup Interval to below 240s on the Z-Wave Network Management page, it seems to reset to 240s. Is this by design? Perhaps I need to set it elsewhere?

Posts: 6

Participants: 3

Read full topic

@michaelblight wrote:

My tuya config has been working for some months with lights, switches and a camera, but from yesterday nothing shows up in HA (0.103.3). The only “change” was an automatic reboot of the Windows PC hosting HA (via a VM), presumably for forced software updates. There is nothing in the logs and calling tuya.pull_devices has no effect. I can still see the devices in the TuyaSmart app.

Has anybody had similar issues lately?

Posts: 2

Participants: 2

Read full topic

@Makis wrote:

Hi
I have hassiso on rasberry b3+ with deconz. Today denconz usb de-attached from rasb. I reconnected the deconz usb and HA was working ok but all my devices connected to deconz was not responding.
I did a restart and now I can not connect to HA at all. I tried to to start HA without deconz usb but again HA is unreachable.
What I could do?

I am on 1.105.02 version and the safe mode won’t work also.

Posts: 8

Participants: 2

Read full topic

@scubammx wrote:

hallo , i have migrated my hass from raspberry to VM ( ubuntu system with virtualbox and hassio vdi ) , all seems working correctly but checking the logs i have tons of errore every minute …
below you can find one , can you help me to check and identity how to solve ?the migration had saved me a lot of time, so i would like to avoid to configure again all the system…
‘’’’’’’’’’’’’’’’’’’
‘‘Error executing query: (sqlite3.DatabaseError) database disk image is malformed
[SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id) VALUES (?, ?, ?, ?, ?, ?, ?)]
[parameters: (‘state_changed’, ‘{“entity_id”: “sensor.powr2_energy_current”, “old_state”: {“entity_id”: “sensor.powr2_energy_current”, “state”: “unknown”, “attributes”: {“unit_of_me … (510 characters truncated) … :00”, “last_updated”: “2020-02-14T09:11:06.227675+00:00”, “context”: {“id”: “a603c2d9d603426496e46af9877f451f”, “parent_id”: null, “user_id”: null}}}’, ‘LOCAL’, ‘2020-02-14 09:11:06.227746’, ‘2020-02-14 09:11:06.486654’, ‘a603c2d9d603426496e46af9877f451f’, None)]
(Background on this error at: http://sqlalche.me/e/4xp6’
‘’’’’’’

Posts: 4

Participants: 3

Read full topic

@sen wrote:

I experience a large delay with every action I do on the server controls page from HA.

• When I want to check my config, it takes easily 15 minutes.
• Reload automations around 5 minutes
• Restart the server + 5 minutes before it becomes unavailable

So it looks like there is a large delay before the command is sent or executed on the server.
The rest of my HA setup is very quick and responsive.
I’m running HA on a Synology NAS

Anyone else experiencing this issue?
Or any idea on how I can find out what’s wrong?

Posts: 1

Participants: 1

Read full topic

@rednas wrote:

Currently I have this automation:

- alias: 'Device State Change Alert'
  trigger:
    platform: state
    entity_id: person.P1, person.P2
  condition:
    condition: template
    value_template: '{{ trigger.to_state.state != trigger.from_state.state }}'
  action:
    - service: notify.notify
      data_template:
        message: >
          {{ trigger.to_state.attributes.friendly_name }} is at {{ trigger.to_state.state }}.
        title: ""

How can I change trigger.to_state.state to a value where it returns the friendly name? Currently it returns the correct name for custom zones, however for the home zone it returns “home” and when not at home it return “not_home”. I would like to have the friendly names returned instead of “home” and “not_home”.
How can I change this?
It’s not trigger.to_state.attributes.friendly_name as this returns the name of the person, which is quite strange I would say.

Posts: 2

Participants: 2

Read full topic

@vindicator wrote:

I’m just checking in here first before submitting the issue to the HA github project.

Everything is running off of the same system/localhost.

Developer Tools -> SERVICES
Service: tts.marytts_say
Service data: {“message”: “hello world”}

---

Feb 13 02:24:45 computerName hass[196024]: 2020-02-13 02:24:45 ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

Feb 13 02:24:45 computerName mpd[195474]: exception: Failed to decode http://<private_ip>:8123/api/tts_proxy/2aae6c35c94fcfb415dbe95f408b9ce91ee846ed_en_us_5470814253323254900_marytts.wave_file

Feb 13 02:24:45 computerName mpd[195474]: exception: nested: CURL failed: The requested URL returned error: 404 Not Found

Feb 13 02:24:45 computerName mpd[195474]: player: played “http://<private_ip>:8123/api/tts_proxy/2aae6c35c94fcfb415dbe95f408b9ce91ee846ed_en_us_5470814253323254900_marytts.wave_file”

Feb 13 02:24:46 computerName hass[196024]: 2020-02-13 02:24:46 ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

Feb 13 02:24:46 computerName hass[196024]: 2020-02-13 02:24:46 ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

Feb 13 02:24:46 computerName hass[196024]: 2020-02-13 02:24:46 ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

Feb 13 02:24:46 computerName hass[196024]: 2020-02-13 02:24:46 ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

Feb 13 02:24:46 computerName hass[196024]: 2020-02-13 02:24:46 ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

---

ls -la output: -rw-r–r-- 1 hass hass 170444 Feb 13 02:24 2aae6c35c94fcfb415dbe95f408b9ce91ee846ed_en_us_5470814253323254900_marytts.wave_file

file output: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 48000 Hz

ffplay plays that file when I give myself permission.

I’d like to be able to see/know what HA is receiving to prompt the “Wrong tts file format” log entry.

Posts: 1

Participants: 1

Read full topic

@blackskull182 wrote:

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

Posts: 1

Participants: 1

Read full topic

@denis.besir wrote:

I need a automation that runs every wednesday but only if the week number is even.

Posts: 4

Participants: 3

Read full topic

@GTaylor wrote:

Hello guys!
I know there are a lot of topics about it, but i’ve implemented all tips and it still doesn’t work, i lost days and nights trying to fix this

My HA is runing on VirtualBox machine, i’ve a local IP 192.168.15.201 for it (fixed on router by the MAC address).

DuckDNS with following config:

 lets_encrypt:
   accept_terms: true
   certfile: fullchain.pem
   keyfile: privkey.pem
 token: DUCK_DNS_TOKEN
 domains:
   - EXTERNAL_URL.duckdns.org
 seconds: 300

NGINX with the config:

 domain: EXTERNAL_URL.duckdns.org
 certfile: fullchain.pem
 keyfile: privkey.pem
 hsts: max-age=31536000; includeSubDomains
 cloudflare: false
 customize:
   active: false
   default: nginx_proxy_default*.conf
   servers: nginx_proxy/*.conf

DNSMask with the config:

 defaults:
   - 8.8.8.8
   - 8.8.4.4
 forwards: []
 hosts:
   - host: EXTERNAL_URL.duckdns.org
     ip: 192.168.15.201

My configuration.yaml

 default_config:
 
 logger:
 system_log:
         max_entries: 100
 
 http:
         base_url: https://EXTERNAL_URL.duckdns.org
 
 tts:
         - platform: google_translate
           base_url: https://EXTERNAL_URL.duckdns.org
     	  #base_url: http://192.168.15.201:8123

My openned ports on router:

image1057×339 20.3 KB

I can access my HA by http://192.168.15.201:8123 or https://EXTERNAL_URL.duckdns.org both works great, i can control the Google Home Mini, play music or mp3 audio link (using Service > media_player.play_media)

HA994×624 253 KB

But if i try to use the service tts.google_translate_say I always get the error Error on init TTS: No TTS from google_translate

On my logs, when start the server:

 INFO (SyncWorker_3) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
 INFO (MainThread) [homeassistant.setup] Setting up tts
 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=tts, service=google_translate_say>

When i try to use the service tts.google_translate_say:

 ERROR (MainThread) [homeassistant.components.google_translate.tts] Timeout for google speech
 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for 'hello'

---

Anybody can help me ??

Posts: 1

Participants: 1

Read full topic

@RalfP wrote:

Hi folks,

after a long time of stability in my config I’m trying to do a new move.
As I’m changing my power supplier to aWattar I can read the hourly prices of electricity. So far, so good.

Now I want to put a part of the values to a simple list like this:

{"data":[21.2,22.3,17.5,...]} 

I want to use this list as JSON table in Node-Red later on.
I have all the single values and the calculation model is right.
It’s just a problem in building the list…

#aWattar Strompreise
  - platform: rest
    resource: https://api.awattar.de/v1/marketdata
    name: "awattar"
    value_template: "{{ (value_json.data[0]) }}"
    json_attributes:
      - data
    scan_interval: 60
  - platform: template
    sensors:
      awattar_json:
        friendly_name: "aWattar JSON table"
        value_template: >-
          {% set awattar_json =
            {"data":
            {
            ((((state_attr('sensor.awattar', 'data')[0].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),
            ((((state_attr('sensor.awattar', 'data')[1].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),
            ((((state_attr('sensor.awattar', 'data')[2].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),
            ((((state_attr('sensor.awattar', 'data')[3].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),
            ((((state_attr('sensor.awattar', 'data')[4].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2)
            }}
          %}

I’ve been fiddeling around with this now for two days in a row but I only get any result if I build up the list like this:

{"0":"22.3",'"1":"23.8","2":"17.5",...}

This format I can’t get my head around in Node-Red for further processing. Basically I want to search for minima, 2 hours in a row minima, 3 hours in a row minima, …

With the current extract from my config I get the following error message (not unexpected):

Failed config
  sensor.template: 
    - Invalid config for [sensor.template]: invalid template (TemplateSyntaxError: expected token ':', got ',') for dictionary value @ data['sensors']['awattar_json']['value_template']. Got '{% set awattar_json =\n  {"data":\n  {\n  ((((state_attr(\'sensor.awattar\', \'data\')[0].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),\n  ((((state_attr(\'sensor.awattar\', \'data\')[1].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),\n  ((((state_attr(\'sensor.awattar\', \'data\')[2].marketprice)|float*100)/1000) | multiply(1.19)  + 19.22) |round(2),\n  ((((state_attr(\'sensor.awattar\', \'data\')[3].marketprice)|float*100)/1000) | multiply(1.19)  +.... (See ?, line ?).

Any simple example in how to build a list is highly appreciated, I’ve read the doc on templates over and over again now. When the list is filled I’ll probably have to use the “to_json” filter. But that’s part two of the cake…

Best regards
Ralf

Posts: 2

Participants: 2

Read full topic

@ColinSchubert wrote:

Hey everybody,

First of all, I am pretty new to the whole Home Assistant thing.
I am using HassOS 3.10 on a Raspberry PI 3B and so far it worked out pretty well for me. Now I’m desperately trying to configure the Fritz_Netmonitor Component. I added the following to the configuration.yaml:

sensor:
  - platform: fritzbox_netmonitor
    host: 192.168.178.1
    name: "Network Monitor"

But so far, even after restarting the whole Home Assistant multiple times, the netmonitor refuses to show up as a sensor and therefore can not be added to the UI.
Here is the Traceback:

fritzbox_netmonitor: Error on device update!

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/fritzconnection/core/fritzconnection.py", line 204, in call_action
    service = self.device_manager.services[service_name]
KeyError: 'WANCommonIFC1'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 304, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 461, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 240, in wrapper
    result = method(*args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/fritzbox_netmonitor/sensor.py", line 119, in update
    self._is_linked = self._fstatus.is_linked
  File "/usr/local/lib/python3.7/site-packages/fritzconnection/lib/fritzstatus.py", line 41, in is_linked
    'GetCommonLinkProperties')
  File "/usr/local/lib/python3.7/site-packages/fritzconnection/core/fritzconnection.py", line 206, in call_action
    raise FritzServiceError(f'unknown service: "{service_name}"')
fritzconnection.core.exceptions.FritzServiceError: unknown service: "WANCommonIFC1"

What can I do?

Greetings,
Colin

Posts: 4

Participants: 3

Read full topic

@JeeCee wrote:

Hi all,
I’ve searched the forums, but I could not find anything which solved my problem.
I’m sure it’s a small config error but I’m searching for a week now, time to call in the troops.

I have some ESPeasy devices which are connected to the Moscquitto broker add-on.
I used discovery before (with rules in EASPeasy) and that worked but I found it more tedious to keep the easpEasy rules up to date so I wanted to migrate to configuring them in HAS.

Developer Tools -> Listen to ‘#’ reveals all topics in the expected scheme.
However, in Developer Tools - States the sensors show “unavailable”.

I’m running HASS.io version 3.10 and HAS version 200.

My broker config is default:

logins: []
anonymous: false
customize:
  active: false
  folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem

I have created an HAS user ‘MQTT’.
The configuration.yaml section is:

mqtt:
  broker: 192.168.2.100
  username: mqtt
  password: *****
#  discovery: true
#  discovery_prefix: homeassistant

My sensors are configured as follows:

sensor:
######################################
# Elec Meters
######################################
  - platform: mqtt
    name: "Souterrain Electricity Power"
    state_topic: "homeassistant/ESPElecMeters/Electricity-SOU/Power"
    availability_topic: "homeassistant/ESPElecMeters/available"
    device_class: "power"
    unit_of_measurement: "W"
    #icon: mdi:

Other sensors:

  - platform: mqtt
    state_topic: "ESP-Sauna/Inside/Humidity"
    name: "Sauna Inside Humidity"

Generate ‘unknown’ state
etc.

Related ESPeasy config:

Controller Publish:	homeassistant/%sysname%/%tskname%/%valname%
Controller LWT Topic: homeassistant/%sysname%/available
Unit name: ESPElecMeters
Device name: Electricity-SOU
Device values: Power (and usage)

I am at a loss what I am doing wrong.
Thanks for any help!

Posts: 4

Participants: 3

Read full topic

@chrisjcbt wrote:

Hi folks,

I have a couple of Logitech Harmony Hubs, both with XMPP enabled for Home Assistant integration. configuration.yaml is below:

remote:
  - platform: harmony
    name: Lounge
    host: 192.168.10.96

  - platform: harmony
    name: Kitchen
    host: 192.168.10.97

I run a unifi network, and have given the hubs static IPs, both hubs have a very strong wifi signal. The lounge hub has an automation attached to it. When the Hub is turned On, then a Fibaro Roller Shutter 3 is triggered. Along with the reverse being true when the hub is switched Off. The automation is in NodeRed, and the automation is set to only trigger once on State Change.

A couple of weeks back the motor that the Fibaro Roller Shutter 3 controls burnt out. I could hear the motor being repeatedly triggered. The whole setup has been installed for around 5 months, and I hadn’t seen/heard this before.

I was about to replace the motor when I checked the Logbook for the setup in the lounge. If you see the attached screenshot, the Harmony Hub is constantly flipping between “unavailable” and “off”. This is what is causing the automation to trigger, and ultimately why I think the motor burnt out. If I replace the motor now, this is going to happen again.

Screenshot 2020-02-14 at 3.10.49 pm742×715 60.7 KB

Is anyone else seeing this in their Logbooks for their HarmonyHubs - and if so - any alternative integration recommendations for the harmony platform?

Thanks,
Chris

Posts: 1

Participants: 1

Read full topic

@gtj wrote:

Hello,

I have suceesfully installed Homeassistant on a VM and now I’m trying to utilize my Zstick. The system don’t seem to recognize the stick.
The path /dev/ttyAMC0 is not right.
ls /dev/tty* reports:
/dev/ttyS0
/dev/ttyS1
/dev/ttyS2
/dev/ttyS3

Tried all the above and initially the stick seemed to be included but when I tried to start the ZWave network nothing happens.

I would be grateful if someone could help out with this.

Posts: 2

Participants: 2

Read full topic

@kendall15 wrote:

I can ssh into my home assistant but I can’t get the web interface to load, I jsut get a page that says Unable to connect to Home Assistant.. I am not sure but I think this happened just after I applied the last update. I usually update within hours of getting notified of a new update. The page just fails to load, the log doesn’t seem to indicate any real issues. I have tried rebooting multiple times, cold booting, deleting the groups.yaml file and related config (based a post looking similar), and restoring to a back up from 12/25/2019. All actions so far have resulted in the same issue. Any help would be greatly appreciated.

log1390×93 18.2 KB

Posts: 5

Participants: 2

Read full topic

@AhmadK wrote:

Yesterday I spent plenty of time reading some very interesting articles by Thomas Loven and applying tricks described.
I was mainly interested in a possibility of using constants across various configuration files.
One of the examples - I want to have an input_select with some string constants as options and in a template sensor I need to know which one is selected and act accordingly (or I want to have a binary_sensor that is on when a particular option is selected).
The easiest way is to use strings where required (hardcode) but the code quickly becomes difficult to maintain/change.
One of the options I came across long time ago is to define constants in secret.yaml and then write !secret my_const where I need it. The problem is it doesn’t work in templates. It’s possible to overcome this restriction by creating a template sensor with

value_template: !secret my_const

The issue with this approach is it requires extra measures if you want to use that template sensor’s state (that very my_const) in another template sensor as during HA start your const template sensor might not be created yet when you try accessing its state. It’s manageable but the whole thing gets too complicated for no reason really…
Anyway, I read some docs and examples, went through this forum and realised it might be useful to summarise the experience with anchors as currently it’s a bit spreaded out/not very obvious. So (briefly as it’s already tl;dr) on YAML anchors (just anchors):

1. They cannot be used in templates.
2. They must be declared and used in *the same .yaml file.
3. They can represent any valid YAML structure.

What does it give us?
(1) That’s sad, but sometimes it’s still useful, I’ll show an example below.
(2) No !include will help. That mean that uless you have everything in your configuration.yaml(unrealistic), the most benefits it gives you when used in packages. Anywhere else it’s almost useless, you can do something simple like this but no more:

- platform: template
  sensors:
    ## groung floor ##
    pir_ground_floor_hall_last_triggered:
      value_template: "{{ states('input_datetime.pir_ground_floor_hall') }}"
      <<: &icon
        icon_template: mdi:calendar-clock

    pir_ground_floor_reception_last_triggered:
      value_template: "{{ states('input_datetime.pir_ground_floor_reception') }}"
      <<: *icon

just because it’s difficult to find a place where you can declare it without getting errors from yaml loader.

Packages are different exactly because everything is in one file (and that’s why anchors work in Lovelace configs if you don’t split it up). You just use a dummy place like

homeassistant:
  customize:
    package.node_anchors:
      const_preset_normal: &const_preset_normal 'normal'

at the top of your package file and it works. However, it’s still limiting you by boundaries of 1 file so no way to have global_anchors.yaml and include it where you need it.
But with packages you can make it a little bit less dependent on secrets.yaml - instead of the approach with const template sensors I use this

homeassistant:
  customize:
    package.node_anchors:
      const_preset_normal: &const_preset_normal 'normal'
      template_normal: &template_normal "{{ is_state('input_select.central_heating_preset', 'normal') }}"

      const_preset_night: &const_preset_night 'night'
      template_night: &template_night "{{ is_state('input_select.central_heating_preset', 'night') }}"

input_select:
  central_heating_preset:
    name: preset
    options:
      - *const_preset_normal
      - *const_preset_night

binary_sensor:
  - platform: template
    sensors:
      central_heating_preset_normal:
        value_template: *template_normal

      central_heating_preset_night:
        value_template: *template_night

I still have to hard-code string constants normal and night but they’re in one place so it’s easy to change them/keep synchronised and I can use them in as many places as I need.

The reason we don’t have access to anchors declared in another file is the way HA processes yaml files (as all !secret, !include etc are not part of YAML, it’s HA). I’m not convinced that it’s impossible to implement such a feature. And maybe it’s relatively easy to write a post-processor that loads configuration.yaml, creates a list of files to process, builds a list of anchor definitions and then performs necessary substitutions.

(3) You can use anchors to substitute a value or a piece of a dictionary (I use both approaches in my packages example).

tl;dr #2
I just summarised my and other’s experience with YAML anchors here and added some comments where I thought it wasn’t clear enough.
It’s easy to find some useful topics here (like this or this).
And I’m happy to discuss the matter further or learn something new I have missed in this write-up.

Posts: 3

Participants: 2

Read full topic

@Bacon-Ranch wrote:

Hello,

I am trying to migrate away grom Wink hub and get my devices on a USB z wave device. So far I have had success with light switches, a Jasco fan control that was first a light dimmer then turned into a fan and Schlage door sensors. I do have 3 Schlage locks and a Yale lock, all with z wave+ and keypads.

The locks are an issie. No problem with inclusions, very easy. But both the Yale and the Schlage do not do anything. The main function lock and unlock does not work.

I am sure there is a log to post but not sure which or where it is. Can someone please help, I can always go back to the Wink hub but would rather sort this out.

Posts: 15

Participants: 2

Read full topic

@MarkR wrote:

Hello

I have a sensor in HA that pulls the power (w) reading via MQTT but they are different from what I see on the sonoff page. Anyone know why this would happen please? sometimes it is 1 or 2w other times it is 20-30w different

image1205×86 7.72 KB

  - platform: mqtt
    name: "TV Power"
    state_topic: "tele/tv/SENSOR"
    value_template: '{{ value_json["ENERGY"]["Power"] }}'
    unit_of_measurement: "W"

Posts: 4

Participants: 2

Read full topic