Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 107032 articles
Browse latest View live

Different Voice Commands per User

$
0
0

@caebrida wrote:

Dear folks,

Not sure if this is the correct category. If not I’m sorry about that.

I’ve been searching for a solution but found nothing yet. I’m wondering if it’s possible to set different device names (or commands) per user. I.e.: If I’m asking Siri: “Siri, turn off bedroom’s lights” only the lights in my room will be off. If my son ask the same for Siri, his bedroom’s light will be off instead.
In other words, I’m looking for a solution to set different commands depending on the user.

Thanks.
Carlos

Posts: 1

Participants: 1

Read full topic


Moderately frustrated- cannot start Zwave

$
0
0

@suburbazine wrote:

Been struggling with a move from Wink to HASS, trying to get Zwave started and the errors aren’t being self explanatory. I’ve tried both /dev/ttyACM0 and the direct path, both seem to open then choke as below. I’m using a Zooz S2 Plus USB adapter running a HASS ESXi image, up to date. What am I missing here?


    serial:
        /dev/ttyACM0
        /dev/ttyS0
        /dev/ttyS3
        /dev/ttyS1
        /dev/ttyS2
        /dev/serial/by-id/usb-0658_0200-if00
    input:
        Power Button
        ImPS/2 Generic Wheel Mouse
        VMware VMware Virtual USB Mouse
        AT Translated Set 2 keyboard
    disk:
    gpio:
    audio:


2020-06-02 16:33:31.948 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-02 16:33:38.888 Info, Setting Up Provided Network Key for Secure Communications
2020-06-02 16:33:38.888 Info, mgr,     Added driver for controller /dev/serial/by-id/usb-0658_0200-if00
2020-06-02 16:33:38.888 Info,   Opening controller /dev/serial/by-id/usb-0658_0200-if00
2020-06-02 16:33:38.888 Info, Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1)
2020-06-02 16:33:39.081 Info, Serial port /dev/serial/by-id/usb-0658_0200-if00 opened (attempt 1)
2020-06-02 16:33:39.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 16:33:39.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 16:33:39.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 16:33:39.082 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 16:33:39.082 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 16:33:39.082 Detail,
2020-06-02 16:33:39.082 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 16:33:39.086 Warning, WARNING: Out of frame flow! (0x61).  Sending NAK.
2020-06-02 16:33:39.094 Warning, WARNING: Out of frame flow! (0x20).  Sending NAK.
2020-06-02 16:33:39.100 Warning, WARNING: Out of frame flow! (0x30).  Sending NAK.
2020-06-02 16:33:49.083 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 16:33:49.083 Detail, contrlr, Removing current message
2020-06-02 16:33:49.083 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 16:33:49.083 Detail,
2020-06-02 16:33:49.083 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 16:33:49.174 Detail, Unsolicited message received while waiting for ACK.
2020-06-02 16:33:49.681 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-06-02 16:33:49.770 Detail, Unsolicited message received while waiting for ACK.
2020-06-02 16:33:50.271 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-06-02 16:33:50.271 Warning, WARNING: Out of frame flow! (0x20).  Sending NAK.
2020-06-02 16:33:50.273 Detail, Unsolicited message received while waiting for ACK.
2020-06-02 16:33:50.773 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-06-02 16:33:50.773 Detail, Unsolicited message received while waiting for ACK.
2020-06-02 16:33:51.273 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-06-02 16:33:51.273 Warning, WARNING: Out of frame flow! (0x20).  Sending NAK.
2020-06-02 16:33:51.401 Detail, Unsolicited message received while waiting for ACK.
2020-06-02 16:33:51.401 Detail, contrlr,   Received: 0x01, 0x01, 0x02
2020-06-02 16:33:51.401 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2020-06-02 16:33:51.401 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:33:51.408 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:33:51.411 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:33:51.418 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:33:51.421 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:33:52.421 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 16:33:52.421 Detail, contrlr, Removing current message
2020-06-02 16:33:52.421 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 16:33:52.422 Detail,
2020-06-02 16:33:52.422 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 16:33:53.422 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 16:33:53.423 Detail, contrlr, Removing current message
2020-06-02 16:33:53.423 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 16:33:53.423 Detail,
2020-06-02 16:33:53.423 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 16:33:53.427 Warning, WARNING: Out of frame flow! (0x07).  Sending NAK.
2020-06-02 16:33:53.427 Warning, WARNING: Out of frame flow! (0x03).  Sending NAK.
2020-06-02 16:33:53.429 Detail, Unsolicited message received while waiting for ACK.
2020-06-02 16:33:53.442 Detail, contrlr,   Received: 0x01, 0x02, 0x87, 0x88
2020-06-02 16:33:53.442 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2020-06-02 16:33:53.445 Warning, WARNING: Out of frame flow! (0x2b).  Sending NAK.
2020-06-02 16:33:53.445 Warning, WARNING: Out of frame flow! (0x07).  Sending NAK.
2020-06-02 16:33:53.445 Warning, WARNING: Out of frame flow! (0x02).  Sending NAK.
2020-06-02 16:33:53.445 Warning, WARNING: Out of frame flow! (0x7a).  Sending NAK.
2020-06-02 16:33:53.445 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-06-02 16:33:53.447 Warning, WARNING: Out of frame flow! (0x02).  Sending NAK.
2020-06-02 16:33:53.451 Warning, WARNING: Out of frame flow! (0x87).  Sending NAK.
2020-06-02 16:33:53.457 Warning, WARNING: Out of frame flow! (0x88).  Sending NAK.
2020-06-02 16:33:54.457 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 16:33:54.457 Detail, contrlr, Removing current message
2020-06-02 16:33:54.457 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 16:33:54.457 Detail,
2020-06-02 16:33:54.457 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 16:33:54.464 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-06-02 16:33:54.467 Warning, WARNING: Out of frame flow! (0x56).  Sending NAK.
2020-06-02 16:33:54.468 Warning, WARNING: Out of frame flow! (0x56).  Sending NAK.
2020-06-02 16:33:54.468 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:33:54.469 Warning, WARNING: Out of frame flow! (0xac).  Sending NAK.
2020-06-02 16:33:54.472 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2020-06-02 16:33:54.477 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2020-06-02 16:34:02.032 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-06-02 16:34:02.032 Warning, WARNING: Out of frame flow! (0x0f).  Sending NAK.
2020-06-02 16:34:02.041 Detail, contrlr,   Received: 0x01, 0x06, 0x64, 0x0f, 0x96, 0x01, 0x01, 0x06
2020-06-02 16:34:02.041 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2020-06-02 16:34:02.047 Warning, WARNING: Out of frame flow! (0x0f).  Sending NAK.
2020-06-02 16:34:02.051 Warning, WARNING: Out of frame flow! (0x96).  Sending NAK.
2020-06-02 16:34:02.057 Warning, WARNING: Out of frame flow! (0x05).  Sending NAK.
2020-06-02 16:34:02.560 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2020-06-02 16:34:02.560 Warning, WARNING: Out of frame flow! (0x64).  Sending NAK.
2020-06-02 16:34:04.458 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 16:34:04.458 Detail, contrlr, Removing current message
2020-06-02 16:34:04.458 Detail, contrlr, Notification: Notification - TimeOut

Posts: 1

Participants: 1

Read full topic

Automation with sensor threshold (sun azimuth) doesn't work

$
0
0

@Nick4 wrote:

Hi all

I’m trying to use the sun azimuth to close/open curtains.
In configuration.yaml I have created these sensors:

binary_sensor:
  - platform: template
    sensors:
      sun_azimuth:
        friendly_name: "Sun Azimuth"
        unit_of_measurement: 'degrees'
        value_template: "{{ state_attr('sun.sun', 'azimuth') }}"

binary_sensor:
  - platform: threshold
    upper: 311
    lower: 308
    entity_id: sensor.sun_azimuth
    name: "sun azimuth front"

This is the automation (for now it’s just a test with a mediaplayer):

- id: '1590702116486'
  alias: test sun front
  description: ''
  trigger:
  - entity_id: binary_sensor.sun_azimuth_front
    from: 'off'
    platform: state
    to: 'on'
  action:
  - data: {}
    entity_id: media_player.1
    service: media_player.media_pause

I have tested the sun_azimuth template which returns the right value.
The ‘binary_sensor.sun_azimuth_front’ state remains off after the sun has passed the lower value.
Am I doing something wrong or what am I missing?

Thanks A LOT in advance!
Nick

Posts: 1

Participants: 1

Read full topic

Should my base_url be my Nabu Casa remote URL or my local IP?

$
0
0

@tmchow wrote:

Suppose I primarily access my HA instance with the Nabu Casa remote UI url (e.g. https://abcdef1234.ui.nabu.casa/ ). Should my configuration.yaml have the base_url set to my local IP (e.g. http://192.168.1.100 ) or my Nabu Casa URL?

Posts: 1

Participants: 1

Read full topic

Ikea Fyrtur with Deconz and ikea remote

$
0
0

@Heijt771 wrote:

Hey!

I recently bought a few Ikea Smart Blinds “Fyrtur” that I have connected through Deconz to control.

Now I would also like to add the support of the original ikea open/close remote while maintaining the ability to control with home assistant.

Can anyone help me set this up? I have tried adding both at the same time but without avail.

I have the open/closed switch linked through Deconz, but I am unable to find it back anywhere in HA.

Any help to get this going either, through direct control with the remote or through sending actions with the on/off remote to HA, would be hugely appreciated.

Kind Regards

Posts: 1

Participants: 1

Read full topic

Date convert format from sensor file

$
0
0

@menarcarlos wrote:

Hello, this is the first time I publish desperate, i’m could not get it to work, the correct date format from a sensor.file that extracts the date from a json string, this is my configuration.yaml:

sensor 4:
  - platform: file
    name: batch_file_inicio
    file_path: Batch.json
    value_template: "{{ value_json.Depuracion_Rollbacks.Date_debut.Fecha | timestamp_custom('%d/%m/%Y') }}"
sensor 5:
  - platform: file
    name: batch_file_fin
    file_path: Batch.json
    value_template: >
        {% set date = states('sensor.batch_file_inicio') %}
        {{ as_timestamp(strptime(date, '%d/%m/%Y')) | timestamp_custom('%d/%m/%Y') }}
        {% if date == states('sensor.date') %} Batch 1
        {% else %} Batch 2
        {% endif %}

I have used other methods, but still have not succeeded. What is the most practical way to solve it?

The result of the above code gives me always: Batch 2

Posts: 2

Participants: 2

Read full topic

Schlage and Calendar Booking

$
0
0

@chrisaxe21 wrote:

hi all

I like the look of the schlage locks, especially as you can use a physical key with them in the event of a system failure.

Are there and solutions or projects where you can go to a booking calendar, select a date/time and get a code emailed through? HA would of course program the schlage lock with that code

Thanks

Posts: 1

Participants: 1

Read full topic

Xiaomi Roborock S5 - Starts automatically after each homeassistant restart

$
0
0

@kwetiaw wrote:

HI there
just wondering if anyone else is experiencing the same ‘issue’ as me.
My xiaomi roborock s5 starts automatically after each homeassistant restart
Anyway to disable this?

Thanks!

Posts: 1

Participants: 1

Read full topic


Home Assistant and RaZberry2/Aeotec stick on different devices?

$
0
0

@sofakng wrote:

Is it possible to run Home Assistant on one machine and RaZberry2 (or Aeotec stick) on a different machine?

For example, I have a Linux server (dual-cpu, etc) in my basement that runs Home Assistant (via Docker) and many other services. I was thinking about building a small Raspberry Pi + RaZberry2 (or Aeotec stick) and placing it upstairs near my door locks, light switches, etc.

Is this possible?

Can I just run OpenZWave or Z-Way on this separate Raspberry Pi and have Home Assistant communicate with it? (i.e. the Raspberry Pi would be functioning as a dedicated Z-Wave Hub essentially)

Posts: 2

Participants: 2

Read full topic

Cannot Start Z-Wave on RP4/Aeotec 5

$
0
0

@Bleak_Chimera wrote:

Hi! I have gone through everything I can find on this topic, and I have tried everything including running the Aeotec stick through a USB 2.0 hub. HA locates the stick no problem when setting up the integration, but the network won’t start - it just hangs when I attempt.

Unfortunately, I’m a 100% noob at this, but I did get the following from the log:

2020-06-02 20:39:06.436 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-02 20:39:11.949 Info, Setting Up Provided Network Key for Secure Communications
2020-06-02 20:39:11.950 Info, mgr,     Added driver for controller /dev/ttyAMA0
2020-06-02 20:39:11.950 Info,   Opening controller /dev/ttyAMA0
2020-06-02 20:39:11.951 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-06-02 20:39:11.951 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-06-02 20:39:11.952 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 20:39:11.952 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 20:39:11.952 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 20:39:11.952 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 20:39:11.952 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 20:39:11.952 Detail,
2020-06-02 20:39:11.952 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 20:39:11.953 Detail, contrlr, Notification: DriverFailed

I did find this thread, and I have tried using both types of address for the z-wave stick. The Integration is created in both cases, and in both cases the z-wave network won’t start - just hangs.

Posts: 3

Participants: 2

Read full topic

Update state of montion sensor in Imou camera

$
0
0

@Kevintitan wrote:

Hi everyone,
I have Imou camera which is added to Hass via ONVIF. All functions works well, including motion detection. I make an automation to turn on light. The thing is time interval of state update is too long, I try homeassistant.update_entity in SERVICE but nothing. Please give me advice if anyone spent experience like this. Thank you

Posts: 1

Participants: 1

Read full topic

Zwave2mqtt- cannot connect to local mqtt broker

$
0
0

@suburbazine wrote:

Can’t figure out why zwave2mqtt isn’t able to connect to the local mqtt broker. I’ve tried using HASS admin credentials, setting up local users, anonymous (after setting the ACLs in MQTT Broker) but it still gets connection refused messages. I don’t even see the connection attempt in the MQTT Broker log, only the zwave log. Am I missing a setting somewhere? I referred to the simple Z2M setup on here to get this far.

2020-06-03T01:23:31.108Z z2m:Mqtt MQTT client closed
2020-06-03T01:24:31.118Z z2m:Mqtt MQTT client reconnecting
2020-06-03T01:24:31.120Z z2m:Mqtt connect ECONNREFUSED 127.0.0.1:1883
2020-06-03T01:24:31.120Z z2m:Mqtt MQTT client closed
[20:16:49] INFO: Setup mosquitto configuration
[20:16:49] WARNING: SSL not enabled - No valid certs found!
[20:16:49] INFO: No local user available
[20:16:50] INFO: Initialize Hass.io Add-on services
[20:16:50] INFO: Initialize Home Assistant discovery
[20:16:50] INFO: Start Mosquitto daemon
1591147010: Loading config file /share/mosquitto/acl.conf
1591147010: mosquitto version 1.6.3 starting
1591147010: Config loaded from /etc/mosquitto.conf.
1591147010: Loading plugin: /usr/share/mosquitto/auth-plug.so
1591147010: |-- *** auth-plug: startup
1591147010:  ├── Username/password checking enabled.
1591147010:  ├── TLS-PSK checking enabled.
1591147010:  └── Extended authentication not enabled.
1591147010: Opening ipv4 listen socket on port 1883.
1591147010: Opening ipv6 listen socket on port 1883.
1591147010: Opening websockets listen socket on port 1884.
1591147010: Warning: Mosquitto should not be run as root/administrator.
1591147011: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1591147011: New client connected from 172.30.32.1 as auto-8892E102-B365-8E5C-7EAE-617048A4D037 (p2, c1, k60, u'homeassistant').

Posts: 1

Participants: 1

Read full topic

iOS companion app - Wyze cam livestream?

$
0
0

@basesnow wrote:

I have a wyzecam (RTSP) in the garage that I want to integrate into my garage notification using the iOS companion app. With the current setup I have, it just gets stuck with “loading camera” with a spinning wheel. Anyone got this working with a Wyze cam? Any suggestions on what I might be messing up? The camera is working fine in Lovelace, and all other aspects of the notification are working. Here is how I have it set up:

Config:

stream:

camera:
  - platform: generic
    still_image_url: !secret garage_rtsp
    stream_source: !secret garage_rtsp
    name: garage

ios:
  push:
    categories:
      - name: GARAGE
        identifier: 'camera'
        actions:
          - identifier: 'close'
            title: 'Close the Garage Door'
            authenticationRequired: 'false'
            destructive: 'true'
          - identifier: 'stop_1_hour_garage'
            title: 'Pause Garage Notifications for 1 Hour'
            authenticationRequired: 'false'
            destructive: 'false'
          - identifier: 'stop_til_tomorrow_garage'
            title: 'Pause Garage Notifications Until Tomorrow'
            authenticationRequired: 'false'
            destructive: 'false'

Here is the automation action to send the notification (I get the actionable items that are called out in the iOS push category actions, but no camera feed):

data:
  data:
    attachment:
      content-type: jpeg
    entity_id: camera.garage
    push:
      category: camera
      thread-id: garage
  message: Garage door was just opened.
  title: Garage Door
service: notify.colins_apple_stuff

Posts: 1

Participants: 1

Read full topic

Automation does not trigger input_boolean

$
0
0

@barnosell wrote:

Hello,
I’m trying to define a template for automation to enable / disable between two dates and times. It is an automation to activate a conditional mode.
For this I have defined the time_date sensor:
sensor:

  • platform: time_date
    display_options:
    • ‘time’
    • ‘date’
    • ‘date_time’
    • ‘date_time_utc’
    • ‘date_time_iso’
    • ‘time_date’
    • ‘time_utc’
    • ‘beat’

The imput_boolean:

input_boolean:
futbol_match:
name: “Futbol Match”
initial: off

And finally the imput_datetime

input_datetime:
futbol_match_on:
name: Match On
has_date: true
has_time: true
futbol_match_off:
name: Match Off
has_date: true
has_time: true

And in automation, I’m trying to use this formula, but it doesn’t work. I can’t find the formula to automatically turn it on and off. Can you help me, please? Thank you

‘{{ states(’‘sensor.date_time’’) == (state_attr(’‘input_datetime.futbol_match_on’’,
‘‘timestamp’’) | int | timestamp_custom(’’%H:%M’’, True)) }}’

and this automation

  • id: ‘Match On’
    alias: Match On
    description: ‘’
    trigger:
    • platform: template
      value_template: ‘{{ states(’‘sensor.date_time’’) == (state_attr(’‘input_datetime.futbol_match_on’’,
      ‘‘timestamp’’) | int | timestamp_custom(’’%H:%M’’, True)) }}’
      condition: []
      action:
    • data: {}
      entity_id: input_boolean.futbol_match
      service: input_boolean.turn_on

Posts: 1

Participants: 1

Read full topic

Tuya lights not working when exposed to Google

$
0
0

@cnschulz wrote:

Gday,

Ive had the Tuya integration working for many months now (heater, kettle). I have exposed these devices to Google and they have bee working fine.

I added two wifi bulbs and they work in the Tuya app and via home assistant but they will not toggle when exposed to Google! I dont understand this at all. :\

Lights work successfully:

  • Through the native app
  • In home assistant with Tuya integration
  • I google home with direct app integration (but i cant continue to use that for other reasons (heater doesnt work))

The lights only fail to respond when exposed to Google via home assistant Tuya integration.

No errors in the log, just google saying “ooops i cant connect to the light”

Any iseds how I might debug this?

Cheers

Posts: 1

Participants: 1

Read full topic


ZHA vs. deCONZ

$
0
0

@Klagio wrote:

Hi, I want to try ZHA, with a COnbee one or Conbee two.

Is it possible to have both running in a production environment (wish to see ZHA compatibility and ease of use) , or one excludes the other?

Posts: 1

Participants: 1

Read full topic

Lovelace doesn't show button state

$
0
0

@DenisSh wrote:

I can’t understand what’s wrong with this code:

- entity: switch.sw_two
    image: 'http://dshgmbh.ru/uploads/light_bulb_off.png'
    state_filter:
      'off': brightness(80%) saturate(0.8)
      'on': brightness(130%) saturate(1.5) drop-shadow(0px 0px 10px gold)
    state_image:
      'on': 'http://dshgmbh.ru/uploads/light_bulb_on.png'
    style:
      left: 78%
      padding: 10px
      top: 65%
      width: 7%
    tap_action:
      action: toggle
    type: image
  - entity: sensor.kitchen_wall_button
    image: 'http://dshgmbh.ru/uploads/light_bulb_off.png'
    state_filter:
      'off': brightness(80%) saturate(0.8)
      'on': brightness(130%) saturate(1.5) drop-shadow(0px 0px 10px gold)
    state_image:
      'on': 'http://dshgmbh.ru/uploads/light_bulb_on.png'
    style:
      left: 85%
      padding: 10px
      top: 25%
      width: 7%
    type: image

The switch -sw_two - work fine, but sensor - kitchen_wall_button doesn’t change image on a floor plane. (both the data goes and come back to same device).
The history view for kitchen button show that state changed.

Posts: 1

Participants: 1

Read full topic

Continue plex to chromecast casting

$
0
0

@mpahic wrote:

Is it possible to create an automation that would run plex on chromecast and would continue the series or a movie where I left off?

Posts: 1

Participants: 1

Read full topic

Tasmota 8.3.1 on SOnOff 4CHProR2 - Switch turns off in 17 seconds everytime

$
0
0

@vishnunn wrote:

Hi,

I have been trying to get my head around this problem since few days now. I have 2 4chpror2 having tasmota and connected to home assistant via external MQTT. One works fine but in the other one, when i turn on a switch from tasmota interface or HA, it turns off automatically in about 17 seconds. No mater what settings I try, it always turns off. As it turns off even if i use tasmota UI, i posted it first in tasmota forum but it looks like there is a MQTT power off message sent from HA; so it is something that HA is doing rather than tasmota. This device was added to HA via auto-discovery so no entries in configuration.yaml.

This is what appears in the console:

12:59:50 MQT: tele/Sonoff4chpro/STATE = {“Time”:“2020-06-03T12:59:50”,“Uptime”:“0T00:37:36”,“UptimeSec”:2256,“Heap”:26,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:1,“POWER1”:“OFF”,“POWER2”:“OFF”,“POWER3”:“OFF”,“POWER4”:“ON”,“Wifi”:{“AP”:1,“SSId”:“",“BSSId”:"”,“Channel”:2,“RSSI”:70,“Signal”:-65,“LinkCount”:1,“Downtime”:“0T00:00:05”}}

12:59:50 MQT: stat/Sonoff4chpro/RESULT = {“POWER4”:“ON”}

12:59:50 MQT: stat/Sonoff4chpro/POWER4 = ON (retained)

13:00:07 MQT: stat/Sonoff4chpro/BUTTON4T = {“TRIG”:“SINGLE”}

13:00:07 MQT: tele/Sonoff4chpro/STATE = {“Time”:“2020-06-03T13:00:07”,“Uptime”:“0T00:37:53”,“UptimeSec”:2273,“Heap”:25,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:1,“POWER1”:“OFF”,“POWER2”:“OFF”,“POWER3”:“OFF”,“POWER4”:“OFF”,“Wifi”:{“AP”:1,“SSId”:“",“BSSId”:"”,“Channel”:2,“RSSI”:76,“Signal”:-62,“LinkCount”:1,“Downtime”:“0T00:00:05”}}

13:00:07 MQT: stat/Sonoff4chpro/RESULT = {“POWER4”:“OFF”}

13:00:07 MQT: stat/Sonoff4chpro/POWER4 = OFF (retained)

Exactly at 17th seconds there is this: stat/Sonoff4chpro/BUTTON4T = {“TRIG”:“SINGLE”}

Can some one help me out on this?

Thanks.

Posts: 1

Participants: 1

Read full topic

Miio Humidifier unable to discover

$
0
0

@suxarik wrote:

Hello all!
I am trying to integrate my Xiaomi Humidifier (CA1) into Home Assistant (0.110.4).
Configuration:

# Xiaomi Humidifier
fan:
  - platform: xiaomi_miio
    host: 192.168.10.187
    token: <<MY_TOKEN>>
    model: zhimi.humidifier.ca1
    name: Humidifier

My error:

2020-06-03 11:18:03 DEBUG (SyncWorker_1) [miio.protocol] Unable to decrypt, returning raw bytes: b''
2020-06-03 11:18:03 DEBUG (SyncWorker_1) [miio.miioprotocol] Got a response: Container: 
    data = Container: 
        data = b'' (total 0)
        value = b'' (total 0)
        offset1 = 32
        offset2 = 32
        length = 0
    header = Container: 
        data = b'!1\x00 \x00\x00\x00\x00\x12k\x16\x1f^\xd7\\\xbb' (total 16)
        value = Container: 
            length = 32
            unknown = 0
            device_id = b'\x12k\x16\x1f' (total 4)
            ts = 2020-06-03 08:18:03
        offset1 = 0
        offset2 = 16
        length = 16
    checksum = b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' (total 16)
2020-06-03 11:18:08 ERROR (SyncWorker_2) [miio.miioprotocol] Unable to discover a device at address 192.168.10.187
2020-06-03 11:18:08 WARNING (MainThread) [homeassistant.components.fan] Platform xiaomi_miio not ready yet. Retrying in 30 seconds.

The strange part:
I cant discover this humidifer manually using mirobo discover --handshake 1 after I pair it with Mi Home.
It can be however discovered then I factory reset it, BUT only once. After I make a first handshake device is no longer discoverable (but works perfectly with Mi Home).
My device and Home assistant are on the same network (no VLANs present).
Using the latest python-miio (0.5.0.1)

Any ideas? I’ll appreciate it. Thanks.

Posts: 1

Participants: 1

Read full topic

Viewing all 107032 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>