@daxm wrote:

What’s the unit of the offset in the gui in automation?

Posts: 2

Participants: 2

Read full topic

@thuva wrote:

I have hassio running on Pi4. I have Z-Wave dongle and it was working well on USB 2.0. ( Z-Wave.Me USB Stick incl. Z-Way Controller Softw - Z-Wave Plus).

Then I bought Wireless Zigbee CC2531 and flashed CC2531_DEFAULT_20190608. Then I copy and paste the code from (https://github.com/danielwelch/hassio-zigbee2mqtt#highlight highlight-source-yaml) to the configuragion.yaml (automation tag in autaomation.yaml, etc.)

Now the Hassio is not working. I tried to remove zigbee dongle, but still hassio is not reachable.
Does anyone know why this is happening? Now I thought to clean the configuration.yaml manually and try to load.

Anyone know how to configure zigbee and zwave? I know that there is a dognle with both protocol. I do not want that.

Posts: 1

Participants: 1

Read full topic

@shehroz96 wrote:

Hi,

I’m trying to connect sensors from NodeMCU to Home Assistant using MQTT broker. Through serial communication, I sent the values to CloudMQTT and then tried to integrate with Home Assistant. I wasn’t able to automatically have my devices discovered by Home Assistant so I manually described the sensors in configuration.yaml file. Both temperature and humidity sensors are created in Home Assistant but they aren’t able to connect to the values from NodeMCU through MQTT.

However, in ‘developer tools/MQTT’, I’m able to listen to the state_topic of both sensors. I’m not understanding where I’m making the mistake.
I’m using these details:

mqtt: 
    broker: 'URL'
    port: 'Port'
    username: 'Username'
    password: 'Password'
    discovery: 'true'
    discovery_prefix: homeassistant

sensor:
  - platform: mqtt
    state_topic: 'sensor/temp'
    name: 'Temperature Sensor'
    unit_of_measurement: '°C' 
    value_template: '{{ value_json.temperature }}'
    force_update: 'true'
    availability_topic: 'sensor/temp'
    payload_available: 'online'
    payload_not_available: 'offline'
    unique_id: ID
    device_class: 'temperature'

  - platform: mqtt
    state_topic: 'sensor/humidity'
    name: 'Humidity Sensor'
    unit_of_measurement: '%' 
    value_template: '{{ value_json.humidity }}'
    force_update: 'true'
    availability_topic: 'sensor/humidity'
    payload_available: 'online'
    payload_not_available: 'offline'
    unique_id: ID
    device_class: 'humidity' 

Please comment.

Posts: 2

Participants: 2

Read full topic

@u8915055 wrote:

Hello there,

I am using Hassbian version 0.104.2 and had a question about something I saw.

If I click on the configuration panel and then ‘Devices’ which lists all my discovered devices, and then click on a specific device, I bring up a ‘Device Info’ dialog. In there, it may list multiple entities associated with my device, which in my case is an Aqara sensor discovered using zigbee2mqtt.

At the top of the entities card, there is a slider switch. For the life of me I cannot tell what that switch is for. Anyone have any idea? I searched everywhere I could think of to find that.

entities735×430 24.8 KB

Thanks very much.

Posts: 4

Participants: 2

Read full topic

@aphesiia wrote:

Hi guys,
I am a newbie in Hassio.
I have a little problem with my TTS.
In my configuration.yaml I put
tts:

• platform: google_translate
  cache: true
  cache_dir: /tmp/tts
  time_memory: 300
  base_url: http://192.168.31.12:8123
  service_name: google_say
  language: ‘fr’

When I put a message directly in my google home mini via the first page to send a message, my google mini speak the message, but in english! not in french.

In 2nd time when I use the service in developement, I have this message :
Échec d’appel du service “tts/google_say”. expected dict for dictionary value @ data[‘service_data’]. Got [{‘service’: ‘tts.google_say’, ‘entity_id’: ‘media_player.gabin’, ‘data’: {‘message’: ‘Attention, les volets vont se fermer’, ‘language’: ‘fr’}}]

I don’t use SSL/TLS service and don t use duckdns. I use cloud home assistant in hassio.
I put a dmz on my routeur to Hassio to test my config

Sorry for my bad english
Could you help me?

Posts: 1

Participants: 1

Read full topic

@PPee wrote:

Hi All,
Please help me get started with the following.
I’m trying to get some information of my central heating system, like boiler temperature, boiler on or not, target temperature, etc, etc, visible in Home Assistant. The information needed is embedded in a JSON response from a HTTP request to a local server.
So my thought is to create entities (sensors and booleans) within Home Assistant and read the returned JSON data into these entities. Searching the Home Assistant information suggests using the Template Platform. Is this right, and how to do that (examples). Cannot figure it out based on the documentation.
Thx for your response
PPee

Posts: 6

Participants: 2

Read full topic

@Mariusthvdb wrote:

as of late, (think it started on 104.x) there’s a very frequent Connection Lost notification sliding up the window.
While my config in rest is near perfect …:

491126×538 73.6 KB

this happens in the blink of an eye:

431118×1728 271 KB

need to refresh the browser window after that.

A complete mystery as to the why of this, it happens most of the time after a relative longer period on 1 tab, or after a wakeup of the screen. Changing tabs do also invoke this every now and then…The actual tab I am on doesn’t seem to matter, it even happens on the state page:

441080×1020 248 KB

clicking the state:1 at the far right reveals this:

551098×96 8.65 KB

anyone else seeing this? Seems like Chrome is mostly affected by this, Safari doesn’t show an error at all (both desktop Mac) while my iOS Companion app behaves nicely too.

Posts: 1

Participants: 1

Read full topic

@Vincent1468 wrote:

Hello everyone,

I’m having a strange issue with three Zigbee devices. Two IKEA TRADFRI remotes (E1524/E1810) and a Xiaomi Aqara single key wall switch (QBKG11LM).
Whenever I press the middle button (toggle) on one of the IKEA remotes the Xiaomi Aqara always toggles, I’ve added the Xiaomi Aqara switch yesterday.
I’m running Home Assistant 0.102.3 and zigbee2mqtt 1.9.0 with a CC2531 USB stick.

I’ve tried the following things:

• repairing the Xiaomi switch
• repairing the IKEA remotes
• running the unbind command

When I stop the Home Assistant and Zigbee2mqtt docker containers the same thing happens, so I’m thinking it’s not a zigbee2mqtt or HA issue.
My thought is that somehow the Xiaomi switch is picking up the toggle commands from the IKEA remote.

Here is the zigbee2mqtt log when the toggle button gets pressed:

zigbee2mqtt:debug 2020-01-22 19:39:55: Received Zigbee message from 'IKEA remote 1', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2020-01-22 19:39:55: MQTT publish: topic 'zigbee2mqtt/IKEA remote 1', payload '{"linkquality":39,"action":"toggle"}'
zigbee2mqtt:info  2020-01-22 19:39:55: MQTT publish: topic 'zigbee2mqtt/IKEA remote 1', payload '{"linkquality":39,"action":""}'
zigbee2mqtt:debug 2020-01-22 19:39:56: Received MQTT message on 'zigbee2mqtt/Light 1/set' with data '{"state": "ON"}'
zigbee2mqtt:debug 2020-01-22 19:39:56: Publishing 'set' 'state' to 'Light 1'
zigbee2mqtt:debug 2020-01-22 19:39:56: Received Zigbee message from 'Xiaomi Aqara Wall Switch', type 'attributeReport', cluster 'genOnOff', data '{"61440":134013020,"onOff":1}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2020-01-22 19:39:56: MQTT publish: topic 'zigbee2mqtt/Xiaomi Aqara Wall Switch', payload '{"power":0,"consumption":2.35,"temperature":24,"linkquality":107,"state":"ON"}'
zigbee2mqtt:info  2020-01-22 19:39:56: MQTT publish: topic 'zigbee2mqtt/Light 1', payload '{"state":"ON"}'

Does anyone have any idea why this is happening?

Thanks!

Edit: If anyone has the same problem, see: https://github.com/Koenkk/zigbee2mqtt/issues/2772

Posts: 1

Participants: 1

Read full topic

@mouthpiec wrote:

Is it possible to delete unused devices?
When I go to Devices and press Delete on the device, it is still present (although without details)

Posts: 1

Participants: 1

Read full topic

@joachi wrote:

first time i set up Hass.io on a raspberry pie 4, and everything went great… i thought. then i saw the logs…
and they are filled with

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.load_1m", "old_state": {"entity_id": "sensor.load_1m", "state": "0.1", "attributes": {"unit_of_measurement": " ", "friendly_nam ... (440 characters truncated) ... :00", "last_updated": "2020-01-22T19:40:57.017800+00:00", "context": {"id": "e899a311d1f4485c8ab190cef66d2310", "parent_id": null, "user_id": null}}}', 'LOCAL', '2020-01-22 19:40:57.017915', '2020-01-22 19:40:57.052834', 'e899a311d1f4485c8ab190cef66d2310', None)] (Background on this error at: http://sqlalche.me/e/4xp6)

8:40 PM components/recorder/util.py (ERROR)

Error saving event: <Event state_changed[L]: entity_id=sensor.memory_use, old_state=<state sensor.memory_use=325.9; unit_of_measurement=MiB, friendly_name=Memory use, icon=mdi:memory @ 2020-01-22T20:40:26.021472+01:00>, new_state=<state sensor.memory_use=325.1; unit_of_measurement=MiB, friendly_name=Memory use, icon=mdi:memory @ 2020-01-22T20:40:57.009903+01:00>>

8:40 PM components/recorder/__init__.py (ERROR)

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.memory_use", "old_state": {"entity_id": "sensor.memory_use", "state": "325.9", "attributes": {"unit_of_measurement": "MiB", "fr ... (458 characters truncated) ... :00", "last_updated": "2020-01-22T19:40:57.009903+00:00", "context": {"id": "0f9d71c57ecc446fa1622838419337f6", "parent_id": null, "user_id": null}}}', 'LOCAL', '2020-01-22 19:40:57.010002', '2020-01-22 19:40:57.023599', '0f9d71c57ecc446fa1622838419337f6', None)] (Background on this error at: http://sqlalche.me/e/4xp6)

8:40 PM components/recorder/util.py (ERROR)

Error saving event: <Event state_changed[L]: entity_id=light.skafferi_2, old_state=<state light.skafferi_2=on; min_mireds=153, max_mireds=500, brightness=254, color_temp=366, friendly_name=skafferi, supported_features=43 @ 2020-01-22T20:37:31.080938+01:00>, new_state=<state light.skafferi_2=on; min_mireds=153, max_mireds=500, brightness=127, color_temp=366, friendly_name=skafferi, supported_features=43 @ 2020-01-22T20:37:31.080938+01:00>>

8:40 PM components/recorder/__init__.py (ERROR)

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": "light.skafferi_2", "old_state": {"entity_id": "light.skafferi_2", "state": "on", "attributes": {"min_mireds": 153, "max_mireds": 500, ... (545 characters truncated) ... :00", "last_updated": "2020-01-22T19:40:37.083629+00:00", "context": {"id": "48b1b315113341ffa923f89f67e2464c", "parent_id": null, "user_id": null}}}', 'LOCAL', '2020-01-22 19:40:37.083709', '2020-01-22 19:40:37.107232', '48b1b315113341ffa923f89f67e2464c', None)] (Background on this error at: http://sqlalche.me/e/4xp6)

i have sensors setup in configurator.yaml
and it looks like this

  - platform: systemmonitor
    resources:
      - type: disk_use_percent
        arg: /home
      - type: memory_free
      - type: memory_use
      - type: last_boot
      - type: processor_use
      - type: load_1m
      - type: swap_use
  - platform: command_line
    name: GPU Temperature
    command: "/opt/vc/bin/vcgencmd measure_temp"
    unit_of_measurement: "°C"
    value_template: '{{ value | replace("temp=", "") | replace("''C", "") }}'

    
  - platform: command_line
    name: CPU Temperature
    command: "cat /sys/class/thermal/thermal_zone0/temp"
    unit_of_measurement: "°C"
    value_template: '{{ value | multiply(0.001) | round(1) }}' 

don’t know what is wrong, and what is what really… i tried to take away all sensors, but that gave me problem reaching home assistant with cloud service…

Posts: 4

Participants: 2

Read full topic

@antaljani wrote:

I just setup a completely new RPI3+ HassOS instance. Only SSH & Web terminal add-on was installed.
After boot up, I can connect perfectly via LAN cable.
After setup WIFI connection and static IP address and reboot, I can connect via LAN calbe and also via WIFI.
I used this guide: Guide: Connecting Pi with HassOS to wifi

If I disconnect LAN cable, it is stop communication on WIFI as well. Not possible to connect via WIFI. Even if I set up DNS and GATEWAY (my router is using 192.168.1.1).

USB stick and my-network file setup method is not working at all for me. Does nothing.

Any idea or suggestion?

Posts: 2

Participants: 2

Read full topic

@a94marbo wrote:

I have a PI3B+ with 16GB U1 sd-card, and after some releases ago check configuration and restart of Hassio became very very slow. Check config can take up to 5-10 minutes and restart can take up to 20 minutes.
I have many integrations and a big system.
15 units on deconz, 20 units in Tradfri (ikea), 10 units in Zwave and Smartthings, Ring integrations and 3 custom components.

I have read many suggestions on forums and tested them all.

• Removed the db file
• Re-flashed the sd card
• Ported to a new and faster sd card (v30)
• Ported to a Pi4 and faster cd card
• check if I have google calendar
• checked for bad config file

Nothing made the system faster, any ideas? I am all out of new things to try.

Posts: 1

Participants: 1

Read full topic

@MDLefevere wrote:

Hi all,

I’m folliwing a guide to get rid of the latency in my Hue Motion sensor when using it with MQTT

I was following a tutorial of Skylar Tech but I’m stuck at some point.

  - platform: mqtt
    state_topic: 'sensors/frontdooroutside/motion'
    name: 'Front Door Motion'
    qos: 0
    payload_on: "1"
    payload_off: "0"
    value_template: '{{ value }}'
    device_class: 'motion'

at the state_topic part… What information do I need to put there?. Were can I find this information?

Link Topic

Posts: 2

Participants: 2

Read full topic

@123 wrote:

Perhaps I’ve missed some important concept because I thought it would be a cakewalk to setup the Emulated Hue integration. Nevertheless, despite all my efforts, attempts to discover new devices via the Alexa app result in finding none.

In configuration.yaml:

emulated_hue:
  host_ip: <MyServerIP>
  listen_port: 80
  expose_by_default: false
  entities:
    light.kitchen:
      name: "Kitchen Light"
      hidden: false
    light.family:
      name: "Family Light"
      hidden: false

Home Assistant 0.103.2 is running in a venv so I’ve executed setcap as per the documentation

sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.7

and I confirmed the service is alive by browsing to this URL:

http://<MyServerIP>:80/api/pi/lights

It returns JSON data containing the lights I specified in configuration.yaml.

It seems to me all the needed pieces are in place. Using the Alexa app on my phone, I instruct it to discover devices (Add Device > Other > Discover Devices) and, after a 45-second wait, it returns and reports it found none.

I have a few Ecobee Switch+ devices with built-in Amazon Alexa. They have most of the capabilities of an Amazon Echo Dot. If I tell one to “Discover Devices”, it promptly replies it found none.

So where’s my mistake? Can the Alexa app be used to discover devices generated by Emulated Hue? Do I need a genuine Amazon Echo to discover devices?

Posts: 5

Participants: 3

Read full topic

@mtnaut3 wrote:

I read somewhere (which I cannot find again), that the new HS fan controller, which has 4 speed selections, can be fine adjusted for each of the 4 speed settings. That would be nice, but I cannot find this info on any HS spec nor in any general web search.
Does anyone know this?

Posts: 2

Participants: 2

Read full topic

@Dino wrote:

Good night,

I’m trying to set up the glow control of these dimmer with ESPHOME, but I’m not successful, the same way was in TASMOTA.
I tried several settings of minimum and maximum glow settings, but none of them worked satisfactory. Has anyone ever succeeded with this module? He’s based on Tuya, with a secondary chip Mcu that connects Tx and Rx.

image3024×4032 2.4 MB

image3024×4032 2.25 MB

image3024×4032 2.53 MB

Posts: 1

Participants: 1

Read full topic

@sd_dracula wrote:

Currently I have hassio installed on a pi4 with an image on the SD card but I am looking to go via the SSD version (still on the pi4) where I just use the SD card to boot from it and then install hassio on top of raspbian.
Just wondering if I am losing any features/functionality if I snapshot my existing setup and restore it to the SSD/raspbian setup.

Posts: 4

Participants: 3

Read full topic

@pejotigrek wrote:

in case of my topic wasn’t too clear, here’s the explaination of my question:
I’ve got a sensor that reads from the water meter. let’s call it sensor.water_read. it is numeric and looks like this: 123456, with the liter as display unit.
when the invoice guy comes to ask for readouts, he needs cubic meters, so in case of sensor.water_read it’s just 123.
I want to display the sensor.water_read in a nice form, but also keep the original numbers for other calculations [like daily/monthly stats, sprinkler useage etc.]. so until now I used sensor.water_read for calculations and I had an additional template sensor, let’s call it sensor.water_display, with below config - just for making it nice in lovelace.

- platform: template
    sensors:
      water_display:
        value_template: "{{ '{0:,}'.format(states('sensor.water_read')|int/1000)|replace(',',' ')|replace('.',',') }}"
        unit: "m³"

and it gave me a nice 123,456 m³ as output in the dashboard.

but that solution isn’t perfect - because it duplicates the sensor just for sake of displaying it another way - so I wonder, if there’s a way to set some options to display the sensor in way I want [with comma and different unit etc.] but within the very same entity? without duplicating it with template sensor? like reformatting it on-the-fly?

Posts: 2

Participants: 2

Read full topic

@BrianHanifin wrote:

I have noticed there is some concern about how to get along without the formerly automatically generated groups like group.all_lights. I promise you there is a way to make your code work without them. Ask here and we can help you.

First off, the following is the correct way to turn off every light now.

service: light.turn_off
entity_id: all  # replace group.all_lights with `all`

Here are some example templates to get lists of entity_ids to get you thinking.

List of all lights

{{ states.light | map(attribute='entity_id') | join(',') }}

List of lights that are turned on

{{ states.light | selectattr('state','eq','on') | map(attribute='entity_id') | join(',') }}

With some slights changes you can make these work for covers.

List of all covers

{{ states.cover | map(attribute='entity_id') | join(',') }}

List of covers that are open

{{ states.light | selectattr('state','eq','open') | map(attribute='entity_id') | join(',') }}

If you really feel like you need the all groups back you have some options. For example you can create a script that rebuilds a group. The script below literally recreates group.all_lights. Call this script just before you need the group to update it.

script:
  # Recreate group.all_lights
  update_all_light_group:
    sequence:
      - service: group.set
        data_template:
          object_id: "all_lights"
          entities: >
            {{ states.light |  map(attribute='entity_id') | join(',') }}

  # Recreate group.all_switches
  update_all_switches_group:
    sequence:
      - service: group.set
        data_template:
          object_id: "all_switches"
          entities: >
            {{ states.switch |  map(attribute='entity_id') | join(',') }}

While these group won’t updated every time the status of a state changes… well, your server doesn’t have to update the group every time a change happens. Every little bit helps on a Raspberry Pi… ammiright?

There also two AppDaemon apps available on HACS that intend to recreate those groups for you.

1. https://github.com/Petro31/ad_group_all
2. https://github.com/so3n/Bring-Back-group.all_x

If you would like help converting a script post an example of your code in this topic.

Posts: 2

Participants: 1

Read full topic

@mboarman wrote:

Coming over from Hubitat and trying to wrap my head around this universe. I’m running Hass.io and trying to transfer over some of my Hubitat automations one at a time…For the most part I’m using a combination of google searches and the Automation GUI to port these over. I have a question that I bet is pretty simple for 90% of the users here. I currently have two automations built: One to turn on a switched light when a door is open and another to turn off the same switched light when the door closes. I’ve got to imagine these can be combined but I can’t figure out how to do it in the GUI and when I start to mess with a text editor I get syntax errors…I’m curious to know how the ‘experts’ here would combine these two automations?

- id: '1579741181375'
  alias: Laundry Room Light - turn on
  description: ''
  trigger:
  - entity_id: binary_sensor.visonic_mct_340_e_3440120b_ias_zone
    from: 'off'
    platform: state
    to: 'on'
  condition: []
  action:
  - device_id: af884a417a494ea0820f6fd43594c5dc
    domain: switch
    entity_id: switch.honeywell_unknown_type_4952_id_3036_switch
    type: turn_on

- id: '1579741745648'
  alias: Laundry Room Light - turn off
  description: ''
  trigger:
  - entity_id: binary_sensor.visonic_mct_340_e_3440120b_ias_zone
    from: 'on'
    platform: state
    to: 'off'
  condition: []
  action:
  - device_id: af884a417a494ea0820f6fd43594c5dc
    domain: switch
    entity_id: switch.honeywell_unknown_type_4952_id_3036_switch
    type: turn_off

Posts: 3

Participants: 3

Read full topic