I added as stated in documentation to my config:
device_tracker:
- platform: bluetooth_tracker
I’ve restarted the hass.io but now device is found. Do I need to somehow enable bluetooth on my raspberry pi? Or it’s done by default?
1 post - 1 participant
On the picture element card under styles it shows you can change the color of your icon by typing
"--paper-item-icon-color": pink
It works for me ,but what is that? Is that some kind of code? Does it work only in home assistant? Can I do other things to icons with code like that ? Where can I learn more about that type of code?
I just spent 2 hours trying to figure out what “–paper-item-icon-color” is or means with no luck.
1 post - 1 participant
The order of persistent_notifications, displayed in the UI, used to be oldest on top and newest on the bottom.
In 0.117, the order has been reversed: newest on top, oldest on the bottom.
I didn’t see this UI alteration mentioned in the release notes other than a button was added to dismiss all persistent_notifications:
@mattmattmatt added the ability to dismiss all notifications at once, and the notifications pane will close when the last notification was dismissed.
Does anyone know if this reordering is by design or error?
Also, the message displayed when you hover over the notification’s time is located in the wrong place. It should appear close to the mouse pointer but it actually appears well below it (above the next message). Pretty sure that’s a bug and I’ll be reporting it.
1 post - 1 participant
Trying to create a single automation to call on of two different scripts using variables. The automation will get trigger when one of a handful of device_trackers changes state, and I’m trying to leverage templates to use only a single automation to handle this instead of new automations for each device_tracker I want to watch.
Current trigger:
condition:
platform: state
entity_id: device_tracker.iot_peloton, device_tracker.anthem_avm
That’s the easy part, the Action I’m trying to launch is one of two different scripts (either track_time_on' or track_time_off’ and then a variable depending on what entity trigger the automation.
Just not sure how to grab the trigger.entity_id and trigger.to_state correctly and have it work - and it’s a pain to ‘test’ this.
service_template: >-
{% if trigger.to_state == 'not_home' %}script.track_time_off
{% else %}script.track_time_on
{% endif %}
data_template:
var: >-
{% if 'peloton' in {{trigger.entity_id}} %}peloton
{% elif 'anthem' in {{trigger.entity_id}} %}anthem
{% else %}{% endif %}
I’m guessing my ’ or {{ or something is off, so figured I’d ask for help. Thank you in advance!
1 post - 1 participant
I would like to trigger a few things, such as lights turning on and blinds opening, when my Alexa alarm goes off.
I am using the “sensor.spare_room_dot_next_alarm” entity from the Alexa Media Player integration, but this outputs “2020-11-03T22:28:00+00 at Nov 2, 22:49”. The only part that is relevant to me is the “22:28:00” (which is the time the alarm is set for) but I don’t know how to extrapolate that part.
Any help would be greatly appreciated!
1 post - 1 participant
Hi everyone. I am new to Home Assistant and have just installed it on my Raspberry Pi 4. The only thing I have done is add the Mosquitto MQTT addon and started it. Right away I started getting errors on the Mosquitto log as below. I do not know what homeassistant is and why it needs to be on (my?) local database. Also, I checked my router local ip address’s and all of them start with 192.168.1.xxx, so I do not know what or who is trying to connect from 172.30.32.1 . I even tried to disable port 1883 and then rebooted Home Assistant but for some reason 172.30.32.1 is still able to try to connect on port 1883. The code below repeats over and over.
Can anyone suggest anything to try to get a handle on this?
Thanks
Clan
[WARN] Not found homeassistant on local database
1604352390: Socket error on client <unknown>, disconnecting.
1604352510: New connection from 172.30.32.1 on port 1883.
1604352510: Socket error on client <unknown>, disconnecting.
1604352630: New connection from 172.30.32.1 on port 1883.
1604352630: Socket error on client <unknown>, disconnecting.
1604352750: New connection from 172.30.32.1 on port 1883.
[WARN] Not found homeassistant on local database
1 post - 1 participant
Hello,
I am trying to control the behavior of a heater either with generic thermostat o with a timer on off cycle script.
The heater should usually work with the script on off , 10 seconds on and 10 off, and repeat,…
The generic thermostat triggers only when reach target temperature.
The problem I am founding is that although the thermostat turns on the heater, the script is running and turns of the heater off every 10 seconds.
also, and this is the origin of the problem: when the thermostat changes state on ->off, the script stops working and does not restart.
Any suggestions to achieve this task?
thank you.
heater reboot: turns script on if it is off
heater starter: turns of the script if reboot is on
Script: switch on, delay, switch off, delay
AUTOMATIONS:
- id: '1604258926397'
alias: heater reboot
description: ''
trigger:
- platform: state
entity_id: script.cycle
to: 'off'
condition: []
action:
- service: script.turn_on
data: {}
entity_id: script.cycle
mode: single
- id: '1604259021574'
alias: heater starter internal
description: ''
trigger:
- platform: state
entity_id: automation.heater_reboot_internal
to: 'on'
condition: []
action:
- service: script.turn_on
data: {}
entity_id: script.cycle
mode: single
SCRIPT:
cycle:
alias: Cycle On and OFF
sequence:
- service: switch.turn_on
data: {}
entity_id: switch.heater
- delay:
seconds: '{{ states(''input_number.time_on'') | int }}'
- service: switch.turn_off
data: {}
entity_id: switch.heater
- delay:
seconds: '{{ states(''input_number.time_off'') | int }}'
mode: single
1 post - 1 participant
Hi!
I had about 10 RfxTrx motion sensors set up in Home Assistant at the beginning of 2020. During the summer I neglected my Home Assistant. Now, that I have time for it again, checked how things are, and, of course, it all fell apart, as it usually happens with the passing of time.
The way RfxTrx is handled has changed. Used to be set up from yaml config, now it’s an “integration”. By setting the integration into a mode when devices are added automatically I can get my RfxTrx motion sensors recognized, however they are always on, they never turn off. This is a problem which existed before, but in the yaml I used ot be able to specify an “off_delay” which turned them off after 20 seconds of no motion. On the RfxTrx integration UI this cannot be done (and a lot of other things either).
So I tried to also add the RfxTrx into the yaml, like this:
rfxtrx:
device: /dev/ttyUSB0
devices:
binary_sensor.living_room_motion_sensor:
off_delay: 20
device_class: motion
The config is valid and there are no erros in the log, but this does not do a darn thing, like it used to in the past. Note that the device id (binary_sensor.living_room_motion_sensor) was taken from the developer tools -> states section after I have renamed the binary sensor in the list of devices of the RfxTrx integration.
So does anybody know how to correctly configure an RfxTrx motion sensor with the new Home Assistant?
1 post - 1 participant
I have a couple of IP cameras working with Blue Iris. I’ve been exploring the different ways of getting them cast to Chromecasts / Google Hub.
I’m running HassOS 4.15 (on Proxmox) with HA core 0.117.2
HA IP Address is 192.168.1.241 / Blue Iris IP is 192.168.1.243
I have the stream component “stream:” enabled in my main configuration.yaml
I have a generic camera defined…
This works OK in Lovelace via a Picture Entity card
If I call the camera.play_stream service against the camera using one of my chromecasts as the media player it fails to play and I simply get the generic blue stream logo.
If I look at the current state of that media player entity - I can see that the media URL that has been sent is http://192.168.1.241/api/hls/xxxx/master_playlist.m3u8
is this correct ? - Surely the URL should be either http://192.168.1.241:8123/ or https://xxxx.duckdns.org/ ?
1 post - 1 participant
Hi all,
I recently installed an ESP8266 using ESPHome to allow me to open my garage door remotely. To determine state I’m looking at status electronically using two GPIOs that are connected to the garage door controller board.
Part of my trouble in working through the logic is:
The “Open” GPIO senses high when the door is open AND it also pulses at approx 1Hz when the door is opening.
The “Closed” GPIO senses high when the door is closed AND it also pulses at approx 1Hz when the door is closing.
I’ve created a button that will toggle the OCS relay and this works nicely, as does the status when the door is closed. The trouble with the status is that when the door opens, the status goes “open/closed/open/closed…” for the duration that the door is opening. Not really ideal.
In my mind I think I need a sensor template that somehow ignores the pulsing and instead reads the final state from each GPIO to determine the actual open/closed state.
Tricky? I’m struggling to get my head around it and seek some wiser council 
As a follow-on, I wish to integrate with HomeKit (which I’ve done by way of a test cover already) however its only able to trigger the door at this stage as I’m unsure how to deal with status (see above).
Heres the relevant ESPhome config so far:
switch:
- platform: gpio
id: relay
pin:
number: D5
inverted: True
restore_mode: ALWAYS_OFF
- platform: template
name: "Garage Door"
icon: "mdi:garage"
turn_on_action:
- switch.turn_on: relay
- delay: 1s
- switch.turn_off: relay
- platform: restart
name: 'Garage Door REBOOT'
binary_sensor:
- platform: gpio
pin: D7
name: "Garage Door Open"
device_class: garage_door
- platform: gpio
pin: D8
name: "Garage Door Closed"
device_class: garage_door
1 post - 1 participant
Device trackers always showing not_home despite being used and should be showing home. This used to work but something has changed. The only ones that work are the ones I use in the Person entity.
How do I get old behaviour back?
1 post - 1 participant
Hello!
Is it possible (or…how?) to copy an existing built in lovelace card just to make a few minor changes?
Example: I use the generic_thermostat platform to control a dumb dehumidifier using a sonoff switch with humidity and temp sensor (Sonoff TH16). This works great! Just set the ‘ac_mode: true’ and heater: and target_sensor to the TH16.
I can display the thermostat control with the built in lovelace card, but I’d like to be able to customize it to display On / Off instead of Cooling / Idel and % instead of °F, and update the icon.
Am I thinking correct that this should be the easiest way?
Thanks!
1 post - 1 participant
I’m setting up a fresh install of HassOS using the qcow2 image running on KVM. Just booted into it. Seems to have already updated itself to v117, that’s cool. When I click into Supervisor, it’s kindly offering to update the Operating System from v4.15 to “null”. It says “Are you sure you want to update the Operating System to version null” ? That doesn’t feel good… Any ideas on what I should look for ?
1 post - 1 participant
Hi, I have the SONOFF integration manually added in my yaml
sonoff:
username: xxxxxx@xxx.xxx
password: nunofyerbiznizz
was working fine and now its not. I have created a guest account and tried that, still nada, what gives?
1 post - 1 participant
I’m getting this notification-
The following integrations and platforms could not be set up:
home
Please check your config and logs.
Log-
2020-11-02 20:45:17 ERROR (MainThread) [homeassistant.setup] Setup failed for home: Integration not found.
2020-11-02 20:45:23 ERROR (SyncWorker_0) [homeassistant.components.homekit.util] media_player.plex_mrmc_atv4klr does not support any media_player features
2020-11-02 20:45:24 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 128, in async_init
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py", line 107, in async_step_zeroconf
uuid = discovery_info["properties"]["uuid"]
KeyError: 'uuid'
configuration.yaml-
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Text to speech
tts:
- platform: google_translate
# Includes
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
home assistant:
customize: !include customize.yaml
sensor:
# World Clock
- platform: worldclock
time_zone: America/New_York
alarm_control_panel:
# Alarm Control Panel Manual
- platform: manual
name: shop alarm
code_arm_required: false
code: '1234'
arming_time: 0
delay_time: 0
trigger_time: 4
disarmed:
trigger_time: 0
armed_home:
arming_time: 0
delay_time: 0
notify:
# Email notification
- name: send_email
platform: smtp
server: smtp.gmail.com
port: 587
timeout: 15
sender: walterstarksjr@gmail.com
encryption: starttls
username: walterstarksjr@gmail.com
password: umxsgjhicstelzhv
recipient:
- walterstarks@icloud.com
sender_name: Home Assistant
# Prowl notification
- name: prowl
platform: prowl
api_key: 7291d42ee46a66ae702dff515ec65afdb1f69040
I don’t have any idea what this means or how to fix it.
3 posts - 2 participants
Hi, i’ve noticed that my deconz appears to completely crash after a couple of days operation. a complete reboot (well, at that point, yanking the power cable) helps to restore functionality.
so i attempted to create a simple automation so i don’t have to manually restart my raspberry pi when it happens:
shell_command:
reboot_host: ha host reboot
with an automation like:
- alias: Reboot HASS
trigger:
- platform: time
at: "19:00:00"
action:
- service: shell_command.reboot_host
It triggers fine, however, the follow error shows up in the logs:
Logger: homeassistant.components.shell_command
Source: /usr/src/homeassistant/homeassistant/components/shell_command/__init__.py:111
Integration: Shell Command (documentation, issues)
First occurred: 19:00:00 (1 occurrences)
Last logged: 19:00:00
Error running command: `ha host reboot`, return code: 127
NoneType: None
what is the correct command i should use to reboot the entire raspberry pi?
cheers!
1 post - 1 participant
I’ve been thinking about a “simple” method for building a whole home audio system that wouldn’t tie me into any particular vendor’s products.
I have six audio zones in my home, driven by two Dayton Audio MA1240a amplifiers, and have a separate Apple Airport Express connected to each zone. I then use Airfoil from Rogue Amoeba to enable each zone, set volume, and play content. The system worked fine, but some of the Airport devices are starting to fail, and I would like to come up with another way to do this.
First off, let me say that I’m not interested in different audio sources for my indoor zones. My goal is to play something from my Volumio server and then simply enable or disable a zone. I think I can pull that off pretty easily with an ESP32 and some inexpressive relays (see diagram below), and then can enable/disable a zone from within Home Assistant. What this doesn’t give me, however, is volume control. Any ideas on how I can do this and make it accessible via Home Assistant?
1 post - 1 participant
So it’s my rental house and I had to ask my tenant to ship the RP to me which took a few days and then even more to move everything to a lenovo desktop etc.
Now, they received everything back and all nodes show as unavailable. I have no idea why but here are some clues:
Zwave log:
2020-11-02 22:32:00.563 Always, OpenZwave Version 1.4.3469 Starting Up
2020-11-02 22:32:02.914 Info, Setting Up Provided Network Key for Secure Communications
2020-11-02 22:32:02.915 Info, mgr, Added driver for controller /dev/serial/by-id/usb-0658_0200-if00
2020-11-02 22:32:02.915 Info, Opening controller /dev/serial/by-id/usb-0658_0200-if00
2020-11-02 22:32:02.915 Info, Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1)
2020-11-02 22:32:02.941 Info, Serial port /dev/serial/by-id/usb-0658_0200-if00 opened (attempt 1)
2020-11-02 22:32:02.941 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-11-02 22:32:02.941 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-11-02 22:32:02.941 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-11-02 22:32:02.941 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-11-02 22:32:02.941 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-11-02 22:32:02.941 Detail,
2020-11-02 22:32:02.942 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-11-02 22:32:02.950 Detail, contrlr, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x34, 0x2e, 0x35, 0x34, 0x00, 0x01, 0x93
2020-11-02 22:32:02.950 Detail,
2020-11-02 22:32:02.950 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2020-11-02 22:32:02.950 Info, contrlr, Static Controller library, version Z-Wave 4.54
2020-11-02 22:32:02.950 Detail, Node045, Expected reply was received
2020-11-02 22:32:02.950 Detail, Node045, Message transaction complete
2020-11-02 22:32:02.950 Detail,
2020-11-02 22:32:02.950 Detail, contrlr, Removing current message
2020-11-02 22:32:02.950 Detail,
2020-11-02 22:32:02.950 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-11-02 22:32:02.957 Detail, contrlr, Received: 0x01, 0x08, 0x01, 0x20, 0xd3, 0x61, 0x89, 0xe3, 0x01, 0x0f
2020-11-02 22:32:02.957 Detail,
2020-11-02 22:32:02.957 Info, contrlr, Received reply to FUNC_ID_ZW_MEMORY_GET_ID. Home ID = 0xd36189e3. Our node ID = 1
2020-11-02 22:32:02.957 Detail, Node097, Expected reply was received
2020-11-02 22:32:02.957 Detail, Node097, Message transaction complete
2020-11-02 22:32:02.957 Detail,
2020-11-02 22:32:02.957 Detail, contrlr, Removing current message
2020-11-02 22:32:02.957 Detail,
2020-11-02 22:32:02.957 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-11-02 22:32:02.964 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x05, 0x28, 0xd7
2020-11-02 22:32:02.964 Detail,
2020-11-02 22:32:02.965 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2020-11-02 22:32:02.965 Info, contrlr, There is no SUC ID Server (SIS) in this network.
2020-11-02 22:32:02.965 Info, contrlr, The PC controller is a primary controller.
2020-11-02 22:32:02.965 Detail, Node215, Expected reply was received
2020-11-02 22:32:02.965 Detail, Node215, Message transaction complete
2020-11-02 22:32:02.965 Detail,
2020-11-02 22:32:02.965 Detail, contrlr, Removing current message
2020-11-02 22:32:02.965 Detail,
2020-11-02 22:32:02.965 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-11-02 22:32:02.974 Detail, contrlr, Received: 0x01, 0x2b, 0x01, 0x07, 0x01, 0x01, 0x00, 0x86, 0x01, 0x01, 0x00, 0x5a, 0xfe, 0x81, 0xff, 0x88, 0x4f, 0x1f, 0x00, 0x00, 0xfb, 0x9f, 0x7d, 0xa0, 0x67, 0x00, 0x00, 0x80, 0x00, 0x80, 0x86, 0x00, 0x00, 0x00, 0xe8, 0x73, 0x00, 0x00, 0x0e, 0x00, 0x00, 0x60, 0x00, 0x00, 0xfb
2020-11-02 22:32:02.974 Detail,
2020-11-02 22:32:02.974 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES
2020-11-02 22:32:02.975 Info, contrlr, Serial API Version: 1.1
2020-11-02 22:32:02.975 Info, contrlr, Manufacturer ID: 0x0086
2020-11-02 22:32:02.975 Info, contrlr, Product Type: 0x0101
2020-11-02 22:32:02.975 Info, contrlr, Product ID: 0x005a
2020-11-02 22:32:02.975 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2020-11-02 22:32:02.975 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2020-11-02 22:32:02.975 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2020-11-02 22:32:02.975 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2020-11-02 22:32:02.975 Detail, Node001, Expected reply was received
2020-11-02 22:32:02.975 Detail, Node001, Message transaction complete
2020-11-02 22:32:02.975 Detail,
2020-11-02 22:32:02.975 Detail, contrlr, Removing current message
2020-11-02 22:32:02.975 Detail,
2020-11-02 22:32:02.975 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-11-02 22:32:02.982 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x56, 0x00, 0xac
2020-11-02 22:32:02.982 Detail,
2020-11-02 22:32:02.982 Info, contrlr, Received reply to GET_SUC_NODE_ID. Node ID = 0
2020-11-02 22:32:02.982 Info, Controller Does not Support SUC - Cannot Setup Controller as SUC Node
2020-11-02 22:32:02.982 Detail, Node172, Expected reply was received
2020-11-02 22:32:02.982 Detail, Node172, Message transaction complete
2020-11-02 22:32:02.982 Detail,
2020-11-02 22:32:02.982 Detail, contrlr, Removing current message
2020-11-02 22:32:02.982 Detail,
2020-11-02 22:32:02.982 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x1c) - FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2020-11-02 22:32:03.044 Detail, contrlr, Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0xd0, 0x35, 0xfd, 0x66, 0xf5, 0x80, 0xac, 0xe5, 0xeb, 0xd4, 0xe2, 0xa1, 0x25, 0x89, 0xb8, 0x17, 0x41, 0x48, 0xf4, 0x26, 0x71, 0xfa, 0xec, 0x09, 0x73, 0xda, 0x5b, 0xe7, 0x2b, 0x59, 0x30, 0x1b, 0x22
2020-11-02 22:32:03.044 Detail,
2020-11-02 22:32:03.044 Info, contrlr, Received reply to FUNC_ID_ZW_GET_RANDOM: true
2020-11-02 22:32:03.044 Detail, Node032, Expected reply was received
2020-11-02 22:32:03.044 Detail, Node032, Message transaction complete
2020-11-02 22:32:03.044 Detail,
2020-11-02 22:32:03.044 Detail, contrlr, Removing current message
2020-11-02 22:32:03.044 Detail,
2020-11-02 22:32:03.044 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x02) - FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2020-11-02 22:32:03.154 Detail, contrlr, Received: 0x01, 0x25, 0x01, 0x02, 0x05, 0x00, 0x1d, 0x01, 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, 0xc5
2020-11-02 22:32:03.154 Detail,
2020-11-02 22:32:03.154 Info, mgr, Driver with Home ID of 0xd36189e3 is now ready.
2020-11-02 22:32:03.154 Info,
2020-11-02 22:32:03.155 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_INIT_DATA:
2020-11-02 22:32:03.155 Info, contrlr, Node 001 - Known
2020-11-02 22:32:03.155 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=CacheLoad live=1
2020-11-02 22:32:03.155 Detail, Node001, QueryStage_CacheLoad
2020-11-02 22:32:03.155 Info, Node001, Node Identity Codes: 0086:0101:005a
2020-11-02 22:32:03.155 Detail, Node001, QueryStage_Associations
2020-11-02 22:32:03.155 Detail, Node001, QueryStage_Neighbors
2020-11-02 22:32:03.155 Detail, contrlr, Requesting routing info (neighbor list) for Node 1
2020-11-02 22:32:03.155 Detail, Node001, Queuing (Command) Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
2020-11-02 22:32:03.155 Detail, Node001, Queuing (Query) Query Stage Complete (Neighbors)
2020-11-02 22:32:03.156 Detail, Expected reply was received
2020-11-02 22:32:03.156 Detail, Message transaction complete
2020-11-02 22:32:03.156 Detail,
2020-11-02 22:32:03.156 Detail, contrlr, Removing current message
2020-11-02 22:32:03.156 Detail, Node001, Notification: DriverReady
2020-11-02 22:32:03.166 Detail, Node001, Notification: NodeAdded
2020-11-02 22:32:03.177 Detail, Node001, Notification: NodeProtocolInfo
2020-11-02 22:32:03.184 Detail, Node001, Notification: EssentialNodeQueriesComplete
2020-11-02 22:32:03.190 Detail, Node001, Notification: ValueAdded
2020-11-02 22:32:03.201 Detail, Node001, Notification: NodeNaming
2020-11-02 22:32:03.207 Detail,
2020-11-02 22:32:03.207 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-11-02 22:32:03.212 Detail, contrlr, Received: 0x01, 0x05, 0x01, 0x06, 0x64, 0x0f, 0x96
2020-11-02 22:32:03.212 Detail,
2020-11-02 22:32:03.212 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_SET_TIMEOUTS
2020-11-02 22:32:03.212 Detail, Node015, Expected reply was received
2020-11-02 22:32:03.212 Detail, Node015, Message transaction complete
2020-11-02 22:32:03.212 Detail,
2020-11-02 22:32:03.212 Detail, contrlr, Removing current message
2020-11-02 22:32:03.212 Detail,
2020-11-02 22:32:03.212 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-11-02 22:32:03.217 Detail, contrlr, Removing current message
2020-11-02 22:32:03.217 Detail,
2020-11-02 22:32:03.217 Info, Node001, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
2020-11-02 22:32:03.227 Detail, Node001, Received: 0x01, 0x20, 0x01, 0x80, 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, 0x5e
2020-11-02 22:32:03.227 Detail,
2020-11-02 22:32:03.227 Info, Node001, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2020-11-02 22:32:03.227 Info, Node001, Neighbors of this node are:
2020-11-02 22:32:03.227 Info, Node001, (none reported)
2020-11-02 22:32:03.227 Detail, Expected reply was received
2020-11-02 22:32:03.228 Detail, Message transaction complete
2020-11-02 22:32:03.228 Detail,
2020-11-02 22:32:03.228 Detail, Node001, Removing current message
2020-11-02 22:32:03.228 Detail, Node001, Query Stage Complete (Neighbors)
2020-11-02 22:32:03.228 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2020-11-02 22:32:03.228 Detail, Node001, QueryStage_Session
2020-11-02 22:32:03.228 Detail, Node001, QueryStage_Dynamic
2020-11-02 22:32:03.228 Detail, Node001, QueryStage_Configuration
2020-11-02 22:32:03.228 Detail, Node001, QueryStage_Complete
2020-11-02 22:32:03.228 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2020-11-02 22:32:03.228 Warning, CheckCompletedNodeQueries all=1, deadFound=0 sleepingOnly=1
2020-11-02 22:32:03.228 Info, Node query processing complete.
2020-11-02 22:32:03.228 Detail, Node001, Notification: NodeQueriesComplete
2020-11-02 22:32:03.234 Detail, contrlr, Notification: AllNodesQueried
2 posts - 1 participant