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

Z-wave config problem - System gets wrong address to device

$
0
0

@G7B wrote:

EDIT: Seem to have solved it - read the next post for solution.

Do anyone have a clue on how to help a fresh smart home / HA-user?
Was expecting the learning curve to be steep - but have gotten to a problem I simply don’t see a way out of. My serach around the internet and this forum gives me different problems I’m not completely able to relate to mine.

I’m running Home Assistant under VMware ESXi. Installed from the image available on home-assistant.io/hassio/installation/.

I have inserted the Aeotec Z-wave stick into the back port of my Intel NUC. (Also have an RFXtrx inserted - but not a priority to get this to work at this moment.)

I have tried several times to get the Z-wave installed and working.

First time I added it to the configuration.yaml with the code:

zwave:
  usb_path: /dev/ttyACM0

And this resulted in this log entry in HA:

Logger: homeassistant.config_entries
First occured: 15:55:09 (1 occurences)
Last logged: 15:55:09

Error setting up entry Z-Wave for zwave

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 78, in __init__
    raise ZWaveException(u"Can't find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: "Zwave Generic Exception : Can't find device /dev/ttyAMA0 : ['NoneType: None\\n']"

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/zwave/__init__.py", line 369, in async_setup_entry
    config_path=config.get(CONF_CONFIG_PATH),
  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 81, in __init__
    raise ZWaveException(u"Error when retrieving device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: 'Zwave Generic Exception : Error when retrieving device /dev/ttyAMA0 : [\'Traceback (most recent call last):\\n\', \'  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 78, in __init__\\n    raise ZWaveException(u"Can\\\'t find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))\\n\', \'openzwave.object.ZWaveException: "Zwave Generic Exception : Can\\\'t find device /dev/ttyAMA0 : [\\\'NoneType: None\\\\\\\\n\\\']"\\n\']'

I have no idea on where it gets “/dev/ttyAMA0” from as I have not entered that anywhere.

So I deleted Z-wave from HA / integrations and from configuration.yaml .

Restarted. Added it again from HA / Integrations and typed in /dev/ttyACM0 as the USB address.
HA then automatically added this to configuration.yaml :

zwave:
  usb_path: /dev/ttyAMA0

And it gives this error



Logger: homeassistant.config_entries
First occured: 23:51:57 (1 occurences)
Last logged: 23:51:57

Error setting up entry Z-Wave (import from configuration.yaml) for zwave

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 78, in __init__
    raise ZWaveException(u"Can't find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: "Zwave Generic Exception : Can't find device /dev/ttyAMA0 : ['NoneType: None\\n']"

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/zwave/__init__.py", line 369, in async_setup_entry
    config_path=config.get(CONF_CONFIG_PATH),
  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 81, in __init__
    raise ZWaveException(u"Error when retrieving device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: 'Zwave Generic Exception : Error when retrieving device /dev/ttyAMA0 : [\'Traceback (most recent call last):\\n\', \'  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 78, in __init__\\n    raise ZWaveException(u"Can\\\'t find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))\\n\', \'openzwave.object.ZWaveException: "Zwave Generic Exception : Can\\\'t find device /dev/ttyAMA0 : [\\\'NoneType: None\\\\\\\\n\\\']"\\n\']'

Again I have no idea where HA gets ttyAMA0 from …

Some terminal output:

~ $ ha hardware info
audio: {}
disk: []
gpio: []
input:
- AT Translated Set 2 keyboard
- VMware VMware Virtual USB Mouse
- ImPS/2 Generic Wheel Mouse
- Power Button
serial:
- /dev/serial/by-id/usb-0658_0200-if00
- /dev/ttyS1
- /dev/ttyS3
- /dev/ttyACM0
- /dev/ttyUSB0
- /dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO44GD4F-if00-port0
- /dev/ttyS2
- /dev/ttyS0
~ $ ls -ltr /dev/tty*
crw-rw----    1 root     audio     188,   0 Mar 10  2020 /dev/ttyUSB0
crw-rw----    1 root     audio       4,  67 Mar 10  2020 /dev/ttyS3
crw-rw----    1 root     audio       4,  66 Mar 10  2020 /dev/ttyS2
crw-rw----    1 root     audio       4,  65 Mar 10  2020 /dev/ttyS1
crw-rw----    1 root     audio       4,  64 Mar 10  2020 /dev/ttyS0
crw-rw----    1 root     audio     166,   0 Mar 10  2020 /dev/ttyACM0
crw-rw-rw-    1 root     root        5,   0 Mar 10  2020 /dev/tty

In advance thanks for any help given :slight_smile:

Posts: 2

Participants: 1

Read full topic


Upgrade issue with Docker

$
0
0

@bucks7756 wrote:

Can anyone help with this error I’m getting when Home Assistant tries to start? This is occuring since trying to upgrade to the latest version with docker.

starting version 3.2.8
2020-03-10 15:57:17 ERROR (MainThread) [homeassistant.bootstrap] Unable to set up error log /config/home-assistant.log (access denied)
2020-03-10 15:57:17 INFO (MainThread) [homeassistant.bootstrap] Config directory: /config
2020-03-10 15:57:17 INFO (SyncWorker_0) [homeassistant.config] Upgrading configuration directory from 0.104.3 to 0.106.5
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 350, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 342, in main
    exit_code = asyncio.run(setup_and_run_hass(config_dir, args))
  File "/usr/local/lib/python3.7/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 583, in run_until_complete
    return future.result()
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 249, in setup_and_run_hass
    safe_mode=args.safe_mode,
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 80, in async_setup_hass
    await hass.async_add_executor_job(conf_util.process_ha_config_upgrade, hass)
  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/config.py", line 387, in process_ha_config_upgrade
    with open(version_path, "wt") as outp:
OSError: [Errno 30] Read-only file system: '/config/.HA_VERSION'

Posts: 2

Participants: 2

Read full topic

Turn switch off after X minuts based on input_number value

$
0
0

@Phill_Healey wrote:

I have a switch that I want to turn off after a given number of minutes. The number of minutes is set by an input slider. However it’s not switching off after the selected time.

Any ideas as to what I’m doing wrong?

automations.yaml

- alias: Niu Manual Charge
  initial_state: true
  trigger:
    platform: state
    entity_id: switch.41034600cc50e3d1cbd7
    to: 'on'
    for:
      minutes: "{{ states('input_number.niu_battery_manual') }}"
  condition:
    - condition: state
      entity_id: input_select.niu_charge_type
      state: 'Manual'
  action:
    service: switch.turn_off
    data:
      entity_id: switch.41034600cc50e3d1cbd7

configuration.yaml:

input_number:
  niu_battery_manual:
    name: Battery Manual Time
    min: 1
    max: 7
    step: 1
    icon: 'mdi:battery-unknown'

input_select:
  niu_charge_type:
    name: Niu Charging
    icon: 'mdi:ev-station'
    options:
      - Manual
      - Bike

Posts: 6

Participants: 3

Read full topic

Samba & HassOS not working on Windows 10

$
0
0

@Suggorath wrote:

Hi, two days I am struggling with the Samba Share addon, and still not work. I tryed connect to server with address in file explorer \\192.168.100.103\config but nothing happened. Already tryed change 128bit to 40-56bit encryption with same result. Samba v1 is manualy installed on Win 10.

Hardware
Raspberry Pi 4 Model B 2GB
PC - Windows 10 Pro 1909

HassOS

  • version: 3.12 - 32 bit
  • deployment: production
  • hostname: homeassistant

Home Assistant

  • version: 0.106.5

Samba Share

  • version - 9.0
  • samba config:
workgroup: HOME
username: Suggorath
password: hass
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes

Note: Already tryed “interface: eth0” without success.

  • samba log:
[21:30:42] INFO: Hostname: homeassistant
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user Suggorath.
nmbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface eth0 ip=192.168.100.103 bcast=192.168.100.255 netmask=255.255.255.0
making subnet name:192.168.100.103 Broadcast address:192.168.100.255 Subnet mask:255.255.255.0
making subnet name:172.30.32.1 Broadcast address:172.30.33.255 Subnet mask:255.255.254.0
making subnet name:172.17.0.1 Broadcast address:172.17.255.255 Subnet mask:255.255.0.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface eth0 ip=192.168.100.103 bcast=192.168.100.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
check_for_master_browser_fail: Forcing election on workgroup HOME subnet 172.17.0.1
check_for_master_browser_fail: Forcing election on workgroup HOME subnet 172.30.32.1
check_for_master_browser_fail: Forcing election on workgroup HOME subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
run_elections: >>> Won election for workgroup HOME on subnet 172.17.0.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
run_elections: >>> Won election for workgroup HOME on subnet 172.30.32.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
run_elections: >>> Won election for workgroup HOME on subnet 192.168.100.103 <<<
become_local_master_browser: Starting to become a master browser for workgroup HOME on subnet 192.168.100.103

System log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing... 
[19:34:03] INFO: Update udev informations
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
20-03-10 19:34:06 INFO (MainThread) [__main__] Initialize Supervisor setup
20-03-10 19:34:06 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 209
20-03-10 19:34:07 INFO (MainThread) [__main__] Setup Supervisor
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.services] Update service information
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.services] Reload local service hassos-apparmor.service
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-03-10 19:34:07 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-dns with version 1
20-03-10 19:34:07 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-audio with version 8
20-03-10 19:34:07 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-03-10 19:34:07 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-10 19:34:07 INFO (MainThread) [supervisor.audio] Start Audio plugin
20-03-10 19:34:07 INFO (SyncWorker_2) [supervisor.docker.interface] Clean hassio_audio application
20-03-10 19:34:07 INFO (SyncWorker_4) [supervisor.docker.interface] Clean hassio_dns application
20-03-10 19:34:09 INFO (SyncWorker_4) [supervisor.docker.dns] Start DNS homeassistant/armv7-hassio-dns with version 1 - 172.30.32.3
20-03-10 19:34:09 INFO (SyncWorker_2) [supervisor.docker.audio] Start Audio homeassistant/armv7-hassio-audio with version 8 - 172.30.32.4
20-03-10 19:34:09 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/raspberrypi4-homeassistant with version 0.106.5
20-03-10 19:34:09 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /
20-03-10 19:34:09 INFO (MainThread) [supervisor.hassos] Detect HassOS 3.12 / BootSlot A
20-03-10 19:34:09 INFO (SyncWorker_0) [supervisor.docker.hassos_cli] Found HassOS CLI homeassistant/armv7-hassio-cli with version 21
20-03-10 19:34:10 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-03-10 19:34:10 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-03-10 19:34:10 INFO (MainThread) [supervisor.store] Load add-ons from store: 64 all - 64 new - 0 remove
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Found 2 installed add-ons
20-03-10 19:34:10 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 4.7
20-03-10 19:34:10 INFO (SyncWorker_9) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-samba with version 9.0
20-03-10 19:34:10 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-03-10 19:34:10 INFO (MainThread) [supervisor.snapshots] Found 0 snapshot files
20-03-10 19:34:10 INFO (MainThread) [supervisor.discovery] Load 0 messages
20-03-10 19:34:10 INFO (MainThread) [supervisor.ingress] Load 2 ingress session
20-03-10 19:34:10 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 1
20-03-10 19:34:10 INFO (MainThread) [__main__] Run Supervisor
20-03-10 19:34:10 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-03-10 19:34:10 INFO (MainThread) [supervisor.utils.gdbus] Call de.pengutronix.rauc.Installer.Mark on /
20-03-10 19:34:10 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Phase 'system' start 0 add-ons
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Phase 'services' start 1 add-ons
20-03-10 19:34:11 INFO (SyncWorker_12) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-samba with version 9.0
20-03-10 19:34:16 INFO (SyncWorker_15) [supervisor.docker.interface] Start homeassistant/raspberrypi4-homeassistant
20-03-10 19:35:15 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-03-10 19:35:15 INFO (MainThread) [supervisor.addons] Phase 'application' start 1 add-ons
20-03-10 19:35:16 INFO (SyncWorker_3) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 4.7
20-03-10 19:35:21 INFO (MainThread) [supervisor.tasks] All core tasks are scheduled
20-03-10 19:35:21 INFO (MainThread) [supervisor.hwmon] Started Supervisor hardware monitor
20-03-10 19:35:21 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-03-10 19:35:21 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-10 19:35:21 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-10 19:35:21 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-03-10 19:35:22 INFO (MainThread) [supervisor.host.services] Update service information
20-03-10 19:35:22 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-10 19:35:22 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-10 19:35:22 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-10 19:35:22 INFO (MainThread) [supervisor.host.sound] Update PulseAudio informationSystem log

Posts: 4

Participants: 3

Read full topic

With a single Automation, how do you turn lights on between two set times and then the lights off?

$
0
0

@HellfireZA wrote:

Hey guys, so for about a year I’ve been running 2 separate automations below to turn my lights on and off between times and I’d very much like to simply that into a single automation. Can someone point me in the right direction as I can’t seem to find what I need by simply searching?

 - alias: Turn Downstairs Lights on Between 11:00 and 19:00 
    hide_entity: true
    trigger:
      - platform: homeassistant
        event: start
      - platform: time
        at: '11:00:00'
    condition:
    - condition: time
      after: '11:00:00'
      before: '19:00:00'
    action:
      - service: switch.turn_on
        entity_id: switch.lights_ds 
        
  - alias: Turn Downstairs Lights off Between 19:00 and 11:00
    hide_entity: true
    trigger:
      - platform: homeassistant
        event: start
      - platform: time
        at: '19:00:08'
    condition:
      condition: time
      before: '10:59:55'
      after: '19:00:05'
    action:
      - service: switch.turn_off
        entity_id: switch.lights_ds

Posts: 2

Participants: 2

Read full topic

Error during setup of component zeroconf

$
0
0

@belljaf wrote:

Hi, currently running HA core 0.106.5. For the last few updates I have been getting the following errors in my log on startup:

Error during setup of component zeroconf
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 174, in _async_setup_component
    component.setup, hass, processed_config  # type: ignore
  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/zeroconf/__init__.py", line 42, in setup
    zeroconf = Zeroconf()
  File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 2134, in __init__
    interfaces, unicast, ip_version, apple_p2p=apple_p2p
  File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 2062, in create_sockets
    respond_socket = add_multicast_member(cast(socket.socket, listen_socket), i, apple_p2p=apple_p2p)
  File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 2009, in add_multicast_member
    listen_socket.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, _value)
OSError: [Errno 105] No buffer space available

This is followed by the error that defaultconfig and ios could not setup all dependencies.

Every thing seems to be working as it should, in particular my ios integration is working so I don’t know if I need to worry about it but I dont like seeing errors in my log.

Any ideas?

Posts: 1

Participants: 1

Read full topic

Passing event data to a script via an automation

$
0
0

@sh00t2kill wrote:

Hi team.
Ive got a couple of threads up around the place RE this, but this is a more specific question.

At a high level, im trrying to curate a list of all current open flights over my house, using the opensky sensor.

If i manually call the script, via developer tools, i get a result on my remote endpoint.
The automation “works”, but im not getting the callsign sent over. Im sure im missing something simple, ive just been looking at it for too long!

Any ideas?

Script:

add_opensky_in:
  sequence:
  - service: rest_command.opensky_list
    data_template:
      payload: "{\n \"callsign\": \"{{ callsign }}\" \n}\n"

Automation:

- alias: Flight API
  trigger:
    platform: event
    event_type: opensky_entry
  action:
  - data:
      data_template:
        callsign: "{{trigger.event.data.callsign }}"
    service: script.add_opensky_in

Posts: 3

Participants: 2

Read full topic

View logged in users?


Thermostat in home assistant

Why isnt my MQTT sensor showing up in HA?

$
0
0

@giygas wrote:

here are the configuration and state messages observed by running mosquitto_sub to peek at mqtt traffic:

homeassistant/sensor/feeder_24hr_feeds/config {"unit_of_measurement": "", "state_topic": "homeassistant/sensor/feeder_24hr_feeds/state", "name": "Daily Feeds"}
homeassistant/sensor/feeder_24hr_feeds/state 13

and Home Assistant is receiving the messages, i see this in the logs:

2020-03-11 09:04:44 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor feeder_24hr_feeds

but no sensor ever actually appears under dev_state. any idea why?

Posts: 5

Participants: 2

Read full topic

Compare input_number value with sensor value

$
0
0

@Phill_Healey wrote:

I’m trying to create a binary sensor that switches on when a battery has a charge lower than that defined via an input_number. The battery value is reported via a sensor as a percentage.

Here’s what I’ve got so far, but this doesn’t work. I’m assuming it’s because the sensor.niu_battery is reported as a percentage.

- platform: template
  sensors:
    niu_end_charge:
      friendly_name: Niu End Charge
      value_template: "{{ states(input_number.niu_battery_max) | float < (sensor.niu_battery) | float }}"

Any ideas as to what I’m doing wrong? Suggestions for things to try?

Thanks.

Posts: 3

Participants: 2

Read full topic

Export Coordinates to CSV/KML format

$
0
0

@dmartinez7500 wrote:

Hey all,
I’m working on a project to keep daily travel logs for work, and I figured I could use the GPS data from my phone, that’s already in HA, to export it to a KML file. I know I can use my existing PHPMyAdmin add-on to export the data based on SQL queries to a CSV, then use a converter to parse it to KML.

I’ve tried creating templates for both lat and long, and combining them to a new device tracker, but the data is still parsed together, as below.

"state_id","domain","entity_id","state","attributes","event_id","last_changed","last_updated","created","context_id","context_user_id"
"20353","device_tracker","device_tracker.my_coords","home","{""source_type"": ""gps"", ""latitude"": 25.57806396484375, ""longitude"": -70.34037622778185, ""gps_accuracy"": 0, ""friendly_name"": ""my_coords""}","24393","2020-03-10 02:19:04","2020-03-10 02:19:04","2020-03-10 02:19:06","0fcb87b99c9e470ab30bffcc469f27f9",NULL
"21456","device_tracker","device_tracker.my_coords","home","{""source_type"": ""gps"", ""latitude"": 25.578079223632812, ""longitude"": -70.34044844154484, ""gps_accuracy"": 0, ""friendly_name"": ""my_coords""}","25563","2020-03-10 02:19:04","2020-03-10 04:27:11","2020-03-10 04:27:11","4f448ca194f6444797529545f6a47b2a",NULL
"21549","device_tracker","device_tracker.my_coords","home","{""source_type"": ""gps"", ""latitude"": 25.578018188476562, ""longitude"": -70.34038697199517, ""gps_accuracy"": 0, ""friendly_name"": ""my_coords""}","25658","2020-03-10 02:19:04","2020-03-10 04:37:51","2020-03-10 04:37:51","aba077ed94a54708a1eb854aff9b4a48",NULL

Is there any way to get this data properly formatted how I’d need it, or am I going about this in a overly complicated manner?

Posts: 2

Participants: 1

Read full topic

Plug-and-Play Remote Access

$
0
0

@ivelin wrote:

I’ve been using Home Assistant for about a year now. Needless to say, great potential!

One of the areas of friction for me has been remote access. Users currently have two options:

  1. Go through a non-trivial and often brittle setup with port-forwarding, TLS tunneling, and dynamic DNS.
  2. Use Nabu Casa Remote Access Cloud.

I think the latter is a completely reasonable way to make things simple for the end user and support the sustainability of the project.

However as the documentation states, there are a few quirks in the implementation that slightly contradict the core promise of user data privacy, because a cloud service sits in the middle of user data traffic. Although its encrypted end to end, there is a minimal risk of someone hacking into the server and mounting a man-in-the-middle attack.

So I’ve done some homework and I think I found a possible improvement. The gist of the proposed solution takes advantage of WebRTC DataChannel - a peer-to-peer communication API that has been long coming and finally all major browsers support.

I’ve been able to use this solution for a side project of mine for several weeks now with other users reporting good results. Here is a technical article published by WebRTCHacks:
https://webrtchacks.com/private-home-surveillance-with-the-webrtc-datachannel/

And a higher level overview blog:
https://blog.ambianic.ai/2020/02/05/pnp.html

If there is interest, I am happy to help with an implementation for Home Assistant Remote Access.

Ivelin

Posts: 3

Participants: 2

Read full topic

Automation. Trigger if sensor NOT updated AFTER input_boolean. Surely there's a better way than this!

$
0
0

@klogg wrote:

I have a really simple requirement so I probably can’t see the woods for the trees…

When an input_boolean changes state I need to be notified if a sensor doesn’t also change state after, but within, a very small (almost zero) number of seconds.

I have this which I can’t believe is the best way to achieve it (and to be honest I haven’t tested it anyway so it might not even work!)

What am I missing to make this better?

  - alias: Warning
    trigger: 
      - platform: state
        entity_id:
          - input_boolean.some_boolean
          - input_boolean.some_other_boolean

    action:
      - wait_template: >
          {{ as_timestamp(states.sensor.my_sensor.last_changed) - 
             as_timestamp(trigger.now) < 10 }}
        timeout:
          seconds: 12

      - condition: template >
          {{ as_timestamp(states.sensor.my_sensor.last_changed) - 
             as_timestamp(trigger.now) > 10 }}

      - service: notify.blah_blah

Posts: 3

Participants: 3

Read full topic

Condition wont work

$
0
0

@forted.exe wrote:

Here is my code, I want it to notify during 6am to 7pm. Remove condition, the code is run, but when I put condition back, it stop working.

  - alias: WPump Idle Warning
    trigger:
      - platform: state
        entity_id: switch.waterpump
        to: "off"
        for:
            minutes: 3
    condition:
        condition: time
        after: '06:00:00'
        before: '19:00:00'
    action:
      - service: notify.browsernotification
        data_template:
            message: "WARNING!!! WaterPump is OFF for 4hrs {{now().strftime('%H:%M:%S %d-%m-%Y')}}."

Posts: 6

Participants: 3

Read full topic


Check what is writing so many times to dB

$
0
0

@poudenes wrote:

Hi All,

Is there a way to check what device is writing so many data to dB?
I checked the recorder, history part but cant find it.

The led of SSD is blinking all the time…

Cheers,

Posts: 2

Participants: 2

Read full topic

Detect lost connection to Envisalink

$
0
0

@gunstr wrote:

The Envisalink integration works like a charm, but I have noticed that if I disconnect the Envisalink board from the LAN the only thing that happens in HA is that the status of the sensors freezes. I would like to detect and show if the connectivity is lost and ideally also send a notifation. There is a timeout variable, but I have not found any way to detect it has happened. Any suggestions how this could be done?

Posts: 1

Participants: 1

Read full topic

Weblink integration being deprecated

$
0
0

@rlongfield wrote:

I am getting this warning in my HA logs

The weblink integration has been deprecated and is pending for removal in Home Assistant 0.107.0. Please use this instead: https://www.home-assistant.io/lovelace/entities/#weblink

But when I go to that url I see the recommended format is:

type: entities
title: Entities card sample
show_header_toggle: true
entities:

And this is what is in my ui-lovelace.yaml file:

type: entities
entities:

Is this a mistake?

Posts: 2

Participants: 2

Read full topic

Mikrotik Device Tracking not working anymore

$
0
0

@nikolas22t wrote:

This is not working anymore and all devices connected to my router are added to device_tracker

Blockquote

device_tracker:

  • platform: mikrotik
    new_device_defaults:
    track_new_devices: false

Blockquote

i tried all options found on the internet but nothing seems to work, any idea?
What i want to do is to track only 2-3 devices via mikrotik router and ignore all other , even the file known_devices.yaml is empty

Posts: 1

Participants: 1

Read full topic

Combine two binary_sensors into one?

$
0
0

@Phill_Healey wrote:

I currently have two input_numbers that I want to use to determine when my battery charger should switch on. They look like this:

- platform: template
  sensors:
    niu_start_charge:
      friendly_name: Niu Start Charge
      value_template: "{{ states('input_number.niu_battery_min') | float > states('sensor.niu_battery') | float }}"
- platform: template
  sensors:
    niu_end_charge:
      friendly_name: Niu End Charge
      value_template: "{{ states('input_number.niu_battery_max') | float < states('sensor.niu_battery') | float }}"

niu_start_charge is on when the battery level is below the value input_number.niu_battery_min and niu_start_charge is on when the battery exceeds the value of input_number.niu_battery_max. sensor.niu_battery is the current charged level of the battery.

I can use these binary_sensors to establish when to start and stop the charging process but it requires two seperate automations. I’d like to be able to combine the two binary_sensors given above into just one, which only returns true when the battery level is below the minimum value and below the maximum level. But, it should not be on when it is above the minimum level even if that is below the maximum charge level.

So… Is there a way to combine those two binary_sensors into one? If so I’d appreciate a nudge in the right direction.

Thanks

Posts: 5

Participants: 3

Read full topic

Viewing all 108152 articles
Browse latest View live


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