@chris669 wrote:

I was wondering if there was a way to create a new lovelace page interface (with a dedicated url), but with keeping the auto-generated page. Because, when I add a new device, I want to check it first in de default view.

Posts: 1

Participants: 1

Read full topic

@tmjpugh wrote:

I previously factory reset zwave controller and all devices and repaired with HA

I recently realized that many devices have retained prior friendly_name. This means, HA default for friendly_name(greyed out) is “bedroom” instead of null. This name shows in frontend.

If I change frienfky_name it has no affect. So friendly_name defined as “kitchen” but frontend still show"bedroom"
I look in device_registry and entity_registry and friendly_name show null. I check other files and do not find any name defined.

Any suggestions?

Posts: 1

Participants: 1

Read full topic

@freekode wrote:

Hi,

I have input_datetime.bedtime for time.

My automation

- alias: Bed Time Automation
  trigger:
    platform: template
    value_template: "{{ now().strftime('%H:%M:%S') == states('input_datetime.bed_time') }}"
  action:
    - service: script.going_sleep

In dev tools I checked values:

{{ now().strftime('%H:%M:%S') # 16:32:00 }}
{{ states('input_datetime.bed_time') # 16:34:00 }}

So they looks the same, and my question, why automation doesn’t trigger at all?

Posts: 4

Participants: 3

Read full topic

@rlongfield wrote:

Not sure even how to figure this out.

Running HA 100.3 in Docker and everything was running well until I did a server restart for a few changes I made in my snips_intent.yaml, automations.yaml, and ui_lovelave.yaml files.

After clicking the Restart option HA refuses to start and the home-assistant.log files has 1131 lines of errors like below (This is the end of the log file)

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 190, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/openuv/__init__.py", line 189, in async_setup_entry
    await openuv.async_update()
  File "/usr/src/homeassistant/homeassistant/components/openuv/__init__.py", line 281, in async_update
    await asyncio.gather(*tasks)
concurrent.futures._base.CancelledError
2019-10-29 11:31:29 ERROR (SyncWorker_3) [concurrent.futures] exception calling callback for <Future at 0x7fe629352c10 state=finished raised RuntimeError>
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/aurora/binary_sensor.py", line 53, in setup_platform
    add_entities([AuroraSensor(aurora_data, name)], True)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 200, in _schedule_add_entities
    update_before_add,
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 77, in run_callback_threadsafe
    loop.call_soon_threadsafe(run_callback)
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 728, in call_soon_threadsafe
    self._check_closed()
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 475, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 324, in _invoke_callbacks
    callback(self)
  File "/usr/local/lib/python3.7/asyncio/futures.py", line 362, in _call_set_state
    dest_loop.call_soon_threadsafe(_set_state, destination, source)
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 728, in call_soon_threadsafe
    self._check_closed()
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 475, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

I reversed the additions I made to the files above and I’ve restarted the Docker container with no change.

Posts: 2

Participants: 1

Read full topic

@zdenek.lipensky wrote:

On my end of configuration Yaml I set:

device_sun_light_trigger: 
  device_group: group.myroom

This I interprets as the if any member of group.myroom is available it will trigger the component.

In groups.yaml I have:

anybodyhome:
  name: anybodyhome
  entities:
   - person.zdenek
   - person.radka
   - person.michal
  
myroom:
  name: myroom
  entities:
   - person.zdenek
   - person.radka

Why the component triggers even when nobody from group myroom is at “home” state please?

Posts: 1

Participants: 1

Read full topic

@sirfalo wrote:

Hi

I have small problem which I can’t find out how to solve.
I made template sensor to recalculate PM2.5 value to have as percentage.
sensor.air_quality_pm25 is my sensor

So I made this:

   - platform: template
     sensors:
       in_pollution_perc:
         value_template: "{{(((states.sensor.air_quality_pm25.state|round)/25)*100)|round|int}}"
         friendly_name: "In PM2.5 %"
         unit_of_measurement: "%"

And it’s working, but out come is something like 32.0% or 40.0000000000001%, but when I was testing SAME template value

 {{(((states.sensor.air_quality_pm25.state|round)/25)*100)|round|int}}

, then it was just INTEGER (32% or 40%).

Any ideas?

Posts: 11

Participants: 5

Read full topic

@qhealy wrote:

Hi,

I have home assistant (raspberry pi hassio with HA 0.100.3) communicating with RfLink (Arduino megae + Espeasy ser2net bridge over wifi) and the sensors setup. All is fine, until rflink is restarted. At this point home assistant doesn’t seem to be able to recover the connections to rflink. To get it working, i need to restart Home Assistant. It seems a bit flakey and would prefer if HA would attempt to reconnect once it’s discovered there is an issue.

HA Configuration:

rflink:
  host: 192.168.1.22
  port: 5747

Posts: 1

Participants: 1

Read full topic

@Maschbaer wrote:

After a long way I was able to set-up Home Assistant on my Raspberry Pi with Raspbian lite Stretch. Therefore, I used the python virtual environment. It now starts up with no issued as far as I can see when using command and I can access it via the webinterface:

sudo systemctl status home-assistant@pi -l

home-assistant@pi.service - Home Assistant
   Loaded: loaded (/etc/systemd/system/home-assistant@pi.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-10-29 22:30:22 CET; 15min ago
 Main PID: 601 (hass)
    Tasks: 30 (limit: 4915)
   CGroup: /system.slice/system-home\x2dassistant.slice/home-assistant@pi.service
           └─601 /srv/homeassistant/bin/python /srv/homeassistant/bin/hass -c /home/pi/.homeassistant

Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_17) [homeassistant.loader] Loaded deconz from homeassistant.components.deconz
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_18) [homeassistant.loader] Loaded notion from homeassistant.components.notion
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_12) [homeassistant.loader] Loaded geonetnz_quakes from homeassistant.components.geonetnz_quakes
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_7) [homeassistant.loader] Loaded toon from homeassistant.components.toon
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_3) [homeassistant.loader] Loaded heos from homeassistant.components.heos
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_13) [homeassistant.loader] Loaded lifx from homeassistant.components.lifx
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_15) [homeassistant.loader] Loaded unifi from homeassistant.components.unifi
Oct 29 22:31:25 raspberrypi hass[601]: 2019-10-29 22:31:25 INFO (SyncWorker_2) [homeassistant.loader] Loaded twentemilieu from homeassistant.components.twentemilieu
Oct 29 22:31:26 raspberrypi hass[601]: 2019-10-29 22:31:26 INFO (SyncWorker_16) [homeassistant.loader] Loaded zha from homeassistant.components.zha
Oct 29 22:31:26 raspberrypi hass[601]: 2019-10-29 22:31:26 INFO (SyncWorker_4) [homeassistant.loader] Loaded hue from homeassistant.components.hue

Next, I started to set-up Zehnder and Tahoma and therefor I changed my configuration.yaml as follows:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

comfoconnect:
  host: 192.168.2.30

tahoma:
  username: abc@icloud.com
  password: helloworld

However, they do not show up in the webinterface at “Configuration/Devices”.
Further, the “Notification” reports

Invalid config

The following components and platforms could not be set up:

• comfoconnect
• tahoma

Please check your config.

Any ideas what missed?
Thanks in advance for any help. I am lost at the moment.

Jan

Posts: 3

Participants: 2

Read full topic

@ianadd wrote:

Because light.toggle ignores color_name I can’t reset my coloured hue light with a toggle of my smart light switch. So, not wanting to produce a script for every switch, I’ve been trying to create a generalised script to do the job and am tearing my last remaining hair out. Can anyone see where I am going wrong, please. Or show me a better way !

test_toggle:
  alias: test light toggle
  sequence:
    - service: script.turn_on
      entity_id: script.light_toggle
      data:
        variables:
          lght: 'office'

light_toggle:
  alias: toggle light to white
  sequence:
    - service_template: script.light_toggle_{% if is_state("{{ 'light.' ~ lght }}" , 'off') %}on{% else %}off{% endif %}
      data_template:
        variables:
          thislight: "{{ lght }}"
      
light_toggle_on:
  alias: light_on
  sequence:
  - service: light.turn_on
    data_template:
      entity_id: "{{ 'light.' ~ thislight }}"
      color_name: white
      brightness: 255
light_toggle_off:
  alias: light_off
  sequence:
  - service: light.turn_off
    data_template:
      entity_id: "{{ 'light.' ~ thislight }}"

Posts: 3

Participants: 2

Read full topic

@Ricardo_Franco wrote:

Hi guys,

So a few days ago I installed Hacs in hass.io . After following all steps I got the community tab on the left sidebar and can access the respective page but the problem is both my Overview and Store subtabs are … empty !!

Following some other user topics which had the same issue, I tried to reload data (in my case I had to do it manually by pressing the button) but even after waiting a few hours nothing happens, it just gets stuck there forever and everything except the settings page remains empty .

Needless to say I already have restarted the server multiple times after . Reinstall also did not help !

Anyone ?

Posts: 8

Participants: 2

Read full topic

@FreelancerJ wrote:

Newbie here! First post and everything! Glad to join you wonderful folks!

The problem in a mouthful: I have the Z-Wave integration set up, but when I attempt to include a device, nothing happens. The one device that seems to have communicated with the RazBerry seems to have failed to provide any info in the interview.

Let’s go into more depth, so I can provide some more helpful info about what I’ve done so far

So where I’m at: I’ve set up a Raspberry Pi 4 with Home Assistant, using the alternate install method to get it up and running in Raspian, and HASSio is running happily in it’s docker. It even controls my Daikin without me needing to code, I’m impressed!

I’m up to trying to get my RazBerry Z-Wave Board running using the built in Integration.
I was previously using the RazBerry with the Z-Way software on a Raspberry Pi 3 with no issue, but the location left a bit to be desired (the Pi 3 is also my DNS host among other things and sits with the router at one end of the house) for coverage, and I wanted to have it more central, hence the Pi 4.
I excluded my Z-Wave devices and factory reset the RazBerry before moving it to the new Pi.

I’ve added dtoverlay=pi3-disable-bt to my /boot/config.txt, ran sudo systemctl disable hciuart and enabled the serial interface using the raspi-config tool. I’ve also purged modemmanager via apt-get

The Razberry shows up in HomeAssistant, and displays the following:

RazBerry Info

node id: 1
node name: Z-Wave.Me RaZberry Controller 2016 ZWave+
manufacturer name: Z-Wave.Me
product name: RaZberry Controller 2016 ZWave+
query stage: Complete
is awake: true
is ready: true
is failed: false
is info received: false
max baud rate: 40000
is zwave plus: false
capabilities: listening, staticUpdateController, beaming, primaryController, routing
neighbors: 2
sentCnt: 2
sentFailed: 0
retries: 0
receivedCnt: 0
receivedDups: 0
receivedUnsolicited: 0
sentTS: 2019-10-30 12:16:59:241
receivedTS: 2019-10-30 12:16:59:184
lastRequestRTT: 0
averageRequestRTT: 0
lastResponseRTT: 0
averageResponseRTT: 0

I’ve added the Z-Wave entry in my configuration.yaml, as well as linked to a network key I’ve stored in a secrets.yaml file.

I was able to get inclusion working for one device, sort of.
At first, when I hit include in the Z-Wave control panel in Home Assistant, nothing would seem to happen. The device I was trying to pair, a ZXT-120, is battery powered so I was timing pressing it’s button to include immediately after pressing include on HASS. I would press it, give the two a minute for interview, and then restart HASS.
After the third or forth time of this, a second Z-Wave entity pops up, as “Unknown Node 2” and nothing really useful

Unknown Node 2 info

node id: 2
node name: Unknown Node 2
manufacturer name: 
product name: 
query stage: Complete
is awake: true
is ready: true
is failed: false
is info received: false
max baud rate: 40000
is zwave plus: false
capabilities: beaming, frequent, routing
sentCnt: 12
sentFailed: 0
retries: 1
receivedCnt: 0
receivedDups: 0
receivedUnsolicited: 0
sentTS: 2019-10-30 12:17:27:240
receivedTS: 2019-10-30 12:16:59:184
lastRequestRTT: 0
averageRequestRTT: 0
lastResponseRTT: 0
averageResponseRTT: 0
application version: Unknown

Selecting “Refresh Node” doesn’t change the detail there, including if I refresh it, wait two minutes and then restart HASS, or Raspian. Here is the output in OZW Log when I try to refresh

OZW_Log when refreshing

2019-10-30 12:32:28.663 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=ProtocolInfo live=1
2019-10-30 12:32:28.663 Detail, Node002, QueryStage_Probe
2019-10-30 12:32:28.663 Info, Node002, NoOperation::Set - Routing=true
2019-10-30 12:32:28.664 Detail, Node002, Queuing (NoOp) NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x12, 0xd2
2019-10-30 12:32:28.664 Detail, Node002, Queuing (Query) Query Stage Complete (Probe)
2019-10-30 12:32:28.664 Detail,
2019-10-30 12:32:28.664 Info, Node002, Sending (NoOp) message (Callback ID=0x12, Expected Reply=0x13) - NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x12, 0xd2
2019-10-30 12:32:29.664 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:29.665 Detail, Node002, Removing current message
2019-10-30 12:32:29.665 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:29.666 Detail, Node002, Query Stage Complete (Probe)
2019-10-30 12:32:29.666 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=WakeUp live=1
2019-10-30 12:32:29.666 Detail, Node002, QueryStage_WakeUp
2019-10-30 12:32:29.667 Detail, Node002, QueryStage_ManufacturerSpecific1
2019-10-30 12:32:29.667 Detail, Node002, Checking for ManufacturerSpecific CC and Requesting values if present on this node
2019-10-30 12:32:29.667 Detail, Node002, Queuing (Query) ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x13, 0xa5
2019-10-30 12:32:29.667 Detail, Node002, Queuing (Query) Query Stage Complete (ManufacturerSpecific1)
2019-10-30 12:32:29.667 Detail,
2019-10-30 12:32:29.667 Info, Node002, Sending (Query) message (Callback ID=0x13, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x13, 0xa5
2019-10-30 12:32:30.667 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:30.667 Detail, Node002, Removing current message
2019-10-30 12:32:30.667 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:30.669 Detail, Node002, Query Stage Complete (ManufacturerSpecific1)
2019-10-30 12:32:30.669 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodeInfo live=1
2019-10-30 12:32:30.669 Detail, Node002, QueryStage_NodeInfo
2019-10-30 12:32:30.669 Detail, Node002, Queuing (Query) Request Node Info (Node=2): 0x01, 0x04, 0x00, 0x60, 0x02, 0x99
2019-10-30 12:32:30.669 Detail, Node002, Queuing (Query) Query Stage Complete (NodeInfo)
2019-10-30 12:32:30.670 Detail,
2019-10-30 12:32:30.670 Info, Node002, Sending (Query) message (Callback ID=0x00, Expected Reply=0x49) - Request Node Info (Node=2): 0x01, 0x04, 0x00, 0x60, 0x02, 0x99
2019-10-30 12:32:31.670 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:31.670 Detail, Node002, Removing current message
2019-10-30 12:32:31.670 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:31.672 Detail, Node002, Query Stage Complete (NodeInfo)
2019-10-30 12:32:31.672 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodePlusInfo live=1
2019-10-30 12:32:31.672 Detail, Node002, QueryStage_NodePlusInfo
2019-10-30 12:32:31.672 Detail, Node002, QueryStage_SecurityReport
2019-10-30 12:32:31.672 Detail, Node002, QueryStage_ManufacturerSpecific2
2019-10-30 12:32:31.672 Detail, Node002, Queuing (Query) ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x14, 0xa2
2019-10-30 12:32:31.672 Detail, Node002, Queuing (Query) Query Stage Complete (ManufacturerSpecific2)
2019-10-30 12:32:31.672 Detail,
2019-10-30 12:32:31.672 Info, Node002, Sending (Query) message (Callback ID=0x14, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x14, 0xa2
2019-10-30 12:32:32.673 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:32.673 Detail, Node002, Removing current message
2019-10-30 12:32:32.673 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:32.674 Detail, Node002, Query Stage Complete (ManufacturerSpecific2)
2019-10-30 12:32:32.674 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Versions live=1
2019-10-30 12:32:32.674 Detail, Node002, QueryStage_Versions
2019-10-30 12:32:32.674 Info, Node002, Requesting Versions
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_NO_OPERATION
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_BASIC
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_THERMOSTAT_MODE
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_THERMOSTAT_SETPOINT
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_MANUFACTURER_SPECIFIC
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_VERSION
2019-10-30 12:32:32.675 Detail, Node002, QueryStage_Instances
2019-10-30 12:32:32.675 Info, Node002, Essential node queries are complete
2019-10-30 12:32:32.675 Detail, Node002, QueryStage_Static
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) ThermostatModeCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x04, 0x25, 0x15, 0x91
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) ThermostatSetpointCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x43, 0x04, 0x25, 0x16, 0x91
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x17, 0xa1
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) VersionCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x86, 0x11, 0x25, 0x18, 0x4f
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) Query Stage Complete (Static)
2019-10-30 12:32:32.676 Detail, Node002, Notification: EssentialNodeQueriesComplete
2019-10-30 12:32:32.676 Detail,
2019-10-30 12:32:32.676 Info, Node002, Sending (Query) message (Callback ID=0x15, Expected Reply=0x04) - ThermostatModeCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x04, 0x25, 0x15, 0x91
2019-10-30 12:32:33.676 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:33.676 Detail, Node002, Removing current message
2019-10-30 12:32:33.676 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:33.678 Detail,
2019-10-30 12:32:33.678 Info, Node002, Sending (Query) message (Callback ID=0x16, Expected Reply=0x04) - ThermostatSetpointCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x43, 0x04, 0x25, 0x16, 0x91
2019-10-30 12:32:34.678 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:34.678 Detail, Node002, Removing current message
2019-10-30 12:32:34.679 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:34.680 Detail,
2019-10-30 12:32:34.680 Info, Node002, Sending (Query) message (Callback ID=0x17, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x17, 0xa1
2019-10-30 12:32:35.680 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:35.681 Detail, Node002, Removing current message
2019-10-30 12:32:35.681 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:35.682 Detail,
2019-10-30 12:32:35.682 Info, Node002, Sending (Query) message (Callback ID=0x18, Expected Reply=0x04) - VersionCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x86, 0x11, 0x25, 0x18, 0x4f
2019-10-30 12:32:36.683 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:36.683 Detail, Node002, Removing current message
2019-10-30 12:32:36.683 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:36.684 Detail, Node002, Query Stage Complete (Static)
2019-10-30 12:32:36.684 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Associations live=1
2019-10-30 12:32:36.684 Detail, Node002, QueryStage_Associations
2019-10-30 12:32:36.684 Detail, Node002, QueryStage_Neighbors
2019-10-30 12:32:36.685 Detail, Requesting routing info (neighbor list) for Node 2
2019-10-30 12:32:36.685 Detail, Node002, Queuing (Command) Get Routing Info (Node=2): 0x01, 0x07, 0x00, 0x80, 0x02, 0x00, 0x00, 0x03, 0x79
2019-10-30 12:32:36.685 Detail, Node002, Queuing (Query) Query Stage Complete (Neighbors)
2019-10-30 12:32:36.685 Detail,
2019-10-30 12:32:36.685 Info, Node002, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=2): 0x01, 0x07, 0x00, 0x80, 0x02, 0x00, 0x00, 0x03, 0x79
2019-10-30 12:32:37.685 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:37.685 Detail, Node002, Removing current message
2019-10-30 12:32:37.685 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:37.687 Detail, Node002, Query Stage Complete (Neighbors)
2019-10-30 12:32:37.687 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2019-10-30 12:32:37.687 Detail, Node002, QueryStage_Session
2019-10-30 12:32:37.687 Detail, Node002, QueryStage_Dynamic
2019-10-30 12:32:37.687 Detail, Node002, Queuing (Send) ThermostatModeCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x02, 0x25, 0x19, 0x9b
2019-10-30 12:32:37.687 Detail, Node002, Queuing (Query) Query Stage Complete (Dynamic)
2019-10-30 12:32:37.687 Detail,
2019-10-30 12:32:37.687 Info, Node002, Sending (Send) message (Callback ID=0x19, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x02, 0x25, 0x19, 0x9b
2019-10-30 12:32:38.688 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:38.688 Detail, Node002, Removing current message
2019-10-30 12:32:38.688 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:38.689 Detail, Node002, Query Stage Complete (Dynamic)
2019-10-30 12:32:38.689 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2019-10-30 12:32:38.690 Detail, Node002, QueryStage_Configuration
2019-10-30 12:32:38.690 Detail, Node002, QueryStage_Complete
2019-10-30 12:32:38.690 Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1
2019-10-30 12:32:38.690 Detail, Node002, Notification: NodeQueriesComplete

I’ve also tried to add a second device, a Aeotec Multisensor 6, to the Z-Wave network however I cannot get inclusion to work for it. The LED indicator pretty clearly shows the pattern for “Inclusion Failed”, according to its manual. The logging I’m getting is as follows.

OZW_Log when including Aeotec Multisensor

2019-10-30 12:40:52.878 Detail, Queuing (Controller) Add Device
2019-10-30 12:40:52.878 Info, Add Device
2019-10-30 12:40:52.878 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1a, 0x6b
2019-10-30 12:40:52.879 Detail, Notification: ControllerCommand - Starting
2019-10-30 12:40:52.880 Detail,
2019-10-30 12:40:52.880 Info, contrlr, Sending (Command) message (Callback ID=0x1a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1a, 0x6b
2019-10-30 12:40:53.881 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:40:53.881 Detail, contrlr, Removing current message
2019-10-30 12:40:53.881 Detail, contrlr, Notification: Notification - TimeOut
2019-10-30 12:40:53.881 Detail, Notification: ControllerCommand - Error - Failed

I don’t know if any of that hints to anyone what I’m getting wrong in all this, or any anyone has a similar setup that can walk me through how to get working.

This is a brand new installation as well, so I am not really opposed to blowing it away and starting again if I have to, but I feel like this will be something really simple I’m missing

Research I’ve done so far
Looking around the forums I’ve only found a few 2-3 year old posts about running Razberrys.
Most are getting stuck making HomeAssistant communicate with the board, rather than trouble including devices, so other than a cursory glance at their solutions to see if they had any steps to set up that I didn’t do, they don’t seem to apply.

Others were having trouble getting HomeAssistant to discover devices that were already paired to the board from previous software, which also doesn’t really apply. most were solved by starting the Z-Wave network over from scratch…

One thing I’ve seen mentioned a few times is installing python-openzwave.
Since I’m running HASS via Docker and not in a Python virtual environment, I figured this doesn’t really apply to me (yeah I know HASS is in python inside the docker).
The OZW_log indicates at the start that it is running OpenZwave Version 1.4.3440 so hopefully that’s right, otherwise I’m not sure I know how to fix it inside the Docker…

Thanks in advance for any insight, ideas and advice you guys have!

Posts: 1

Participants: 1

Read full topic

@Inrego wrote:

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

Posts: 1

Participants: 1

Read full topic

@pbcrunch wrote:

This seems like a question someone would have asked before, but I couldn’t come up with a good set of search terms.

Every page in my Home Assistant UI says the same thing on its browser tab: “Home Assistant”. This isn’t very descriptive, and is kind of a butt-pain when I have multiple tabs open for the regular interface, the states page, the templates page, etc.

Is there some option buried somewhere to get more descriptive browser title bars? Like “Home Assistant: Dev Tools” when I’m on the Developer Tools page or “Home Assistant: Family Room” when the Family Room Lovelace view is displayed?

Posts: 2

Participants: 2

Read full topic

@Pete wrote:

Hi All,

I have just purchased a Hue Go to use in a stairway where there is no power for a lamp.

I have configured it in Zigbee2Mqtt and can control it from Home Assistant.

BUT, it seems that after 2 hours it goes from standby mode to off and needs to be turned on via the button.

I’m thinking of setting up an automation to turn it on momentarily during the 2 hour period and turn it off again to avoid it powering itself off.

I’ve got a couple of questions though:

1. Is this the only way of maintaining contact with it, apart from it being plugged into a power point which is not available to me.
2. I’m assuming that this means it is permanently on standby, so wondering how this will affect battery life and the life of the light itself?
3. The light doesn’t give me a battery level, so wondering how to know when it should be recharged?

Thanks,
Pete

Posts: 1

Participants: 1

Read full topic

@ianadd wrote:

I want to keep a reasonably long-term record of some data that HA captures but don’t want the database getting huge for no good reason.

For example:
Looking at the ‘events’ table, my wife’s iphone is generating around 400 records per hour whilst she is fast asleep. I do want to track history of people in and out of home but not hundreds of records saying the same thing.

I am using device_tracker on ip from the router and bluetooth from Pi. I link both up to ‘person’ entity if they are family members.

I am also using iphonedetect: which may be part of the reason for lots of entries.

Are there any elegant solutions?

Posts: 3

Participants: 3

Read full topic

@Jonathanese wrote:

I have a climate component, and most of its interesting sensors are stored away as attributes rather than distinct entities.

If I wanted to, say, show the fan RPM attribute, I suppose I could create a template sensor, but that just seems redundant since the sensor is already there. Is there a shorthand method to skip the step of creating a template sensor just to read an attribute?

If this isn’t a thing yet, it would probably be pretty ideal if I had another namespace. For instance, climate.infinitive**.fan_rpm**

Posts: 2

Participants: 2

Read full topic

@Ricardo_Franco wrote:

So I was thinking that it would be cool to have the name of all the media streaming in Hass.io, be it Netflix, Kodi, etc .

Surprisingly I couldn’t find any info about this !

I know if it’s local media or a spotify stream you already get that , but what about online streams from platforms like the ones I mentioned ?

Surely there must be a way to get this integrated into hassio without that much hassle, either through adb commands or some app installed on the streaming platform (a Mi box in my case) that could fetch this data .

Ideally it would also get a picture (such as a cover from the tv show / movie / etc) from the media currently playing in any of those sources .

Anyone who can share their insights on this and how feasible it would be ?

Posts: 6

Participants: 2

Read full topic

@kazihaha wrote:

I’m the man successful created rf dimmer with slider in this topic.

But in homekit, It just show on/off, how can I show it as a dimmer in homekit?
Please show me some guides
Thanks for reading my post

Posts: 1

Participants: 1

Read full topic

@chris669 wrote:

Just trying to read meteo conditions based on a post I read. I try to read the ID provided there but these doesn’t seems to trigger. Below my code. I say over 4 the weather is bad and I turn on boolean.
Bad approach?

- id: '1111175202183'
  alias: Rain Start
  description: ''
  trigger:
  - entity_id: weather.homecr
    from: '5'
    platform: state
    to: '50'
  condition: []
  action:
  - data:
      entity_id: input_boolean.bad_weather
    service: input_boolean.turn_on

Posts: 4

Participants: 2

Read full topic

@Marcos_Martinez wrote:

Dear Team,

My Xiaomi HUB was working very good but recently it has packet loss during 1 hour a couple of times per day. See the picture below:

image.png1245×35 5.26 KB

I have changed the wifi router but same behaviour. I am pinging the Xiaomi HUB and when it stops answering to ping, other wifidevices are working fine, so I am sure it is the HUB.

I have tried to modify the wifi setting limiting it to the most basic protocols 54Mbps, but always the same.

Did someone have the same problem? Any ideas?

Thank you in advance!

Posts: 2

Participants: 2

Read full topic