@EricR wrote:

I created a simple sensor to identify if the temperature is going to be warmer or cooler using darksky. It returned “warmer” but does not change to “cooler”. No errors in the logs. It’s as if it only evaluated when I restarted HASSIO and won’t evaluate again. What am I doing wrong?

  #State of weather for weather light bulb
  - platform: template
    sensors:
      weather_state_custom:
        entity_id:
          - sensor.dark_sky_daytime_high_temperature_0d
          - sensor.dark_sky_daytime_high_temperature_1d
        value_template: >-
          {% if float('sensor.dark_sky_daytime_high_temperature_0d') < 
          float('sensor.dark_sky_daytime_high_temperature_1d') %}warmer
          {% else %}cooler
          {% endif %}

Posts: 1

Participants: 1

Read full topic

@willh wrote:

The dimmer slider for MQTT lights behaves differently than my z-wave light dimmers. When the slider is moved all the way to the left, the zwave dimmers will remain on (the toggle in the upper left of the lovelace card stays on) and the dimmer gets the lowest value possible. This is preferable as I’d like to dim the lights as low as possible.

With the MQTT lights, however, moving the slider all the way to the left turns the dimmer value to 0 and turns the toggle off.

I noticed this issue where there a turn_off was removed from slider. Not sure why MQTT is different

Posts: 1

Participants: 1

Read full topic

@SimonPth wrote:

Hi all

I started off with a Wyze Sense pack, intending to have a bit of a play with just that and the corresponding app. In walks Home Assistant and I have fallen very deep down a rabbit hole that I didn’t even know existed.

Basically I have Home Assistant running very nicely on a RPi 3B+, with my Wyze Sense sensors doing their thing.

I recently installed the ESPHome add-on, flashed up a ESP8266 that’s connected to a relay module, which, in turn, drives the OSC (OpenStopClose) contact on my garage door.

This works flawlessly. I can open my garage door using a toggle, which, after 2.seconds, resets back to off, to reset the relay for the next time I want to open/close the door.

I then installed the very handy Google Assistant Webserver add-on, hacked a Wyze Sense door contact together with a normally closed pushbutton, and voila, I have my Google Homes announcing when someone presses my homebrew doorbell.

Using this, I can now open my garage door via voice commands too.

Which leads me to my eventual (very slight) issue.

Since I’m using the ESP8266 to drive a relay, which has a 2 second delay and sets itself back to zero, I have to issue Google with the command “Turn on the garage door” or better, "Activate the garage door.

I’ve since discovered the covers template and implemented that, which gives me a decent graphic, up/down arrows and a stop button.

I can now issue an “Open the garage door” and google will happily reply with “Alright, opening the garage door”
But the graphic never changes, and the up arrow on the Lovelace page is always greyed out. Also, the garage door symbol never changes to open.
When I tell Google to “Close the garage door”, she dutifully replies with "Alright “OPENING the garage door”. And the garage door closes.

There is 1 Wyze contact on the garage door that closes when the garage door is closed, and is open at any other position.

Obviously something is wrong in my code somewhere and I need a bit of help. This has been a LOT of new information to digest in the week that I’ve had it.

The code for the cover in my configuration.yaml is as follows:

cover:
  - platform: template
    covers:
      garage_door:
        friendly_name: "Garage Door"
        position_template: "{{ states('binary_sensor.wyzesense_77825a44') }}"
        open_cover:
          service: switch.toggle
          data:
            entity_id: switch.garage_door_opener
        close_cover:
          service: switch.toggle
          data:
            entity_id: switch.garage_door_opener
        stop_cover:
          service: switch.toggle
          data:
            entity_id: switch.garage_door_opener
        icon_template: >-
          {% if states('binary_sensor.wyzesense_77825a44')|float > 0 %}
            mdi:garage-open
          {% else %}
            mdi:garage
          {% endif %}

Code on the ESP8266 is as follows:

switch:
- platform: gpio
  id: relay
  pin:
    number: GPIO0
    inverted: False
  restore_mode: ALWAYS_OFF
- platform: template
  name: "Garage Door Opener"
  icon: "mdi:garage"
  turn_on_action:
  - switch.turn_on: relay
  - delay: 2s
  - switch.turn_off: relay

Garage door cover is as follows on Overview.
This is while the door is currently closed, but the arrow states or garage door symbold do not change.

Would appreciate any help, thanks all!

Posts: 1

Participants: 1

Read full topic

@pnbruckner wrote:

The current implementation for motion detection uses polling. Every 5 seconds it checks to see if a motion detection event has happened. Obviously this can cause up to 5 seconds of delay between the event and the motion detection binary sensor changing to on.

The camera HTTP API does allow for subscribing to events, but that feature has yet to be used. Work is now being done to switch to this method. However, there are many camera models out there, with many different firmware versions in use. It would be helpful to gather some data about how these various cameras respond to the command.

To that end I’ve written a small Python script that will subscribe to the video motion detection event and output the received data when these events occur. If anyone would be willing to run it and share their results (especially if they are different from previously shared results), it would be much appreciated.

All you need is a command line that can run python3, and has the amcrest package installed. You can do this in a Python virtual environment like so:

python3 -m venv venv
source venv/bin/activate

Then run deactivate when you’re done.

Run the test like so:

python3 test_events.py host port user password

Where host is the camera’s IP address, port is the port number it listens on (80 is the default), user is the username of an account on the camera (admin is the default), and password is the account’s password.

When I run it on one of my cameras, I get output like this:

2020-01-22 22:42:02 'Code=VideoMotion;action=Start;index=0'
2020-01-22 22:42:05 'Code=VideoMotion;action=Stop;index=0'
2020-01-22 22:42:05 'Code=VideoMotion;action=Start;index=0'
2020-01-22 22:42:11 'Code=VideoMotion;action=Stop;index=0'

The pair of Start & Stop lines are printed for each motion detection event.

End the test by typing Ctrl-C.

Of course, motion detection needs to be enabled. You can do this via HA by using the camera.enable_motion_detection service. The test script can run at the same time HA is controlling the camera. There is no conflict between the two.

And now for the script. You can get it from here. (Be sure to use the Raw button when downloading.)

Thanks in advance!

Posts: 1

Participants: 1

Read full topic

@lazza wrote:

I have a automation created in the front end that i feel should work but it doesn’t and wondering if anyone can assist.

I live in a RV/caravan so my location changes all the time as i travel the country. My RVWiFi router " used to " report the geo location of my switches using NMAP. but since a recent router firmware update there is no space left on the router to reinstall extra packages.

So… plan b was to create a automation that detected when i drive away from the caravan ( using the switch.ute_power entity). If its unavailable then i’m not near the caravan. But when i return and switch.ute_power shows “off” then i must be near the caravan, so use my phones lat and longitude data to update the lat and long attributes of the router and the caravans location and set.location.

However, the below automation sends me the Telegram message saying its been updated but when i look in the states tab both person.caravan and the RVWiiFi device tracker and set.location still have incorrect coordinates. Any suggestions please ?

oh and if i copy the value templates into the templates tab it returns correct details so assuming they are actually correct.

alias: Update Location
  trigger:
  - entity_id: switch.ute_power
    for: '15'
    from: unavailable
    platform: state
    to: 'off'
  condition:
  - condition: and
    conditions:
    - condition: template
      value_template: 'value_template: "{{ ( states.person.larry.attributes.latitude  )
        != ( states.person.caravan.attributes.latitude ) }}"'
  action:
  - data:
      latitude: '{{ states.person.larry.attributes.latitude }}'
      longitude: '{{ states.person.larry.attributes.longitude }}'
    data_template:
      latitude: '{{ states.device_tracker.rvwifi_lan.attributes.latitude }}'
      longitude: '{{ states.device_tracker.rvwifi_lan.attributes.longitude }}'
    service: homeassistant.set_location
  - data:
      message: The Caravans location has just been updated
    service: notify.larrys_phone
  - data:
      latitude: '{{ states.person.larry.attributes.latitude }}'
      longitude: '{{ states.person.larry.attributes.longitude }}'
    entity_id: person.caravan,  device_tracker.rvwifi_lan
    service: homeassistant.update_entity

Happy to not focus on the Router getting updated as im not concerned about that. But back a few months ago when i had it working using nmap the reasoning was … If “person.caravan” changes location then set.location to person.caravans new coordinates

cheers

Posts: 2

Participants: 1

Read full topic

@DessertBesom wrote:

Hi,
I try to setup mqtt, but it does not work. I tested with several variants (host networking, bridge, external ip, localhost, container ip) but ha is not able to talk with mqtt. Other devices in my network can communicate with mqtt broker.

• latest HA in docker (no HASS) on armv7 with host networking
• Mosquitto MQTT 1.6 in docker on armv7 with bridged networking, port 1883 exposed

ha startup logs

2020-01-23 08:07:01 INFO (MainThread) [homeassistant.setup] Setting up mqtt
2020-01-23 08:07:01 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.0 seconds.
2020-01-23 08:07:01 ERROR (MainThread) [homeassistant.setup] Setup failed for mqtt: Integration failed to initialize.
2020-01-23 08:07:02 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform mqtt.sensor: Unable to set up component.
2020-01-23 08:07:02 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform mqtt.sensor: Unable to set up component.

configuration.yaml

mqtt:
  broker: 192.168.1.20
  port: 1883

As there is no additional error message in ha, I dont know how to solve this issue…

Edit: I configured integration with same settings in ha web ui and it works. What is the difference? Should I create a issue on Github?

Posts: 1

Participants: 1

Read full topic

@myxor wrote:

Hello community,
this is my first post here so please be kind to me

I configured an automation which should turn on the kitchen light in the morning if at least one of two devices are at home and the sun is not yet up.
The device trackers are working and manually switching the light on and off is working as well but this automation is never triggering.
The sun-up change is happened are around 8:15 here right now so this should be okay, too.

Can you help me finding out what is wrong here?

- id: '1579591309996'
  alias: Turn light on in the morning if someone is at home
  description: ''
  trigger:
  - at: 06:45:00
    platform: time
  condition:
  - condition: device
    device_id: fd03bb[...]da
    domain: device_tracker
    entity_id: device_tracker.ane_lx1
    type: is_home
  - condition: or
    conditions:
    - condition: device
      device_id: caa8fa[...]b5
      domain: device_tracker
      entity_id: device_tracker.oneplus_a5000
      type: is_home
  - condition: and
    conditions:
    - before: sunrise
      condition: sun
  action:
  - device_id: 4bfb4[...]1e
    domain: light
    entity_id: light.kitchen
    type: turn_on

(i shortened the device_ids in this code, in real they are longer of course )

Thank you in advance

Posts: 1

Participants: 1

Read full topic

@Van wrote:

Hi all,

I not sure how to get the trigger to use group similar to how you would list each entity.

for example:

- alias: test
  trigger:
    - platform: state
      entity_id: switch.s1,switch.s2,switch.s3,switch.s4
      to: 'on'
  action:
  - service: persistent_notification.create
    data_template:
      message: "{{ states['switch'] | selectattr('entity_id','in',state_attr('group.mygroup','entity_id')) | selectattr('state','eq','on') | list  }}"
      title: "Group test"

This would get a trigger on every switch state is on. Meaning it if I turn on 3 switches, I would get 3 alerts.

If I change the code to:

- alias: test
  trigger:
    - platform: state
      entity_id: group.mygroup
      to: 'on'
...

Then I would only get a trigger on the first switch that turns on.
If I turn on the 2nd switch, nothing happens.

I tries using platform: template as well and it doesn’t seem to work

- alias: test
  trigger:
    - platform: template
      value_template: "states['switch'] | selectattr('entity_id','in',state_attr('group.mygroup','entity_id')) | selectattr('state','eq','on') | list | count > 0 }}"
...

Is there a way I can get a notification when a switch is turned on regardless of the state of the other switches using group?

Thanks,
Van

Posts: 2

Participants: 2

Read full topic

@D3nnisd wrote:

Hi,

Until recently, KNX on Home-assistant with HASSOS on a RPI 3b+ has been a blessing. Fast and reliable. However, since a few weeks it seems to be slow responding. If i turn on or off a device, it takes 1 or 2 seconds showing up on the bus.

Is this because i have to much devices?

I tried using a Wiser HomeLynk and a Baos 771. Both have the same result.

Kind regards,

Posts: 4

Participants: 2

Read full topic

@ibstyln wrote:

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

Posts: 1

Participants: 1

Read full topic

@HemiBob wrote:

How can I stop getting notifications that a new device has been found when it’s not new and has been working fine for weeks?
If I dismiss the notification, it comes right back on the next restart of HA.
If I click on the “Check it out” link, it has “discovered” my Hue hub. So if I then follow the instructions to configure it again, it comes up with “Unknown linking error occurred.”
I don’t want to delete the Hue hub and start again, I don’t want to turn off auto-discovery, I just want to stop the notification for the Hue.

Posts: 2

Participants: 2

Read full topic

@Fredrik_Jacobsson wrote:

I try to set up MQTT, Mosquitto broker addon in Hassio.
But I can’t get it to work, can somebody give me a hand.

image497×851 24.4 KB

And I have created following user for the MQTT.

Posts: 2

Participants: 2

Read full topic

@lseufer wrote:

Hi,

Stupid question, but is there a way to disable the warning logs saying “You are using a custom integration for…”?

I am aware I am using custom components, I installed them.

Thanks.

Posts: 2

Participants: 2

Read full topic

@Ener-G wrote:

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

Posts: 1

Participants: 1

Read full topic

@zhulik wrote:

Hello! I’m trying to builda script that saves and then restores states of my lights, there is a very useful feature in the scene.create service called snapshot_entities, but it seems like it is not recursive. This means it simply does not support snapshotting states of all members of groups recursively.

So if I try to snapshot a group:

  - service: scene.create
    data_template:
      scene_id: before
      snapshot_entities:
        - group.living_room

It saves the state of the whole group.

For example: I have my ceiling light switched off and my floor light switched on. I create a scene with the script from above. This group includes both of those lights. Then I apply a different scene for some time, and when I restore the initial state both bulbs in the group get the same state - the state of the floor light(which was also the state of the group).

Is it possible to snapshot states of groups recursively?

Thank you!

Posts: 1

Participants: 1

Read full topic

@hajo62 wrote:

I have some sensors from xiaomi, which are not very reliable.
The Pi looses the connection to my Xiaomi bluetooth temperature sensors every now and than. Only a Pi reboot does a reconnect. Other temperature sensors need a manual activity to reconnect.

My idea is to do an automatic reboot, when one of the bluetooth sensors got no new value i.e. for more than 1 hour.

Second I would like to display something, when one of my sensor has paused to long. I.e. a traffic light. Green 0 to 30 minutes, yellow from 30 to 60 and red above…

Might someone have an idea how to realize that?
(I’ve never made an automation…)

Posts: 7

Participants: 2

Read full topic

@ibstyln wrote:

Users status never changes and don’t show up on map. The icons for the zones appear on the map but not the device tracker(s). User status always states away even though I work from home quite a bit.

config file entries

zone:
  - name: Home
    latitude: coordinates of home are entered here
    longitude: coordinates of home are entered here
    radius: 100
    icon: mdi:home
    
  - name: MikeWork
    latitude: 38.932903
    longitude: -94.691920
    icon: mdi:office-building
    
  - name: JenniferWork
    latitude: 39.043003
    longitude: -94.592940
    icon: mdi:office-building

proximity:
  mike_home:
    zone: Home
    devices:
      - device_tracker.mike
    tolerance: 50
    unit_of_measurement: mi
  jennifer_home:
    zone: Home
    devices:
      - device_tracker.jennifer
    tolerance: 50
    unit_of_measurement: mi

Posts: 1

Participants: 1

Read full topic

@nicktheguitar wrote:

I’m building the automations to use tradfri 5 button remotes as light switches for my kids, using the Deconz Conbee2 stick. I’ve got the one below to work dimming one light, but I’d like one button to work dimming two lights, but only if they’re on. The same goes for another button but for brightness.

How would the data template work if I were to add light.ed_lamp and a condition that the action would only work if the light were already on?

- id: 'ed_main_dimmer_from_switch'
  alias: Ed Main Dimmer From Switch
  initial_state: 'on'
  trigger:
    platform: event
    event_type: deconz_event
    event_data:
      id: ed_switch
      event: 3002
  action:
  - service: light.turn_on
    data_template:
      entity_id: light.ed_main
      brightness: '{% set bri = state_attr(''light.ed_main'', ''brightness'') |
        int %} {{ [bri-30, 0] | max }}'

Posts: 1

Participants: 1

Read full topic

@letohicy wrote:

Hi everybody,

A couple of hours since I’m stuck in setting z-wave. I’ve read more then once the documentation and several topics here, but without any success. So, my turn to ask for your help.

I’ve received today my Sigma Designs Z-Wave Plus dongle, with some Eurotronic Spirit Z-Wave+ TRV. I’ve plugged the USB on my RPI3 (running Hass.IO), update the configuration.yaml and restart HA : OpenZWave start the network and … nothing. Like OZW is continuously starting the network.

(Sorry - still in French)

For information, initially I was running HA 0.103.x. After few hours I’ve upgrade to 0.104.3 to check if that could make any difference (spoiler alert : no).
I’ve also try the 3 differents “address” for the usb in the configuration.yaml :

/dev/ttyACM0
/dev/ttyAMA0
/dev/serial/by-id/usb-0658_0200_32303136-3131-3033-3030-303032343933-if00

But I still have the same log into OZW :

2020-01-23 22:37:10.131 Always, OpenZwave Version 1.4.3452 Starting Up
2020-01-23 22:37:43.250 Info, Setting Up Provided Network Key for Secure Communications
2020-01-23 22:37:43.250 Warning, Failed - Network Key Not Set
2020-01-23 22:37:43.250 Info, mgr,     Added driver for controller /dev/serial/by-id/usb-0658_0200_32303136-3131-3033-3030-303032343933-if00
2020-01-23 22:37:43.250 Info,   Opening controller /dev/serial/by-id/usb-0658_0200_32303136-3131-3033-3030-303032343933-if00
2020-01-23 22:37:43.250 Info, Trying to open serial port /dev/serial/by-id/usb-0658_0200_32303136-3131-3033-3030-303032343933-if00 (attempt 1)
2020-01-23 22:37:43.251 Info, Serial port /dev/serial/by-id/usb-0658_0200_32303136-3131-3033-3030-303032343933-if00 opened (attempt 1)
2020-01-23 22:37:43.252 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-01-23 22:37:43.252 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-01-23 22:37:43.252 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-01-23 22:37:43.252 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-01-23 22:37:43.252 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-01-23 22:37:43.252 Detail,
2020-01-23 22:37:43.252 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-01-23 22:37:43.255 Detail, contrlr,   Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x31, 0x00, 0x01, 0x91
2020-01-23 22:37:43.255 Detail,
2020-01-23 22:37:43.255 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2020-01-23 22:37:43.255 Info, contrlr,     Static Controller library, version Z-Wave 6.01
2020-01-23 22:37:43.255 Detail, Node045,   Expected reply was received
2020-01-23 22:37:43.255 Detail, Node045,   Message transaction complete
2020-01-23 22:37:43.255 Detail,
2020-01-23 22:37:43.255 Detail, contrlr, Removing current message
2020-01-23 22:37:43.255 Detail,
2020-01-23 22:37:43.255 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-01-23 22:37:43.258 Detail, contrlr,   Received: 0x01, 0x08, 0x01, 0x20, 0xff, 0xff, 0xff, 0xfe, 0xef, 0x38
2020-01-23 22:37:43.259 Detail,
2020-01-23 22:37:43.259 Info, contrlr, Received reply to FUNC_ID_ZW_MEMORY_GET_ID. Home ID = 0xfffffffe.  Our node ID = 239
2020-01-23 22:37:43.259 Detail, contrlr,   Expected reply was received
2020-01-23 22:37:43.259 Detail, contrlr,   Message transaction complete
2020-01-23 22:37:43.259 Detail,
2020-01-23 22:37:43.259 Detail, contrlr, Removing current message
2020-01-23 22:37:43.259 Detail,
2020-01-23 22:37:43.259 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-01-23 22:37:43.261 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x05, 0x28, 0xd7
2020-01-23 22:37:43.261 Detail,
2020-01-23 22:37:43.261 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2020-01-23 22:37:43.261 Info, contrlr,     There is no SUC ID Server (SIS) in this network.
2020-01-23 22:37:43.261 Info, contrlr,     The PC controller is a primary controller.
2020-01-23 22:37:43.261 Detail, Node215,   Expected reply was received
2020-01-23 22:37:43.261 Detail, Node215,   Message transaction complete
2020-01-23 22:37:43.261 Detail,
2020-01-23 22:37:43.261 Detail, contrlr, Removing current message
2020-01-23 22:37:43.261 Detail,
2020-01-23 22:37:43.261 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-01-23 22:37:43.265 Detail, contrlr,   Received: 0x01, 0x2b, 0x01, 0x07, 0x05, 0x0e, 0x00, 0x00, 0x00, 0x03, 0x00, 0x08, 0xfe, 0x87, 0x7f, 0x88, 0xcf, 0x7f, 0xc0, 0x4f, 0xfb, 0xdf, 0xfd, 0xe0, 0x67, 0x00, 0x80, 0x80, 0x00, 0x80, 0x86, 0x00, 0x01, 0x00, 0xe8, 0x73, 0x00, 0x80, 0x0f, 0x00, 0x00, 0x60, 0x00, 0x00, 0x4e
2020-01-23 22:37:43.266 Detail,
2020-01-23 22:37:43.266 Info, contrlr,  Received reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES
2020-01-23 22:37:43.266 Info, contrlr,     Serial API Version:   5.14
2020-01-23 22:37:43.266 Info, contrlr,     Manufacturer ID:      0x0000
2020-01-23 22:37:43.266 Info, contrlr,     Product Type:         0x0003
2020-01-23 22:37:43.266 Info, contrlr,     Product ID:           0x0008
2020-01-23 22:37:43.266 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2020-01-23 22:37:43.266 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2020-01-23 22:37:43.266 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2020-01-23 22:37:43.266 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2020-01-23 22:37:43.266 Detail, Node014,   Expected reply was received
2020-01-23 22:37:43.266 Detail, Node014,   Message transaction complete
2020-01-23 22:37:43.266 Detail,
2020-01-23 22:37:43.266 Detail, contrlr, Removing current message
2020-01-23 22:37:43.266 Detail,
2020-01-23 22:37:43.266 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-01-23 22:37:43.268 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x56, 0x00, 0xac
2020-01-23 22:37:43.268 Detail,
2020-01-23 22:37:43.268 Info, contrlr, Received reply to GET_SUC_NODE_ID.  Node ID = 0
2020-01-23 22:37:43.268 Info, Controller Does not Support SUC - Cannot Setup Controller as SUC Node
2020-01-23 22:37:43.268 Detail, Node172,   Expected reply was received
2020-01-23 22:37:43.268 Detail, Node172,   Message transaction complete
2020-01-23 22:37:43.268 Detail,
2020-01-23 22:37:43.268 Detail, contrlr, Removing current message
2020-01-23 22:37:43.269 Detail,
2020-01-23 22:37:43.269 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x1c) - FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2020-01-23 22:37:43.326 Detail, contrlr,   Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0xd8, 0xfb, 0xd1, 0xb2, 0x14, 0xac, 0x93, 0x26, 0x95, 0x1b, 0x28, 0x3c, 0x31, 0x79, 0xd6, 0xf7, 0x59, 0x99, 0xc9, 0x65, 0x18, 0x30, 0xf0, 0x7a, 0x32, 0xc8, 0xf2, 0x52, 0x09, 0xfa, 0xc9, 0x14, 0xe2
2020-01-23 22:37:43.326 Detail,
2020-01-23 22:37:43.326 Info, contrlr, Received reply to FUNC_ID_ZW_GET_RANDOM: true
2020-01-23 22:37:43.326 Detail, Node032,   Expected reply was received
2020-01-23 22:37:43.326 Detail, Node032,   Message transaction complete
2020-01-23 22:37:43.326 Detail,
2020-01-23 22:37:43.326 Detail, contrlr, Removing current message
2020-01-23 22:37:43.326 Detail,
2020-01-23 22:37:43.327 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x02) - FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2020-01-23 22:37:43.424 Detail, contrlr,   Received: 0x01, 0x25, 0x01, 0x02, 0x08, 0x00, 0x1d, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x00, 0xc9
2020-01-23 22:37:43.424 Detail,
2020-01-23 22:37:43.424 Info, mgr,     Driver with Home ID of 0xfffffffe is now ready.
2020-01-23 22:37:43.424 Info,
2020-01-23 22:37:43.424 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_INIT_DATA:
2020-01-23 22:37:43.424 Detail,   Expected reply was received
2020-01-23 22:37:43.424 Detail,   Message transaction complete
2020-01-23 22:37:43.424 Detail,
2020-01-23 22:37:43.424 Detail, contrlr, Removing current message
2020-01-23 22:37:43.424 Detail, Node239, Notification: DriverReady
2020-01-23 22:37:43.427 Detail,
2020-01-23 22:37:43.428 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x06) - FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2020-01-23 22:37:43.432 Detail, contrlr,   Received: 0x01, 0x05, 0x01, 0x06, 0x64, 0x0f, 0x96
2020-01-23 22:37:43.434 Detail,
2020-01-23 22:37:43.434 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_SET_TIMEOUTS
2020-01-23 22:37:43.434 Detail, Node015,   Expected reply was received
2020-01-23 22:37:43.434 Detail, Node015,   Message transaction complete
2020-01-23 22:37:43.434 Detail,
2020-01-23 22:37:43.434 Detail, contrlr, Removing current message
2020-01-23 22:37:43.435 Detail,
2020-01-23 22:37:43.435 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x00) - FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2020-01-23 22:37:43.438 Detail, contrlr, Removing current message

If you have any idea on how to resolve this problem, I’m ready to hear it

Posts: 10

Participants: 3

Read full topic

@NicolasG wrote:

Hey there,
I have a specific switch which is just a power toggle button for a device, so I don’t want the switch to be appear “on” when I press it, it should always think that I haven’t pressed it before. Is there a way to always have the value_template as false/off?

  - platform: template
    switches:
     klrst3g:
       value_template: "{{ is_state('script.klrst3g_onoff', 'on')}}"
       turn_on:
         service: script.turn_on
         entity_id: script.klrst3g_onoff
       turn_off:
         service: script.turn_on
         entity_id: script.klrst3g_onoff

Posts: 2

Participants: 2

Read full topic