@tomdh76 wrote:

I have a aeotec z wave light bulb multi color level zwa002 which cannot be turned off. I have hass on docker v0.106.6.

Inclusion goes well.

After inclusion I can turn it off by the switch in the frontend.

In the evening the light turns on by an automation rule.
When I go to sleep the light should be turned off by an automation rule as all other lights however this does not happen. And also I cannot turn it off in the frontend. The switch goes to the off position and then quickly goes to the on position again.

I did several inclusion and exclusions

The OZW_log I cannot understand well but I do not see errors at first sight.

The light is in a good mesh and has 18 neighbours.

Any suggestion where to troubleshoot?
Or is the light DOA?

Posts: 1

Participants: 1

Read full topic

@mefistofelis wrote:

If I enter the following in developers tools template i get the minutes that have passed since the door was closed. When I use it as a template sensor i get 0.

This works:
{{ ((as_timestamp(now())-as_timestamp(states.binary_sensor.sensor.last_changed))/60) | round | int }}

This doesnt:

- platform: template
  sensors:
    door_closed_since:
      entity_id: binary_sensor.sensor
      value_template: "{{ ((as_timestamp(now())-as_timestamp(states.binary_sensor.sensor.last_changed))/60) | round | int }}"
      friendly_name: "Time since Door was closed"

Any help?

Posts: 3

Participants: 2

Read full topic

@ncortines wrote:

Hi,

I have a Generic Thermostat that triggers a MQTT Switch to open/close the valve of a water heater:

- platform: mqtt
  name: "heater_bedroom"
  state_topic: "bedroom/relay/state"
  command_topic: "bedroom/relay/set"
  payload_on: 1
  payload_off: 0
  state_on: "1"
  state_off: "0"
  retain: true

- platform: generic_thermostat
  name: thermostat_bedroom
  heater: switch.heater_bedroom
  target_sensor: sensor.temperature_xiaomi_air_1
  min_temp: 16
  max_temp: 26
  ac_mode: False
  target_temp: 20.5
  cold_tolerance: 0.1
  hot_tolerance: 0.1
  min_cycle_duration:
    seconds: 5
  keep_alive:
    minutes: 3
  initial_operation_mode: "auto"
  away_temp: 16

I also have an automation that triggers the central heating boiler whenever 1 or more heater switches are open:

- id: enable_boiler
  alias: Enable Boiler
  trigger:
    - platform: state
      entity_id:
        - group.all_heaters
      to: 'on'
      from: 'off'
  action:
    - service: switch.turn_on
      data:
        entity_id:
          - switch.boiler

This configuration works pretty well (I’ve been using it for the whole season without glitches) until, for whatever the reason, one of the heater’s MQTT Switches disconnects.

If one of the heater’s MQTT Switches disconnects while the State was “ON”, it remains “ON”, and my Boiler keeps heating even though the heater’s MQTT Switch now is closed, because those are Normally Closed valves.

So basically, the ideal solution for me would be a MQTT Switch that changes state to “OFF” when the connection to the client is lost.

What could be a solution for my problem?

Thanks!
Juan

Posts: 8

Participants: 4

Read full topic

@perryflynn wrote:

Hi,

I am working on a reliable connection of my Zigbee Dongle (Conbee II) to Home Assistant Core which is running as Docker Container. I am using usbip to bring the Zigbee Dongle from a Raspberry Pi to my Docker Server.

On the Raspberry Pi I have already a reboot-safe and hotplug-stable solution. Here the implementation steps as Ansible Playbook:

---

# root@dashboard:/etc/systemd/system# lsusb -d 1cf1:0030 -v

# Bus 001 Device 011: ID 1cf1:0030 Dresden Elektronik
# Device Descriptor:
#   bLength                18
#   bDescriptorType         1
#   bcdUSB               2.01
#   bDeviceClass            2 Communications
#   bDeviceSubClass         0
#   bDeviceProtocol         0
#   bMaxPacketSize0        64
#   idVendor           0x1cf1 Dresden Elektronik
#   idProduct          0x0030
#   bcdDevice            1.00
#   iManufacturer           1 dresden elektronik ingenieurtechnik GmbH
#   iProduct                2 ConBee II
#   iSerial                 3 DE2154525
#   bNumConfigurations      1


#
# -> Zigbee Host
#

- name: Setup usbip on Zigbee Stick Host
  hosts:
    - dashboard

  vars:
    usbvendorid: "1cf1"
    usbproductid: "0030"

  tasks:

    - name: Install usbip
      package:
        name: usbip
        state: present

    - name: Load kernel modules at boot
      copy:
        dest: /etc/modules-load.d/usbipd.conf
        owner: root
        group: root
        mode: u=rw,go=r
        content: |
          # load kernel modules needed for usbip daemon
          # this file is managed by ansible

          usbip_host

    - name: Load kernel modules now
      modprobe:
        name: usbip_host
        state: present

    - name: "Create vendor:product bind script for usbip"
      copy:
        dest: /usr/sbin/usbip-bind-vendorproduct
        owner: root
        group: root
        mode: u=rwx,go=r
        content: |
          #!/bin/bash

          VENDORPRODUCT=$(echo "$1" | sed 's/-/:/g')
          MODE=$2
          BUSID=$(usbip list -l | grep -oP "busid\s+([0-9\-\.]+)\s+\(${VENDORPRODUCT}\)" | head -n 1 | awk '{print $2}')
          USBIPACTIVE=$(pidof usbipd 2>&1 > /dev/null; echo $?)

          if [ $USBIPACTIVE -ne 0 ]; then
              echo "usbip daemon is not running"
              exit 1
          fi

          if [ "$MODE" == "bind" ]; then
              /usr/sbin/usbip bind -b $BUSID
          elif [ "$MODE" == "unbind" ]; then
              /usr/sbin/usbip unbind -b $BUSID
          else
              echo "Unknown Mode"
              exit 1
          fi

    - name: Create systemd unit for the zigbee stick
      copy:
        dest: /etc/systemd/system/usbip-device@.service
        owner: root
        group: root
        mode: u=rw,go=r
        content: |
          [Unit]
          Description=USB/IP Binding on %I
          After=network-online.target usbipd.service
          Wants=network-online.target
          Requires=usbipd.service

          [Service]
          Type=simple
          ExecStart=/usr/sbin/usbip-bind-vendorproduct %i bind
          RemainAfterExit=yes
          ExecStop=/usr/sbin/usbip-bind-vendorproduct %i unbind
          Restart=on-failure

          [Install]
          WantedBy=multi-user.target

    - name: Create systemd unit for usbip
      copy:
        dest: /etc/systemd/system/usbipd.service
        owner: root
        group: root
        mode: u=rw,go=r
        content: |
          [Unit]
          Description=USB/IP server
          After=network.target

          [Service]
          ExecStart=/usr/sbin/usbipd

          [Install]
          WantedBy=multi-user.target

    - name: Enable and start usbip dongle
      systemd:
        daemon_reload: yes
        enabled: yes
        name: "usbip-device@{{usbvendorid}}-{{usbproductid}}"

    - name: Enable and start usbipd service
      systemd:
        daemon_reload: yes
        enabled: yes
        name: usbipd
        state: started

    - name: Create udev hotplug trigger script
      copy:
        dest: /usr/sbin/usbip-hotplug-trigger
        owner: root
        group: root
        mode: u=rwx,go=r
        content: |
          #!/bin/bash

          /usr/sbin/usbip-bind-vendorproduct ${ID_VENDOR_ID}:${ID_MODEL_ID} bind

    - name: Create udev rule for hotplug dongle
      copy:
        dest: /etc/udev/rules.d/usbip.rules
        owner: root
        group: root
        mode: u=rw,go=r
        content: |
          ACTION=="add", ATTR{idVendor}=="{{usbvendorid}}", ATTR{idProduct}=="{{usbproductid}}", RUN+="/usr/sbin/usbip-hotplug-trigger"
      register: dongleudevrule

    - name: Restart udev
      service:
        name: udev
        state: restarted
      when: dongleudevrule.changed

Now the problem: The implementation of the communication between the usb device and hass is not reconnect-safe. If there is any issue with the communication between, the container needs to be restarted.

I am able to bring the usb device into the container with cgroup rules, so that I can hotplug:

docker create \
    --init \
    --name "hass" \
    --hostname hass \
    --network hassinternal \
    --device-cgroup-rule='c 166:0 rmw' \
    -v /containerdata/homeassistant:/config \
    -v /etc/localtime:/etc/localtime:ro \
    homeassistant/home-assistant:latest

Now I can start the container and add the device right afterwards. (If this works without any issues, I would create an extension of the container image and to the creation of the usb device via startup script.)

usbip attach -r dashboard -b 1-1.4
docker start hass
docker exec hass mknod /dev/ttyACM0 c 166 0

Until this point, it works without any problems. But if I detach the device or if there is a network issue, hass throws an exception and the implementation is broken until I restart the container:

2020-04-05 09:58:14 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.write_parameter' command
2020-04-05 09:58:14 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/zigpy_deconz/zigbee/application.py", line 36, in _reset_watchdog
    await self._api.write_parameter(NetworkParameter.watchdog_ttl, 3600)
  File "/usr/local/lib/python3.7/site-packages/zigpy_deconz/api.py", line 210, in _command
    return await asyncio.wait_for(fut, timeout=COMMAND_TIMEOUT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 449, in wait_for
    raise futures.TimeoutError()
concurrent.futures._base.TimeoutError
2020-04-05 09:58:49 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_request' command

Is there any way to make this more stable?

It would be awesome to have an reconnect mechanism in hass. I’ve already looked into the code, but my python skills are not strong enough.

Kind Regards
Christian

Posts: 1

Participants: 1

Read full topic

@devotio wrote:

I have recently bought a HeatIt Z-Dim device, which replaced a Fibaro Dimmer 2. I have some issues with it. I keep getting dead node. When it does work most commands are delayed, they also seem to delay the other Z-Wave dimmer I have (TBK plug).
I use a HeatIt Scene controller (node 16), which triggers a scene to turn on all lights, which include the HeatIt Z-Dim (node 17) and the TBK dimmer (node 14). What I notice is that the Z-Wave devices are turned on (or off) seconds later (more than 5 seconds). I also see that the Z-Dim (node 17) will turn on and then the TBK (node 14) will turn on quickly after. I guess that the Z-Wave mesh might be disturbed somehow, or that there is something wring with Z-Dim (node 17) and that TBK (node 14) is connected to the HA “further out” the Z-dim (node 17) in the mesh network.
I have tried to exclude the Z-Dim, but it won’t.
I have not set up a secure key, but have assumed that new versions of HA has done this automatically.

How can I resolve this, making the Z-Dim appear correctly (and not die)?
Is the delay commands related to taking out the Fibaro Dimmer (node 8) of the system (I did not exclude it)?

Below is the OZW logs:

2020-04-05 10:26:43.840 Detail, Node017, Queuing (Send) MeterCmd_Get (Node=17): 0x01, 0x0a, 0x00, 0x13, 0x11, 0x03, 0x32, 0x01, 0x00, 0x25, 0x52, 0xb0
2020-04-05 10:26:43.840 Detail, Node017, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_METER
2020-04-05 10:26:43.840 Detail, Node017, Queuing (Send) MeterCmd_Get (Node=17): 0x01, 0x0a, 0x00, 0x13, 0x11, 0x03, 0x32, 0x01, 0x10, 0x25, 0x53, 0xa1
2020-04-05 10:26:43.840 Info, Node017, CentralScene RequestState: 4
2020-04-05 10:26:43.840 Info, Node017, CentralScene: Not a StaticRequest
2020-04-05 10:26:43.841 Detail, Node017, Queuing (Query) Query Stage Complete (Dynamic)
2020-04-05 10:26:43.841 Detail,
2020-04-05 10:26:43.841 Info, Node017, Processing (Send) Nonce Request message (Callback ID=0x50, Expected Reply=0x04)
2020-04-05 10:26:43.841 Info, Node017, Sending (Send) message (Callback ID=0x50, Expected Reply=0x04) - Nonce_Get(SwitchBinaryCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x98, 0x40, 0x05, 0x02:
2020-04-05 10:26:43.848 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:43.848 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:43.948 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2020-04-05 10:26:43.949 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2020-04-05 10:26:43.949 Info, Node017, Request RTT 107 Average Request RTT 330
2020-04-05 10:26:44.029 Detail, Node017,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x11, 0x0a, 0x98, 0x80, 0x14, 0xc8, 0xd6, 0x36, 0x9b, 0x65, 0xd0, 0x6f, 0xbb, 0x00, 0x2c
2020-04-05 10:26:44.030 Info, Node017, Received SecurityCmd_NonceReport from node 17
2020-04-05 10:26:44.030 Info, Node017, Sending (Send) message (Callback ID=0x54, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=17): 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x25, 0x02, 0x25, 0x54, 0xa0
2020-04-05 10:26:44.043 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:44.044 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:44.179 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x54, 0x00, 0xbd
2020-04-05 10:26:44.179 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x54 received (expected 0x54)
2020-04-05 10:26:44.179 Info, Node017, Request RTT 339 Average Request RTT 334
2020-04-05 10:26:44.179 Detail,   Expected callbackId was received
2020-04-05 10:26:44.255 Detail, Node017,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x11, 0x02, 0x98, 0x40, 0xbb, 0x00, 0x81
2020-04-05 10:26:44.255 Info, Node017, Received SecurityCmd_NonceGet from node 17
2020-04-05 10:26:44.256 Info, NONCES: 0x03, 0xf3, 0x40, 0x28, 0x4d, 0xa6, 0xb2, 0xd8
2020-04-05 10:26:44.256 Info, NONCES: 0x61, 0x7b, 0xe6, 0x9a, 0xa5, 0x9f, 0xd4, 0x81
2020-04-05 10:26:44.256 Info, NONCES: 0x43, 0x3c, 0x5e, 0x53, 0x6d, 0xdb, 0x3b, 0x0a
2020-04-05 10:26:44.256 Info, NONCES: 0x26, 0xc3, 0x4a, 0x68, 0xb2, 0x01, 0xa2, 0x2f
2020-04-05 10:26:44.256 Info, NONCES: 0xbb, 0x04, 0xd3, 0x5c, 0x27, 0x9a, 0x7c, 0x5d
2020-04-05 10:26:44.256 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:44.256 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:44.256 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:44.256 Info, Node017, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x11, 0x0a, 0x98, 0x80, 0xbb, 0x04, 0xd3, 0x5c, 0x27, 0x9a, 0x7c, 0x5d, 0x05, 0x01, 0x56:
2020-04-05 10:26:44.267 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:44.267 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:44.396 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2020-04-05 10:26:44.396 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-04-05 10:26:44.396 Info, Node017, Request RTT 556 Average Request RTT 445
2020-04-05 10:26:44.486 Detail, Node017,   Received: 0x01, 0x1f, 0x00, 0x04, 0x00, 0x11, 0x17, 0x98, 0x81, 0x5a, 0xf4, 0x6f, 0xa2, 0x5b, 0x83, 0x18, 0x63, 0x53, 0x7c, 0x01, 0x85, 0xbb, 0x6d, 0x40, 0xa8, 0x42, 0xf0, 0x6f, 0xbf, 0x77, 0xbb, 0x00, 0x00
2020-04-05 10:26:44.487 Info, Raw: 0x98, 0x81, 0x5a, 0xf4, 0x6f, 0xa2, 0x5b, 0x83, 0x18, 0x63, 0x53, 0x7c, 0x01, 0x85, 0xbb, 0x6d, 0x40, 0xa8, 0x42, 0xf0, 0x6f, 0xbf, 0x77, 0xbb
2020-04-05 10:26:44.487 Detail, Node017, Decrypted Packet: 0x00, 0x25, 0x03, 0xff
2020-04-05 10:26:44.487 Detail,
2020-04-05 10:26:44.487 Info, Node017, Response RTT 647 Average Response RTT 725
2020-04-05 10:26:44.487 Info, Node017, Received SwitchBinary report from node 17: level=On
2020-04-05 10:26:44.487 Detail, Node017, Initial read of value
2020-04-05 10:26:44.487 Detail, Node017,   Expected reply and command class was received
2020-04-05 10:26:44.487 Detail, Node017,   Message transaction complete
2020-04-05 10:26:44.487 Detail,
2020-04-05 10:26:44.487 Detail, Node017, Removing current message
2020-04-05 10:26:44.488 Detail, Node017, Notification: ValueChanged
2020-04-05 10:26:44.502 Detail,
2020-04-05 10:26:44.502 Info, Node017, Processing (Send) Nonce Request message (Callback ID=0x51, Expected Reply=0x04)
2020-04-05 10:26:44.502 Info, Node017, Sending (Send) message (Callback ID=0x51, Expected Reply=0x04) - Nonce_Get(SwitchMultilevelCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x98, 0x40, 0x05, 0x02:
2020-04-05 10:26:44.510 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:44.511 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:44.628 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2020-04-05 10:26:44.628 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2020-04-05 10:26:44.628 Info, Node017, Request RTT 125 Average Request RTT 285
2020-04-05 10:26:44.710 Detail, Node017,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x11, 0x0a, 0x98, 0x80, 0x1a, 0x83, 0xc6, 0xdd, 0x33, 0x80, 0xa0, 0x38, 0xbb, 0x00, 0xf8
2020-04-05 10:26:44.710 Info, Node017, Received SecurityCmd_NonceReport from node 17
2020-04-05 10:26:44.710 Info, Node017, Sending (Send) message (Callback ID=0x55, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=17): 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x26, 0x02, 0x25, 0x55, 0xa2
2020-04-05 10:26:44.724 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:44.724 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:44.859 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x55, 0x00, 0xbc
2020-04-05 10:26:44.859 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x55 received (expected 0x55)
2020-04-05 10:26:44.859 Info, Node017, Request RTT 356 Average Request RTT 320
2020-04-05 10:26:44.859 Detail,   Expected callbackId was received
2020-04-05 10:26:44.935 Detail, Node017,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x11, 0x02, 0x98, 0x40, 0xbb, 0x00, 0x81
2020-04-05 10:26:44.936 Info, Node017, Received SecurityCmd_NonceGet from node 17
2020-04-05 10:26:44.936 Info, NONCES: 0x03, 0xf3, 0x40, 0x28, 0x4d, 0xa6, 0xb2, 0xd8
2020-04-05 10:26:44.936 Info, NONCES: 0x61, 0x7b, 0xe6, 0x9a, 0xa5, 0x9f, 0xd4, 0x81
2020-04-05 10:26:44.936 Info, NONCES: 0x43, 0x3c, 0x5e, 0x53, 0x6d, 0xdb, 0x3b, 0x0a
2020-04-05 10:26:44.936 Info, NONCES: 0x26, 0xc3, 0x4a, 0x68, 0xb2, 0x01, 0xa2, 0x2f
2020-04-05 10:26:44.936 Info, NONCES: 0xbb, 0x04, 0xd3, 0x5c, 0x27, 0x9a, 0x7c, 0x5d
2020-04-05 10:26:44.936 Info, NONCES: 0x01, 0x20, 0x21, 0xc8, 0x77, 0xef, 0xe5, 0x79
2020-04-05 10:26:44.936 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:44.936 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:44.936 Info, Node017, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x11, 0x0a, 0x98, 0x80, 0x01, 0x20, 0x21, 0xc8, 0x77, 0xef, 0xe5, 0x79, 0x05, 0x01, 0x36:
2020-04-05 10:26:44.947 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:44.947 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:45.076 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2020-04-05 10:26:45.076 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-04-05 10:26:45.076 Info, Node017, Request RTT 574 Average Request RTT 447
2020-04-05 10:26:45.167 Detail, Node017,   Received: 0x01, 0x21, 0x00, 0x04, 0x00, 0x11, 0x19, 0x98, 0x81, 0x2f, 0x7c, 0x3d, 0x90, 0xc8, 0x4b, 0xb5, 0x0f, 0x6f, 0x26, 0x28, 0x03, 0x75, 0xe6, 0x01, 0xd5, 0xa2, 0x9b, 0xe8, 0x6d, 0xba, 0x8a, 0xf2, 0xbb, 0x00, 0xec
2020-04-05 10:26:45.168 Info, Raw: 0x98, 0x81, 0x2f, 0x7c, 0x3d, 0x90, 0xc8, 0x4b, 0xb5, 0x0f, 0x6f, 0x26, 0x28, 0x03, 0x75, 0xe6, 0x01, 0xd5, 0xa2, 0x9b, 0xe8, 0x6d, 0xba, 0x8a, 0xf2, 0xbb
2020-04-05 10:26:45.168 Detail, Node017, Decrypted Packet: 0x00, 0x26, 0x03, 0x20, 0x20, 0x00
2020-04-05 10:26:45.168 Detail,
2020-04-05 10:26:45.168 Info, Node017, Response RTT 666 Average Response RTT 695
2020-04-05 10:26:45.168 Info, Node017, Received SwitchMultiLevel report: level=32
2020-04-05 10:26:45.168 Detail, Node017, Initial read of value
2020-04-05 10:26:45.168 Detail, Node017,   Expected reply and command class was received
2020-04-05 10:26:45.168 Detail, Node017,   Message transaction complete
2020-04-05 10:26:45.168 Detail,
2020-04-05 10:26:45.168 Detail, Node017, Removing current message
2020-04-05 10:26:45.169 Detail, Node017, Notification: ValueChanged
2020-04-05 10:26:45.182 Detail,
2020-04-05 10:26:45.183 Info, Node017, Processing (Send) Nonce Request message (Callback ID=0x52, Expected Reply=0x04)
2020-04-05 10:26:45.183 Info, Node017, Sending (Send) message (Callback ID=0x52, Expected Reply=0x04) - Nonce_Get(MeterCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x98, 0x40, 0x05, 0x02:
2020-04-05 10:26:45.190 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:45.190 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:45.309 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2020-04-05 10:26:45.309 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2020-04-05 10:26:45.309 Info, Node017, Request RTT 126 Average Request RTT 286
2020-04-05 10:26:45.389 Detail, Node017,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x11, 0x0a, 0x98, 0x80, 0x99, 0x77, 0x5a, 0x90, 0x6e, 0x73, 0xe0, 0x25, 0xbb, 0x00, 0xad
2020-04-05 10:26:45.390 Info, Node017, Received SecurityCmd_NonceReport from node 17
2020-04-05 10:26:45.390 Info, Node017, Sending (Send) message (Callback ID=0x56, Expected Reply=0x04) - MeterCmd_Get (Node=17): 0x01, 0x0a, 0x00, 0x13, 0x11, 0x03, 0x32, 0x01, 0x00, 0x25, 0x56, 0xb4
2020-04-05 10:26:45.403 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:45.404 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:45.539 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x56, 0x00, 0xbf
2020-04-05 10:26:45.539 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x56 received (expected 0x56)
2020-04-05 10:26:45.539 Info, Node017, Request RTT 356 Average Request RTT 321
2020-04-05 10:26:45.539 Detail,   Expected callbackId was received
2020-04-05 10:26:45.615 Detail, Node017,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x11, 0x02, 0x98, 0x40, 0xb9, 0x00, 0x83
2020-04-05 10:26:45.615 Info, Node017, Received SecurityCmd_NonceGet from node 17
2020-04-05 10:26:45.616 Info, NONCES: 0x03, 0xf3, 0x40, 0x28, 0x4d, 0xa6, 0xb2, 0xd8
2020-04-05 10:26:45.616 Info, NONCES: 0x61, 0x7b, 0xe6, 0x9a, 0xa5, 0x9f, 0xd4, 0x81
2020-04-05 10:26:45.616 Info, NONCES: 0x43, 0x3c, 0x5e, 0x53, 0x6d, 0xdb, 0x3b, 0x0a
2020-04-05 10:26:45.616 Info, NONCES: 0x26, 0xc3, 0x4a, 0x68, 0xb2, 0x01, 0xa2, 0x2f
2020-04-05 10:26:45.616 Info, NONCES: 0xbb, 0x04, 0xd3, 0x5c, 0x27, 0x9a, 0x7c, 0x5d
2020-04-05 10:26:45.616 Info, NONCES: 0x01, 0x20, 0x21, 0xc8, 0x77, 0xef, 0xe5, 0x79
2020-04-05 10:26:45.616 Info, NONCES: 0x89, 0xf0, 0xa7, 0xbf, 0x4c, 0xb2, 0x3e, 0x83
2020-04-05 10:26:45.616 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:45.616 Info, Node017, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x11, 0x0a, 0x98, 0x80, 0x89, 0xf0, 0xa7, 0xbf, 0x4c, 0xb2, 0x3e, 0x83, 0x05, 0x01, 0xd8:
2020-04-05 10:26:45.627 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:45.627 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:45.756 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2020-04-05 10:26:45.756 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-04-05 10:26:45.756 Info, Node017, Request RTT 573 Average Request RTT 447
2020-04-05 10:26:45.913 Detail, Node017,   Received: 0x01, 0x2a, 0x00, 0x04, 0x00, 0x11, 0x22, 0x98, 0x81, 0x3b, 0xb7, 0x42, 0x75, 0x1a, 0x07, 0x17, 0xd4, 0x1d, 0x07, 0x42, 0x11, 0x23, 0x32, 0x9e, 0x69, 0x2f, 0x4d, 0x44, 0x37, 0xa6, 0x02, 0xc7, 0x89, 0x6a, 0xfc, 0x22, 0xb0, 0x68, 0xa7, 0x2b, 0xe2, 0xb9, 0x00, 0x71
2020-04-05 10:26:45.914 Info, Raw: 0x98, 0x81, 0x3b, 0xb7, 0x42, 0x75, 0x1a, 0x07, 0x17, 0xd4, 0x1d, 0x07, 0x42, 0x11, 0x23, 0x32, 0x9e, 0x69, 0x2f, 0x4d, 0x44, 0x37, 0xa6, 0x02, 0xc7, 0x89, 0x6a, 0xfc, 0x22, 0xb0, 0x68, 0xa7, 0x2b, 0xe2, 0xb9
2020-04-05 10:26:45.914 Detail, Node017, Decrypted Packet: 0x00, 0x32, 0x02, 0x21, 0x44, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:45.914 Detail,
2020-04-05 10:26:45.914 Info, Node017, Response RTT 731 Average Response RTT 713
2020-04-05 10:26:45.914 Detail, Node017, Refreshed Value: old value=false, new value=false, type=bool
2020-04-05 10:26:45.914 Detail, Node017, Changes to this value are not verified
2020-04-05 10:26:45.914 Info, Node017, Received Meter report from node 17: Energy=0.00kWh
2020-04-05 10:26:45.914 Detail, Node017, Refreshed Value: old value=0.00, new value=0.00, type=decimal
2020-04-05 10:26:45.914 Detail, Node017, Changes to this value are not verified
2020-04-05 10:26:45.914 Detail, Node017,   Expected reply and command class was received
2020-04-05 10:26:45.915 Detail, Node017,   Message transaction complete
2020-04-05 10:26:45.915 Detail,
2020-04-05 10:26:45.915 Detail, Node017, Removing current message
2020-04-05 10:26:45.915 Detail, Node017, Notification: ValueChanged
2020-04-05 10:26:45.927 Detail, Node017, Notification: ValueChanged
2020-04-05 10:26:45.938 Detail,
2020-04-05 10:26:45.938 Info, Node017, Processing (Send) Nonce Request message (Callback ID=0x53, Expected Reply=0x04)
2020-04-05 10:26:45.938 Info, Node017, Sending (Send) message (Callback ID=0x53, Expected Reply=0x04) - Nonce_Get(MeterCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x98, 0x40, 0x05, 0x02:
2020-04-05 10:26:45.945 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:45.945 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:46.049 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2020-04-05 10:26:46.049 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2020-04-05 10:26:46.049 Info, Node017, Request RTT 112 Average Request RTT 279
2020-04-05 10:26:46.129 Detail, Node017,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x11, 0x0a, 0x98, 0x80, 0x7c, 0x28, 0xf1, 0x62, 0x19, 0x3d, 0x9c, 0xd0, 0xbb, 0x00, 0xfe
2020-04-05 10:26:46.130 Info, Node017, Received SecurityCmd_NonceReport from node 17
2020-04-05 10:26:46.130 Info, Node017, Sending (Send) message (Callback ID=0x57, Expected Reply=0x04) - MeterCmd_Get (Node=17): 0x01, 0x0a, 0x00, 0x13, 0x11, 0x03, 0x32, 0x01, 0x10, 0x25, 0x57, 0xa5
2020-04-05 10:26:46.143 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:46.143 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:46.280 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x57, 0x00, 0xbe
2020-04-05 10:26:46.280 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x57 received (expected 0x57)
2020-04-05 10:26:46.280 Info, Node017, Request RTT 343 Average Request RTT 311
2020-04-05 10:26:46.280 Detail,   Expected callbackId was received
2020-04-05 10:26:46.355 Detail, Node017,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x11, 0x02, 0x98, 0x40, 0xb8, 0x00, 0x82
2020-04-05 10:26:46.355 Info, Node017, Received SecurityCmd_NonceGet from node 17
2020-04-05 10:26:46.356 Info, NONCES: 0x03, 0xf3, 0x40, 0x28, 0x4d, 0xa6, 0xb2, 0xd8
2020-04-05 10:26:46.356 Info, NONCES: 0x61, 0x7b, 0xe6, 0x9a, 0xa5, 0x9f, 0xd4, 0x81
2020-04-05 10:26:46.356 Info, NONCES: 0x43, 0x3c, 0x5e, 0x53, 0x6d, 0xdb, 0x3b, 0x0a
2020-04-05 10:26:46.356 Info, NONCES: 0x26, 0xc3, 0x4a, 0x68, 0xb2, 0x01, 0xa2, 0x2f
2020-04-05 10:26:46.356 Info, NONCES: 0xbb, 0x04, 0xd3, 0x5c, 0x27, 0x9a, 0x7c, 0x5d
2020-04-05 10:26:46.356 Info, NONCES: 0x01, 0x20, 0x21, 0xc8, 0x77, 0xef, 0xe5, 0x79
2020-04-05 10:26:46.356 Info, NONCES: 0x89, 0xf0, 0xa7, 0xbf, 0x4c, 0xb2, 0x3e, 0x83
2020-04-05 10:26:46.356 Info, NONCES: 0xb3, 0x29, 0x55, 0x6c, 0x0b, 0x07, 0x7d, 0x7f
2020-04-05 10:26:46.357 Info, Node017, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x11, 0x0a, 0x98, 0x80, 0xb3, 0x29, 0x55, 0x6c, 0x0b, 0x07, 0x7d, 0x7f, 0x05, 0x01, 0x57:
2020-04-05 10:26:46.366 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:26:46.367 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:26:46.496 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2020-04-05 10:26:46.496 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-04-05 10:26:46.496 Info, Node017, Request RTT 558 Average Request RTT 434
2020-04-05 10:26:46.590 Detail, Node017,   Received: 0x01, 0x26, 0x00, 0x04, 0x00, 0x11, 0x1e, 0x98, 0x81, 0xb3, 0xfb, 0xf7, 0xa6, 0x0e, 0xf0, 0x97, 0x6c, 0x5c, 0x8b, 0x04, 0x80, 0xc5, 0xe2, 0xf3, 0xc7, 0x2c, 0x2f, 0x6c, 0xb3, 0x7a, 0x0f, 0x39, 0x02, 0x8e, 0x7b, 0xb3, 0x44, 0xb9, 0x00, 0xbe
2020-04-05 10:26:46.590 Info, Raw: 0x98, 0x81, 0xb3, 0xfb, 0xf7, 0xa6, 0x0e, 0xf0, 0x97, 0x6c, 0x5c, 0x8b, 0x04, 0x80, 0xc5, 0xe2, 0xf3, 0xc7, 0x2c, 0x2f, 0x6c, 0xb3, 0x7a, 0x0f, 0x39, 0x02, 0x8e, 0x7b, 0xb3, 0x44, 0xb9
2020-04-05 10:26:46.590 Detail, Node017, Decrypted Packet: 0x00, 0x32, 0x02, 0x21, 0x52, 0x08, 0x34, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:26:46.590 Detail,
2020-04-05 10:26:46.590 Info, Node017, Response RTT 653 Average Response RTT 683
2020-04-05 10:26:46.590 Detail, Node017, Refreshed Value: old value=false, new value=false, type=bool
2020-04-05 10:26:46.590 Detail, Node017, Changes to this value are not verified
2020-04-05 10:26:46.591 Info, Node017, Received Meter report from node 17: Power=21.00W
2020-04-05 10:26:46.591 Detail, Node017, Initial read of value
2020-04-05 10:26:46.591 Detail, Node017,   Expected reply and command class was received
2020-04-05 10:26:46.591 Detail, Node017,   Message transaction complete
2020-04-05 10:26:46.591 Detail,
2020-04-05 10:26:46.591 Detail, Node017, Removing current message
2020-04-05 10:26:46.591 Detail, Node017, Notification: ValueChanged
2020-04-05 10:26:46.602 Detail, Node017, Notification: ValueChanged
2020-04-05 10:26:46.619 Detail, Node014, Query Stage Complete (Dynamic)
2020-04-05 10:26:46.619 Detail, Node014, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2020-04-05 10:26:46.619 Detail, Node014, QueryStage_Configuration
2020-04-05 10:26:46.619 Detail, Node014, QueryStage_Complete
2020-04-05 10:26:46.619 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2020-04-05 10:26:46.620 Warning, CheckCompletedNodeQueries all=0, deadFound=1 sleepingOnly=0
2020-04-05 10:26:46.620 Detail, Node014, Notification: NodeQueriesComplete
2020-04-05 10:26:46.623 Detail, Node017, Query Stage Complete (Dynamic)
2020-04-05 10:26:46.623 Detail, Node017, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2020-04-05 10:26:46.623 Detail, Node017, QueryStage_Configuration
2020-04-05 10:26:46.623 Detail, Node017, QueryStage_Complete
2020-04-05 10:26:46.623 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2020-04-05 10:26:46.623 Warning, CheckCompletedNodeQueries all=0, deadFound=1 sleepingOnly=1
2020-04-05 10:26:46.623 Info,          Node query processing complete except for sleeping nodes.
2020-04-05 10:26:46.623 Detail, Node017, Notification: NodeQueriesComplete
2020-04-05 10:26:46.625 Detail, contrlr, Notification: AwakeNodesQueried
2020-04-05 10:27:11.860 Detail, Node017,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x11, 0x02, 0x98, 0x40, 0xb5, 0x00, 0x8f
2020-04-05 10:27:11.860 Info, Node017, Received SecurityCmd_NonceGet from node 17
2020-04-05 10:27:11.861 Info, NONCES: 0x93, 0xd9, 0x2a, 0xc1, 0x54, 0x81, 0x42, 0x43
2020-04-05 10:27:11.861 Info, NONCES: 0x61, 0x7b, 0xe6, 0x9a, 0xa5, 0x9f, 0xd4, 0x81
2020-04-05 10:27:11.861 Info, NONCES: 0x43, 0x3c, 0x5e, 0x53, 0x6d, 0xdb, 0x3b, 0x0a
2020-04-05 10:27:11.861 Info, NONCES: 0x26, 0xc3, 0x4a, 0x68, 0xb2, 0x01, 0xa2, 0x2f
2020-04-05 10:27:11.861 Info, NONCES: 0xbb, 0x04, 0xd3, 0x5c, 0x27, 0x9a, 0x7c, 0x5d
2020-04-05 10:27:11.861 Info, NONCES: 0x01, 0x20, 0x21, 0xc8, 0x77, 0xef, 0xe5, 0x79
2020-04-05 10:27:11.861 Info, NONCES: 0x89, 0xf0, 0xa7, 0xbf, 0x4c, 0xb2, 0x3e, 0x83
2020-04-05 10:27:11.861 Info, NONCES: 0xb3, 0x29, 0x55, 0x6c, 0x0b, 0x07, 0x7d, 0x7f
2020-04-05 10:27:11.861 Info, Node017, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x11, 0x0a, 0x98, 0x80, 0x93, 0xd9, 0x2a, 0xc1, 0x54, 0x81, 0x42, 0x43, 0x05, 0x01, 0x8f:
2020-04-05 10:27:11.871 Detail,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:27:11.872 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:27:12.007 Detail,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2020-04-05 10:27:12.007 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-04-05 10:27:12.102 Detail, Node017,   Received: 0x01, 0x2a, 0x00, 0x04, 0x00, 0x11, 0x22, 0x98, 0x81, 0x73, 0x2a, 0xfe, 0x0c, 0xd9, 0x28, 0x1b, 0x58, 0x9c, 0x92, 0x08, 0xb5, 0xdb, 0x41, 0x8d, 0x70, 0x09, 0xb7, 0x73, 0x62, 0x40, 0x5e, 0x45, 0x93, 0x2f, 0xd6, 0x64, 0x2c, 0x26, 0xc4, 0x76, 0xa6, 0xb8, 0x00, 0x6a
2020-04-05 10:27:12.102 Info, Raw: 0x98, 0x81, 0x73, 0x2a, 0xfe, 0x0c, 0xd9, 0x28, 0x1b, 0x58, 0x9c, 0x92, 0x08, 0xb5, 0xdb, 0x41, 0x8d, 0x70, 0x09, 0xb7, 0x73, 0x62, 0x40, 0x5e, 0x45, 0x93, 0x2f, 0xd6, 0x64, 0x2c, 0x26, 0xc4, 0x76, 0xa6, 0xb8
2020-04-05 10:27:12.103 Detail, Node017, Decrypted Packet: 0x00, 0x32, 0x02, 0x21, 0x44, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-05 10:27:12.103 Detail,
2020-04-05 10:27:12.103 Detail, Node017, Refreshed Value: old value=false, new value=false, type=bool
2020-04-05 10:27:12.103 Detail, Node017, Changes to this value are not verified
2020-04-05 10:27:12.103 Info, Node017, Received Meter report from node 17: Energy=0.00kWh
2020-04-05 10:27:12.103 Detail, Node017, Refreshed Value: old value=0.00, new value=0.00, type=decimal
2020-04-05 10:27:12.103 Detail, Node017, Changes to this value are not verified
2020-04-05 10:27:12.103 Detail, Node017, Notification: ValueChanged
2020-04-05 10:27:12.114 Detail, Node017, Notification: ValueChanged
2020-04-05 10:27:39.133 Detail, Queuing (Controller) Remove Device
2020-04-05 10:27:39.134 Info, Remove Device
2020-04-05 10:27:39.134 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveDevice: 0x01, 0x05, 0x00, 0x4b, 0x81, 0x58, 0x68
2020-04-05 10:27:39.134 Detail, Notification: ControllerCommand - Starting
2020-04-05 10:27:39.135 Detail,
2020-04-05 10:27:39.135 Info, contrlr, Sending (Command) message (Callback ID=0x58, Expected Reply=0x4b) - ControllerCommand_RemoveDevice: 0x01, 0x05, 0x00, 0x4b, 0x81, 0x58, 0x68
2020-04-05 10:27:39.139 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4b, 0x58, 0x01, 0x00, 0x00, 0xea
2020-04-05 10:27:39.139 Detail,
2020-04-05 10:27:39.139 Info, FUNC_ID_ZW_REMOVE_NODE_FROM_NETWORK:
2020-04-05 10:27:39.139 Info, REMOVE_NODE_STATUS_LEARN_READY
2020-04-05 10:27:39.139 Detail, Node001,   Expected callbackId was received
2020-04-05 10:27:39.139 Detail, Node001,   Expected reply was received
2020-04-05 10:27:39.139 Detail, Node001,   Message transaction complete
2020-04-05 10:27:39.139 Detail,
2020-04-05 10:27:39.140 Detail, contrlr, Removing current message
2020-04-05 10:27:39.140 Detail, Notification: ControllerCommand - Waiting
2020-04-05 10:27:39.141 Info, WriteNextMsg Controller nothing to do
2020-04-05 10:28:22.222 Detail, Node017, AdvanceQueries queryPending=0 queryRetries=0 queryStage=ProtocolInfo live=1
2020-04-05 10:28:22.222 Detail, Node017, QueryStage_Probe
2020-04-05 10:28:22.222 Info, Node017, NoOperation::Set - Routing=true
2020-04-05 10:28:22.222 Detail, Node017, Queuing (NoOp) NoOperation_Set (Node=17): 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x00, 0x00, 0x25, 0x59, 0x8a
2020-04-05 10:28:22.223 Detail, Node017, Queuing (Query) Query Stage Complete (Probe)
2020-04-05 10:28:22.223 Detail,
2020-04-05 10:28:22.223 Info, Node017, Sending (NoOp) message (Callback ID=0x59, Expected Reply=0x13) - NoOperation_Set (Node=17): 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x00, 0x00, 0x25, 0x59, 0x8a
2020-04-05 10:28:22.231 Detail, Node017,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-05 10:28:22.232 Detail, Node017,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-05 10:28:22.287 Detail, Node017,   Received: 0x01, 0x05, 0x00, 0x13, 0x59, 0x00, 0xb0
2020-04-05 10:28:22.287 Detail, Node017,   ZW_SEND_DATA Request with callback ID 0x59 received (expected 0x59)
2020-04-05 10:28:22.287 Info, Node017, Request RTT 63 Average Request RTT 248
2020-04-05 10:28:22.287 Detail,   Expected callbackId was received
2020-04-05 10:28:22.287 Detail,   Expected reply was received
2020-04-05 10:28:22.287 Detail,   Message transaction complete
2020-04-05 10:28:22.287 Detail,
2020-04-05 10:28:22.288 Detail, Node017, Removing current message
2020-04-05 10:28:22.288 Detail, Node017, Notification: Notification - NoOperation

Posts: 1

Participants: 1

Read full topic

@stianhoe wrote:

I’ve made myself a markdown card, but i get weather i english.
Is there a way to translate this to another language?
code:

    Vær: {{ states('weather.svehogda_157') | capitalize}} og
    {{states.weather.svehogda_157.attributes["temperature"]}}°C

Posts: 1

Participants: 1

Read full topic

@dimmanramone wrote:

Hi

I decided to clean a little bit my configuration folders and I’m not totally sure which files are safe to delete. I can see the contents of some files can be found in core.config_entries.

The files I’m wondering about are:

• phue.conf
• plex.conf
• sabnzbd.conf
• harmony_harmony_hub.conf
• .uuid
• html5_push_registrations.conf

What about known_devices.yaml are there still device trackers that still using this file?

Thanks in advanced

Posts: 3

Participants: 2

Read full topic

@adamhisham wrote:

Hi,

HA noob here. Been trying to access my config folder via samba share but have been unsuccessful the whole day. Tried everything I can find on the internet. Here’s my samba log.

Any masters with ideas? thanks in advance

Samba Log 1742hrs 0504201490×162 21.5 KB

Posts: 1

Participants: 1

Read full topic

@CousinLarry wrote:

I have been shifting across all my containers from Synology NAS Docker to a Proxmox with an ubuntu VM. I have several containers running incl HA and Deconz but they don’t want to see each other. I have them both on the host network, but HA does not detect via Discovery the deconz container (which is working fine - has connected to all the zigbee devices in the house). Can anyone push in the right direction as to why it can’t be seen? Must be something to do with firewalls between Proxmox and Ubuntu?

EDIT I should point out HA can see via Discovery my Ecobee and Hue bridge no worries, but they are not running under docker of course…

Posts: 1

Participants: 1

Read full topic

@Djiest wrote:

I have HA running on my Synology NAS with a custom domain from DuckDNS and SSL from LetsEncrypt. I’m using my Synology as proxy server (which basically is nginx).
My router has port forwards for 443 to my Synology

https://foo.duckdns.org shows the Home Assistant login page. However when trying to login, the login page gives an error

Unable to connect to Home Assistant. Retry

In my console I can see that the websocket gives an error

Error during WebSocket handshake: Unexpected response code: 400

image1034×138 5.01 KB

Login itself works, because when I enter the wrong credentials, it states

Invalid username or password

Using HA on the local IP works flawless.

Does anybody know why I can not use HA remote via my custom domain & SSL?

Below are screenshots of my configurations

Port forwards on router

image763×92 4.95 KB

Reverse Proxy Rules in Synology

image470×547 13.7 KB

Certificate for domain

image844×131 3.29 KB

I’ve checked my Nginx configuration and it hass a passthrough for HA

image919×489 13.8 KB

And this is in my configuration.yaml

Hope anyone can help!

Posts: 1

Participants: 1

Read full topic

@Naobana wrote:

Hi all,

I have a problem with a pretty straightforward automation script. The problem is that the script not always triggers (while the conditions are true);

Sometimes it works for 3 days, and sometimes it only works one day. To get the script / trigger working again i need to restart HomeAssistant or i need to reload the automations.

The script:

  alias: Turn on fan if humidity is > 75 and temperature > 30 and fan is off
  description: ''
  trigger:
  - platform: template
    value_template: '{{ states.sensor.room_sensor_mijia_humidity.state | float > 75 }}'
  condition:
  - condition: template
    value_template: '{{ states.sensor.sonoffth_fan_ds18b20_temperature.state | float > 30 }}'
  - condition: state
    entity_id: switch.sonofftouch_t2afan
    state: 'off'
  action:
  - device_id: sdf3fd3ssd4fsdf
    domain: switch
    entity_id: switch.sonofftouch_t2afan
    type: turn_on

When the script doesn’t work i always check the conditions. The conditions are truebut the script will not always trigger.

I can fix this with a time_pattern trigger but is not a real nice solution. Right?

Thanks!

Posts: 11

Participants: 5

Read full topic

@orc.trial wrote:

hi
need some help figuring out how to extract value from the following response from a http sensor:
http request:

http://192.168.1.30:8688/controller/rest/devices/Zooz%20dimmer%20zen22/status?name=zooz%20dimmer%20a%20switch%20status

Raw response:

<sensors><sensor name="zooz dimmer a switch status">off</sensor></sensors>

I have this setup as a rest sensor in HA

sensor:
  - platform: rest
    #resource: http://192.168.1.30:8688/controller/rest/devices/Zooz%20dimmer%20zen22/status?name=zooz%20dimmer%20a%20switch%20status&name=zooz%20dimmer%20a%20switch%20status
    resource: http://192.168.1.30:8688/controller/rest/devices/Zooz%20dimmer%20zen22/status?name=zooz%20dimmer%20a%20switch%20status
    name: Dinning Light Status 
    #json_attributes: '{{sensor.["#text"]}}'
    value_template: '{{sensor."#text" }}'

without the value_template, on the UI it is displaying status as

{"sensors": {"sensor": {"@name": "zooz dimmer a switch status", "#text": "off"}}}

trying to figue out how to extract just the status and display “off” and not the entire raw response

value:template does not seem to like “#”

error message is

    Invalid config for [sensor.template]: invalid template (TemplateSyntaxError: expected name or number) for dictionary value @ data['sensors']['dinning_light_status']['value_template']. Got '{{sensor.["@name"] }}'. (See ?, line ?).
    Invalid config for [sensor.rest]: invalid template (TemplateSyntaxError: expected name or number) for dictionary value @ data['value_template']. Got '{{sensor.["#text"] }}'. (See ?, line ?).
    Invalid config for [sensor.rest]: invalid template (TemplateSyntaxError: expected name or number) for dictionary value @ data['value_template']. Got '{{sensor."#text" }}'. (See ?, line ?).

any ideas how to extract and display just the on / off value?

i understand the @ and # are being added as per:

https://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html

Posts: 2

Participants: 2

Read full topic

@bcowell wrote:

Running HA on a Raspberry PI and spent hours today making changes. It now loads in to safe mode and I can’t fix it. The last thing I did before it started loading in to safe mode was installing an update for the host under supervisor > updates.

I’m getting the following error messages. I’ve searched for ages and I can’t find a solution, tried removing the http: in configuration.yaml, tried adding the system_health: in configuration.yaml. I basically rmeoved most of the changes I have made today, any ideas please? These messages show in the logs.

Login attempt or request with invalid authentication from MYEXTERNAL IP

9:24:50 PM – http (WARNING) - message first occurred at 8:53:06 PM and shows up 363 times

Received message for unregistered webhook 6e02515c79457bee67124746a48b8723c0522aa4619586a7413e5

9:13:11 PM – webhook (WARNING) - message first occurred at 8:54:00 PM and shows up 4 times

Don’t use ‘server_host’ options with Hass.io

8:52:47 PM – Hass.io (WARNING)

This shows under info

System Health

System Health

error System Health component is not loaded. Add ‘system_health:’ to configuration.yaml

Posts: 1

Participants: 1

Read full topic

@smurfen wrote:

Hi!
I am running Hassos in Virtualbox on a Windows 2016 server.
I want to add an extra disk for storage available for use in HA (NOT expand the existing).
A extra physical SSD is added in the host machine, and i created a partition and formatted it with NTFS.

I am not a Linux guy, but how is the best approach to add this diskdrive/make it visible to HA?
Can i make a vhd in Virtualbox, add it to the virtual machine and some way mount it/make it visible for HA?

Posts: 1

Participants: 1

Read full topic

@itajackass wrote:

Hi i need to track battery level of my wall mounted tablet.
So i don’t need geolocalization and I can use my local MQTT mosquitto on my Raspberry.

After some research I see Owntracks is the best way but I don’t find how to configure app on my tablet.

In my configuration.yaml i’ve this:

mqtt:
  discovery: true
  broker: 192.168.2.5
  port: 1883
  birth_message:
    topic: 'hass/status'
    payload: 'online'
  will_message:
    topic: 'hass/status'
    payload: 'offline'

Can someone help my how to configure app on my tablet? i don’t undestand some fields to compile

Posts: 1

Participants: 1

Read full topic

@medri wrote:

Hi everyone,

since about 1 or 2 weeks I have a problem with my wol-switch. After updating to v107 my wol-switch won’t work anymore. When I switch on the switch in the UI it stays there for 2 secs and then jumps back to off. I have not touched any config nor changed anything else.

- platform: wake_on_lan
  mac: aa:bb:cc:dd:ee:ff
  name: Server
  host: 10.1.0.10

My HA runs standalone on a raspberry Pi on my IoT-VLAN with the IP 10.10.0.2. My firewall is set up accordingly.

Anyone else having this issue?

Regards
Manu

Posts: 1

Participants: 1

Read full topic

@MrRogers wrote:

I set up HA last year to automate some Christmas Lights. I’ve pretty much forgotten everything I learned from that.

My installation is via Docker on an Ubuntu powered laptop, using a HUSBZB-1 USB stick (Zigbee and Z-Wave).

Now I’d like to integrate a ZHA thermostat. I’ve read every topic I can find, and they seem to either end unresolved, or they ramble on and on. In some cases, links provided at the beginning of the topic are now dead. So I’m completely lost as to how to add this integration.

I have my HUSBZB-1 USB stick working fine. I have a Centralite Pearl 3000 series thermostat that is not hooked up yet but powered by batteries. My HA Overview shows a fan switch and battery sensor (so far), so I know I’ve successfully connected to it.

But I can’t seem to figure out how to do anything else with it. Can someone point me to the “next step”?

Thanks.
Jack

Posts: 2

Participants: 2

Read full topic

@Tonvenio wrote:

Hi everyone,

I recently purchased two Elgato Key Lights for streaming and they work well with my computer, but unfortunately cannot be added to HA.

They don’t know up on the integrations page and if I click on the plus button to add them manually, after entering their respective IP address, the following error turns up:

“Unknown error occurred.”

Screenshot 2020-04-05 at 14.54.401008×616 32.1 KB

The log entry reads:

File "/usr/src/homeassistant/homeassistant/components/elgato/config_flow.py", line 33, in async_step_user
    user_input[CONF_HOST], user_input[CONF_PORT]
  File "/usr/src/homeassistant/homeassistant/components/elgato/config_flow.py", line 136, in _get_elgato_info
    return await elgato.info()
  File "/usr/local/lib/python3.7/site-packages/elgato/elgato.py", line 86, in info
    return Info.from_dict(data)
  File "/usr/local/lib/python3.7/site-packages/elgato/models.py", line 48, in from_dict
    display_name=data["displayName"],

My router is a Unifi Router and a USG. mDNS is enabled.

Any idea what else I could try?
Thanks a lot!
Tonvenio

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

trying to count the number of persistent notifications with the string ‘rss_feeds’ I had this for loop, and I do think it worked correctly before:

          {% for state in states.persistent_notification  %}
            {% if 'rss_feed' in state.entity_id %}
              {% if loop.first %}{{loop.length}}
              {% endif %}
            {% endif %}
          {% endfor %}

I had an issue in case of 0, since this template then shows nothing… but, and this is what’s more surprising now, it doesnt even count at all anymore…

check this:

Schermafbeelding 2020-04-05 om 15.39.562274×526 78.4 KB

showing correctly there are 3 pers notifications, and 1 of them has the string ’ rss_feed’ in its entity_id:

Schermafbeelding 2020-04-05 om 15.33.362396×678 141 KB

yet the template shows nothing:

Schermafbeelding 2020-04-05 om 15.34.331724×616 58.7 KB

what am I doing wrong here, to not have it show 1, and, how can I show 0 if there is no notification with the string in the entity_id?

a binary_sensor test works fine too:

    {% set feed = states.persistent_notification
                |map(attribute='object_id')
               |join %}
    {{'rss_feed' in feed }}

Schermafbeelding 2020-04-05 om 15.42.591420×516 45.9 KB

thanks for having a look

Posts: 2

Participants: 2

Read full topic

@romainrg wrote:

Hello everybody !

I’m actually trying to include my Livolo switchs to HA.

With basic configuration I can juste control Lights toggle by using conf like this :

rfxtrx:
  device: /dev/ttyUSB0

switch:
  platform: rfxtrx
  automatic_add: true
  devices:
    0A140A20004010010F0000:
      name: lumiere_cuisine

I would like to define ON and OFF command separalty but not possible with RFXtrx entities …

Someone did something like this ?

Thanks

Posts: 1

Participants: 1

Read full topic