@Canedje wrote:

Today I switched my netgear firmware to dd-rwt.
on my Netgear r8000
In de basics it worked out fine.
I’m only not possible to open HA anymore by Samba in the explorer.
The network device is vissible: but gives an access error.:

Knipsel775×188 26.8 KB

I did restart and reinstall Samba, no effect.
If I look in the Samba log I do see attemps for logging in:

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 eth0 ip=192.168.2.78 bcast=192.168.2.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
netbios connect: name1=HASSIO         0x20 name2=PC-EDWARDW8    0x0
netbios connect: local=hassio remote=pc-edwardw8, name type = 0
netbios connect: name1=HASSIO         0x20 name2=PC-EDWARDW8    0x0
netbios connect: local=hassio remote=pc-edwardw8, name type = 0
netbios connect: name1=HASSIO         0x20 name2=PC-EDWARDW8    0x0
netbios connect: local=hassio remote=pc-edwardw8, name type = 0
Could not find child 72 -- ignoring
netbios connect: name1=HASSIO         0x20 name2=PC-EDWARDW8    0x0
netbios connect: local=hassio remote=pc-edwardw8, name type = 0

I do have the feeling it is something to do with login credentials.
But I get no loggin prompt.
Any ideas?

Posts: 2

Participants: 2

Read full topic

@daveLeiser wrote:

Hello

I got a problem configuring my zigbee sensors in HA.

I have installed and configured mosquitto broker and zigbee2mqtt. I also already was able to pair some devices and i can see the states changing in the zigbee2mqtt log like this:
zigbee2mqtt:info 2020-04-11 12:25:43: MQTT publish: topic 'zigbee2mqtt/0x00158d0002e9d384', payload '{"contact":true,"linkquality":52,"battery":100,"voltage":3005}'

The problem now is that Homeassistant dont get any updates on the states of the devices. State is unknown when i check it under Settings -> Integrations -> MQTT:

MQTTProblem2299×864 98 KB

I now removed all configured zigbee sensors from the configuration.yaml file but this somehow changes nothing. I can still see all the sensors like in the picture above. Where do these devices get configured? Or am I mixing stuff up with the MQTT Integration of HA while i am also running mosquitto broker?

Hope somebody can clear this up as i am quite stuck here.

Thanks in advance!

Happ easter

Posts: 1

Participants: 1

Read full topic

@dsonenberg wrote:

I have several automations I would like to build that would control multiple lights, and I thought it would be best to use scenes to accomplish this. If i create this scene:

- name: BasementLightsOn
  entities:
    switch.basement_light_1:
      state: on
    switch.basement_light_2:
      state: on

and activate it by:

- alias: Turn on basement light when there is movement
  trigger:
    platform: state
    entity_id: binary_sensor.basement_motion_1_sensor
    to: 'on'
  action:
    service: scene.turn_on
    entity_id: scene.BasementLightsOn

Do i need to make a second scene to turn the lights off or can I simply use:

scene.turnoff

TIA

Posts: 2

Participants: 2

Read full topic

@ihavenoidea wrote:

I recently reinstalled HA onto my Pi4 yesterday and got it all setup and working. I also installed the “Terminal & SSH” addon so I can ssh into the Pi4 from my Mac. After getting it all setup, I confirmed it was working and even copied over my keys.

I’ve tried to login today and it appears I can no longer login via SSH, the connection is refused. Debugging the login attempt says the following:

OpenSSH_7.8p1, LibreSSL 2.6.2
debug1: Reading configuration data /Users/Account/.ssh/config
debug1: /Users/Account/.ssh/config line 9: Applying options for hassio
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: Connecting to 192.168.1.15 [192.168.1.15] port 22.
debug1: connect to address 192.168.1.15 port 22: Connection refused
ssh: connect to host 192.168.1.15 port 22: Connection refused

Looking at the addon doc it looks like external SSH access is no longer enabled by default (not sure how I accessed it yesterday without any issues). To enable this I need to setup the Network card, but I’m not sure exactly what to setup here. Heres what my Network config looks like

Posts: 2

Participants: 2

Read full topic

@casm wrote:

Hi there. I’m running into some difficulty with understanding what needs to happen in order to migrate existing NUT clients off of their existing monitoring server and into HA, and could use some assistance with the process.

First things first: HA is 0.108.2; remote UPS monitors are RasPi Zero Ws running NUT under Raspbian Stretch. The configuration on the RasPis has been in place for roughly 3 years and works reliably.

What I would like to happen is that these NUT clients either report their status in to HA or are polled for it. My understanding of how NUT works in HA seems to be hampering this, though.

So far, a NUT integration has been created in HA. It’s pointed at one of the NUT clients, from which it will successfully get whatever status info it has been configured to get. However, I’m not sure how to add in the other NUT clients - I can’t add another NUT integration since one already exists, and trying to use the alias field as suggested in the documentation hasn’t worked out.

Additionally, no UPS is directly attached to the VMWare ESXi box that HA runs on, so it’s not clear as to what should happen with the device configuration for NUT in HA. Config currently appears as follows:

users:
  - username: redacted
    password: redacted
    instcmds:
      - all
    actions:
      - set
devices:
  - name: myups
    driver: usbhid-ups
    port: auto
    config: []
mode: netserver
shutdown_host: 'false'

TIA for any assistance - the UPSes are actually a pretty big part of why we’re migrating from Domoticz to HA, and I’m really looking forward to getting this part of things up and running.

Posts: 1

Participants: 1

Read full topic

@ihavenoidea wrote:

I need to access the Config.txt file on my Host OS to make changes to the system fan speed but I’m struggling to try and connect to it.

The docs here state I need to ssh into port 22222, but I simply get a connection refused.

Can anyone advise how I can correctly connect to it?

Posts: 8

Participants: 3

Read full topic

@ihavenoidea wrote:

I am using the Synology integration to get my camera feeds into HA, which works. I can see all cameras, their states and even a live feed.

However I have noticed the live feeds are either delayed or frozen. I don’t actually view my streams through HA so that’s not a huge issue, my problem though is that I use HA on my iOS device to get Camera stills (via the Shortcuts app) and these aren’t the most real time because of this (sometimes brings back stills from 2+ hours ago).

How can I force the cameras to be updated more often? or at least when I query them get my the latest image?

Posts: 7

Participants: 3

Read full topic

@Juggler wrote:

I have segmented by home network (Ubiquiti) into multiple VLANs for proper isolation. HA is sitting on my “main” VLAN, while my Chromecasts are sitting on a VLAN I have called IoT. I am able to integrate the Chromecasts into HA by assigning them static IPs, however Chromecast groups are not accessible as there is no way to statically map them. I believe they are advertised via mDNS.

On my EdgeRouter, I have configured both the reflector and repeaters as follows:

service mdns reflector
service mdns repeater {
  interface eth0.20
  interface eht0.30
}

(eth0.20 and .30 are the virtual interfaces assigned to my main and IoT VLANs)

I am still not seeing any of the Chromecast groups. Has anyone been able to get this working?

Posts: 1

Participants: 1

Read full topic

@Giuseppe-P wrote:

I have an esp32 cam with arduino sketch … I inserted the cam in the home assistant with the card Pictures but I only see the cam when I am under the local network in HA … While if I access HA remotely with a private IP address it does not I see nothing … How come since the flow is still local?

Posts: 1

Participants: 1

Read full topic

@jedi87pl wrote:

Hi Community
I’m using manually added yeelight bulbs and lighstrip. I can’t add them via autodiscover since they are in different VLAN (Or maybe i can but i don’t know how? Any help? ) so they are manually configured.

They appear in Entities list but they are not in Device list. Because of that, i think, i can’t use them in front end creators for scenes or automations. Is there anyway to do that? To add them as devices not entities? Or make entitites avaible in automations and scene creators?

Posts: 1

Participants: 1

Read full topic

@DeanKellham wrote:

I’ve got a couple of TP-Link Bulbs all integrated correctly into HA, however when I set up a scene with them, the stored color_temp value isn’t applied with the rest of the scene, instead having the light default to a default warm white colour. I can adjust the color_temp of the bulbs perfectly fine through the web UI, but it seems the scene just ignores the set color_temp.

Any ideas?

Posts: 1

Participants: 1

Read full topic

@tika911 wrote:

Hi All,

coupe of days ago my Ubuntu VM was forced rebooted. When it came back up the gui was not accessible. Tried a bunch of things including installed from scratch (gui was accessible) restoring from snapshot (still accessible) but the cloud integration was not working. I remove the cloud file from the config and reboot. Gui is no longer accessible. Looks like something changed that is causing the GUI to not work. Google a whole bunch and found this topic.

I am a noob with docker but learning fast. I tried removing the supervisor container and reinstalling but that does not work also.

Appreciate any help. Logs attached from the reboot this am when the gui stopped.

2020-04-11 07:14:11 WARNING (Thread-8) [pychromecast.socket_client] [192.168.4.203:8009] Heartbeat timeout, resetting connection
2020-04-11 07:14:41 ERROR (Thread-8) [pychromecast.socket_client] [192.168.4.203:8009] Failed to connect, retrying in 5.0s
2020-04-11 07:39:40 ERROR (MainThread) [homeassistant.components.cloud.http_api] Unexpected error processing request for /api/cloud/login
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/cloud/http_api.py", line 129, in error_handler
    result = await handler(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 50, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/cloud/http_api.py", line 196, in post
    await cloud.login(data["email"], data["password"])
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 179, in login
    await self.start()
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 237, in start
    await self.client.logged_in()
  File "/usr/src/homeassistant/homeassistant/components/cloud/client.py", line 120, in logged_in
    gconf.async_enable_local_sdk()
  File "/usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py", line 210, in async_enable_local_sdk
    self.hass, DOMAIN, "Local Support", webhook_id, self._handle_local_webhook,
  File "/usr/src/homeassistant/homeassistant/components/webhook/__init__.py", line 33, in async_register
    raise ValueError("Handler is already defined!")
ValueError: Handler is already defined!
2020-04-11 07:39:58 ERROR (MainThread) [homeassistant.components.cloud.http_api] Unexpected error processing request for /api/cloud/login
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/cloud/http_api.py", line 129, in error_handler
    result = await handler(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 50, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/cloud/http_api.py", line 196, in post
    await cloud.login(data["email"], data["password"])
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 178, in login
    await self.run_executor(self.auth.login, email, password)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 136, in login
    cognito = self._authenticate(email, password)
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 195, in _authenticate
    assert not self.cloud.is_logged_in, "Cannot login if already logged in."
AssertionError: Cannot login if already logged in.
2020-04-11 07:48:47 ERROR (MainThread) [homeassistant.components.cloud.http_api] Unexpected error processing request for /api/cloud/login
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/cloud/http_api.py", line 129, in error_handler
    result = await handler(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 50, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/cloud/http_api.py", line 196, in post
    await cloud.login(data["email"], data["password"])
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 178, in login
    await self.run_executor(self.auth.login, email, password)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 136, in login
    cognito = self._authenticate(email, password)
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 195, in _authenticate
    assert not self.cloud.is_logged_in, "Cannot login if already logged in."
AssertionError: Cannot login if already logged in.
2020-04-11 07:49:38 ERROR (Thread-9) [pychromecast.socket_client] [192.168.4.207:8009] Failed to connect. No retries.
2020-04-11 07:49:41 ERROR (Thread-10) [pychromecast.socket_client] [192.168.4.204:8009] Failed to connect. No retries.
2020-04-11 07:49:41 ERROR (Thread-11) [pychromecast.socket_client] [192.168.4.206:8009] Failed to connect: [Errno 113] Host is unreachable. aborting due to stop signal.
2020-04-11 07:54:15 INFO (MainThread) [homeassistant.bootstrap] Config directory: /config
2020-04-11 07:54:17 INFO (SyncWorker_0) [homeassistant.loader] Loaded breaking_changes from custom_components.breaking_changes
2020-04-11 07:54:18 INFO (SyncWorker_2) [homeassistant.loader] Loaded hacs from custom_components.hacs
2020-04-11 07:54:18 INFO (SyncWorker_5) [homeassistant.loader] Loaded weather from homeassistant.components.weather
2020-04-11 07:54:18 INFO (SyncWorker_4) [homeassistant.loader] Loaded alarm_control_panel from homeassistant.components.alarm_control_panel
2020-04-11 07:54:18 INFO (SyncWorker_0) [homeassistant.loader] Loaded light from homeassistant.components.light
2020-04-11 07:54:18 INFO (SyncWorker_1) [homeassistant.loader] Loaded group from homeassistant.components.group
2020-04-11 07:54:19 INFO (SyncWorker_5) [homeassistant.loader] Loaded scene from homeassistant.components.scene
2020-04-11 07:54:19 INFO (SyncWorker_3) [homeassistant.loader] Loaded input_number from homeassistant.components.input_number
2020-04-11 07:54:19 INFO (SyncWorker_2) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2020-04-11 07:54:19 INFO (SyncWorker_0) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2020-04-11 07:54:19 INFO (SyncWorker_6) [homeassistant.loader] Loaded input_text from homeassistant.components.input_text
2020-04-11 07:54:19 INFO (SyncWorker_7) [homeassistant.loader] Loaded automation from homeassistant.components.automation
2020-04-11 07:54:19 INFO (SyncWorker_4) [homeassistant.loader] Loaded device_automation from homeassistant.components.device_automation
2020-04-11 07:54:20 INFO (SyncWorker_3) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook
2020-04-11 07:54:20 INFO (SyncWorker_2) [homeassistant.loader] Loaded http from homeassistant.components.http
2020-04-11 07:54:20 INFO (SyncWorker_7) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
2020-04-11 07:54:20 INFO (MainThread) [homeassistant.setup] Setting up homeassistant
2020-04-11 07:54:20 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds.
2020-04-11 07:54:20 INFO (SyncWorker_8) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
2020-04-11 07:54:20 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
2020-04-11 07:54:20 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.
2020-04-11 07:54:20 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-04-11 07:54:21 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for breaking_changes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2020-04-11 07:54:21 INFO (SyncWorker_5) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery
2020-04-11 07:54:21 INFO (SyncWorker_9) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded plex from homeassistant.components.plex
2020-04-11 07:54:21 INFO (SyncWorker_6) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded map from homeassistant.components.map
2020-04-11 07:54:21 INFO (SyncWorker_4) [homeassistant.loader] Loaded speedtestdotnet from homeassistant.components.speedtestdotnet
2020-04-11 07:54:21 INFO (SyncWorker_3) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2020-04-11 07:54:21 INFO (SyncWorker_7) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2020-04-11 07:54:21 INFO (SyncWorker_1) [homeassistant.loader] Loaded config from homeassistant.components.config
2020-04-11 07:54:21 INFO (SyncWorker_5) [homeassistant.loader] Loaded cover from homeassistant.components.cover
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded ecobee from homeassistant.components.ecobee
2020-04-11 07:54:21 INFO (SyncWorker_1) [homeassistant.loader] Loaded esphome from homeassistant.components.esphome
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded zwave from homeassistant.components.zwave
2020-04-11 07:54:21 INFO (SyncWorker_3) [homeassistant.loader] Loaded cast from homeassistant.components.cast
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2020-04-11 07:54:21 INFO (SyncWorker_6) [homeassistant.loader] Loaded system_health from homeassistant.components.system_health
2020-04-11 07:54:21 INFO (SyncWorker_8) [homeassistant.loader] Loaded tts from homeassistant.components.tts
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded hassio from homeassistant.components.hassio
2020-04-11 07:54:21 INFO (SyncWorker_3) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2020-04-11 07:54:21 INFO (SyncWorker_5) [homeassistant.loader] Loaded life360 from homeassistant.components.life360
2020-04-11 07:54:21 INFO (SyncWorker_1) [homeassistant.loader] Loaded nest from homeassistant.components.nest
2020-04-11 07:54:21 INFO (SyncWorker_4) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded coronavirus from homeassistant.components.coronavirus
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded input_select from homeassistant.components.input_select
2020-04-11 07:54:21 INFO (SyncWorker_8) [homeassistant.loader] Loaded cloud from homeassistant.components.cloud
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded switch from homeassistant.components.switch
2020-04-11 07:54:21 INFO (SyncWorker_5) [homeassistant.loader] Loaded panel_iframe from homeassistant.components.panel_iframe
2020-04-11 07:54:21 INFO (SyncWorker_4) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
2020-04-11 07:54:21 INFO (SyncWorker_3) [homeassistant.loader] Loaded sun from homeassistant.components.sun
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded updater from homeassistant.components.updater
2020-04-11 07:54:21 INFO (SyncWorker_8) [homeassistant.loader] Loaded proximity from homeassistant.components.proximity
2020-04-11 07:54:21 INFO (SyncWorker_5) [homeassistant.loader] Loaded logger from homeassistant.components.logger
2020-04-11 07:54:21 INFO (SyncWorker_6) [homeassistant.loader] Loaded script from homeassistant.components.script
2020-04-11 07:54:21 INFO (SyncWorker_3) [homeassistant.loader] Loaded panel_custom from homeassistant.components.panel_custom
2020-04-11 07:54:21 INFO (SyncWorker_1) [homeassistant.loader] Loaded mqtt from homeassistant.components.mqtt
2020-04-11 07:54:21 INFO (SyncWorker_2) [homeassistant.loader] Loaded wled from homeassistant.components.wled
2020-04-11 07:54:21 INFO (SyncWorker_4) [homeassistant.loader] Loaded history from homeassistant.components.history
2020-04-11 07:54:21 INFO (SyncWorker_6) [homeassistant.loader] Loaded person from homeassistant.components.person
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded ifttt from homeassistant.components.ifttt
2020-04-11 07:54:21 INFO (SyncWorker_3) [homeassistant.loader] Loaded zone from homeassistant.components.zone
2020-04-11 07:54:21 INFO (SyncWorker_8) [homeassistant.loader] Loaded notify from homeassistant.components.notify
2020-04-11 07:54:21 INFO (SyncWorker_5) [homeassistant.loader] Loaded api from homeassistant.components.api
2020-04-11 07:54:21 INFO (SyncWorker_1) [homeassistant.loader] Loaded auth from homeassistant.components.auth
2020-04-11 07:54:21 INFO (SyncWorker_4) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
2020-04-11 07:54:21 INFO (SyncWorker_9) [homeassistant.loader] Loaded envisalink from homeassistant.components.envisalink
2020-04-11 07:54:21 INFO (SyncWorker_0) [homeassistant.loader] Loaded search from homeassistant.components.search
2020-04-11 07:54:21 INFO (SyncWorker_8) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2020-04-11 07:54:21 INFO (SyncWorker_7) [homeassistant.loader] Loaded influxdb from homeassistant.components.influxdb
2020-04-11 07:54:21 INFO (MainThread) [homeassistant.bootstrap] Setting up {'system_log', 'logger'}
2020-04-11 07:54:21 INFO (MainThread) [homeassistant.setup] Setting up logger
/usr/local/lib/python3.7/site-packages/sqlalchemy/connectors/pyodbc.py:79: SAWarning: No driver name specified; this is expected by PyODBC when using DSN-less connections
  "No driver name specified; "
2020-04-11 07:54:34 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2020-04-11 07:58:45 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
/usr/local/lib/python3.7/site-packages/sqlalchemy/connectors/pyodbc.py:79: SAWarning: No driver name specified; this is expected by PyODBC when using DSN-less connections
  "No driver name specified; "
2020-04-11 08:03:09 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:07:34 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:11:58 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:16:22 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:20:46 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:25:10 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:29:35 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 08:33:59 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 09:00:03 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (pyodbc.OperationalError) ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
2020-04-11 09:00:48 ERROR (MainThread) [homeassistant.setup] Setup failed for recorder: Integration failed to initialize.
2020-04-11 09:03:12 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:13 WARNING (MainThread) [homeassistant.components.group] The 'view' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-04-11 09:03:32 WARNING (MainThread) [homeassistant.setup] Setup of envisalink is taking over 10 seconds.
2020-04-11 09:03:32 WARNING (MainThread) [homeassistant.setup] Setup of group is taking over 10 seconds.
2020-04-11 09:03:32 WARNING (MainThread) [homeassistant.setup] Setup of input_number is taking over 10 seconds.
2020-04-11 09:03:32 WARNING (MainThread) [homeassistant.setup] Setup of influxdb is taking over 10 seconds.
2020-04-11 09:03:39 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of history. Setup failed for dependencies: recorder
2020-04-11 09:03:39 ERROR (MainThread) [homeassistant.setup] Setup failed for history: Could not set up all dependencies.
2020-04-11 09:03:39 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2020-04-11 09:03:39 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2020-04-11 09:04:02 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.
2020-04-11 09:04:02 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.
2020-04-11 09:04:02 WARNING (MainThread) [homeassistant.setup] Setup of updater is taking over 10 seconds.
2020-04-11 09:04:02 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds.
2020-04-11 09:04:05 WARNING (MainThread) [homeassistant.components.scene] Setup of scene platform homeassistant is taking over 10 seconds.
2020-04-11 09:04:05 WARNING (MainThread) [homeassistant.setup] Setup of person is taking over 10 seconds.
2020-04-11 09:04:05 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2020-04-11 09:04:05 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Setup of alarm_control_panel platform manual is taking over 10 seconds.
2020-04-11 09:04:16 ERROR (MainThread) [homeassistant.components.updater] Could not contact Home Assistant Update to check for updates
2020-04-11 09:04:18 ERROR (MainThread) [homeassistant.components.updater] Error fetching Home Assistant update data:
2020-04-11 09:04:18 WARNING (MainThread) [homeassistant.components.met.weather] Loading Met.no via platform config is deprecated
2020-04-11 09:04:25 WARNING (MainThread) [homeassistant.components.weather] Setup of weather platform darksky is taking over 10 seconds.
2020-04-11 09:04:26 WARNING (MainThread) [homeassistant.components.weather] Setup of weather platform met is taking over 10 seconds.
2020-04-11 09:04:28 ERROR (Thread-9) [pychromecast.socket_client] [192.168.4.204:8009] Failed to connect, retrying in 5.0s
2020-04-11 09:04:29 ERROR (Thread-11) [pychromecast.socket_client] [192.168.4.207:8009] Failed to connect, retrying in 5.0s
2020-04-11 09:04:35 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2020-04-11 09:04:35 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying...
2020-04-11 09:04:35 WARNING (MainThread) [homeassistant.components.automation] The 'hide_entity' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107
2020-04-11 09:04:36 WARNING (MainThread) [homeassistant.components.automation] The 'hide_entity' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107
2020-04-11 09:04:36 WARNING (MainThread) [homeassistant.components.automation] The 'hide_entity' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107
2020-04-11 09:04:38 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform mqtt is taking over 10 seconds.
--- Logging error ---
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1025, in emit
    msg = self.format(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 869, in format
    return fmt.format(record)
  File "/usr/local/lib/python3.7/site-packages/colorlog/colorlog.py", line 123, in format
    message = super(ColoredFormatter, self).format(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 608, in format
    record.message = record.getMessage()
  File "/usr/local/lib/python3.7/logging/__init__.py", line 369, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  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 570, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 538, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 1782, in _run_once
    handle._run()
  File "/usr/local/lib/python3.7/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/template/cover.py", line 123, in async_setup_platform
    "Must specify at least one of %s" or "%s", OPEN_ACTION, POSITION_ACTION
Message: 'Must specify at least one of %s'
Arguments: ('open_cover', 'set_cover_position')
--- Logging error ---
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1025, in emit
    msg = self.format(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 869, in format
    return fmt.format(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 608, in format
    record.message = record.getMessage()
  File "/usr/local/lib/python3.7/logging/__init__.py", line 369, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  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 570, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 538, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 1782, in _run_once
    handle._run()
  File "/usr/local/lib/python3.7/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/template/cover.py", line 123, in async_setup_platform
    "Must specify at least one of %s" or "%s", OPEN_ACTION, POSITION_ACTION
Message: 'Must specify at least one of %s'
Arguments: ('open_cover', 'set_cover_position')

Posts: 1

Participants: 1

Read full topic

@kahless wrote:

Hi all,

since some days i get some alexa.intent errors in my logfile but i don’t use it.(as far as i can tell :))

How can i fix that?

2020-04-11 16:44:06 ERROR (MainThread) [homeassistant.helpers.integration_platform] Error processing platform alexa.intent
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/integration_platform.py", line 31, in _process
    await process_platform(hass, component_name, platform)
  File "/usr/src/homeassistant/homeassistant/components/intent/__init__.py", line 47, in _async_process_intent
    await platform.async_setup_intents(hass)
AttributeError: module 'homeassistant.components.alexa.intent' has no attribute 'async_setup_intents'

I’m on the latest Hassio and supervisor versions.

Thank you very much in advance.

Posts: 1

Participants: 1

Read full topic

@adampdistefano wrote:

Hi All,

I am having troubles getting some custom text on my UI.

I have a binary sensor which monitors my computers lock state, so HA knows if I am using my machine or not. This works fine.

I wanted to create a UI element instead of saying On/Off,Detected/Clear etc, it says something like “In Use” or “Locked”

I looked at this thread (and others) which seemed to be exactly what I wanted.

2020-04-12 00_44_50-Home Assistant1349×610 34.6 KB

The Template Dev tool shows this is working, but I can’t seem to get it to work after adding it to my configuration. The computer_in_use_template sensor always shows Off.

The following is from my binary_sensors.yaml. First part is the MQTT sensor for the computer lock state, second is the template.

- platform: mqtt
  name: "Computer Lock State"
  state_topic: "computer/lock-state"
  payload_on: "unlocked"
  payload_off: "locked"
  device_class: power
  unique_id: computer_lock_state

- platform: template
  sensors:
    computer_in_use_template:
      friendly_name: Computer State
      entity_id: binary_sensor.computer_lock_state
      value_template: >-
        {% if is_state('binary_sensor.computer_lock_state', 'on') %}
          Using
        {% else %}
          Locked
        {% endif %}

Any help is appreciated!

Cheers

Posts: 2

Participants: 2

Read full topic

@Klex1404 wrote:

Hi,
I purchased a P1 meter cable at robbshop.nl to connect our Sagecom S211 DSMR to my NUC on which HA is running hassio in a docker environment.
No matter what I try, I see no values coming in.
My config:

- platform: dsmr
  #port: /dev/ttyUSB1
  port: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AO43PQP1-if00-port0
  dsmr_version: 5B

Anyone has the solution?

Posts: 2

Participants: 2

Read full topic

@Darbos wrote:

I see a lot of projects that monitor energy usage. How is everyone getting so much energy statistics? Does anyone happen to know if you can get data from comed? They did install a smart meter but I can’t find anything about extracting data

Posts: 1

Participants: 1

Read full topic

@2jan wrote:

Is there any way I can start (or actually continue where I left off) playing my podcasts on my Sonos speaker from Home Assistant?

I have a Hue dimmer switch I use to trigger Spotify playlists and TuneIn radio channels which are set up in the Sonos app. I use the standard apple podcast app, but am open to change if necessary.

Posts: 1

Participants: 1

Read full topic

@lollo03 wrote:

Hello, I’m trying to connect home assistant to my vimar by-me domotic installation. Obviously it uses KNX. But there is a problem: vimar use addresses like 0x1073 and home assistant use addresses like 0/1/2, so, my question is: can I use addresses like the one that my system already uses? I really don’t want to reconfigure all my devices! I really want to connect my house to the wonderful home assistant world!

Thank you for your support, waiting for your answers,
Lorenzo.

Posts: 1

Participants: 1

Read full topic

@davidino wrote:

Hi all,
the new 108 version bring the new functionality that supports a camera stream to an Alexa Echo show.

That is great but the stream needs to be on HTTPS otherwise Alexa will say the camera is not supported.

Now, I do have a motionEyeOS camera with the motionEye add-on but that does not support HTTPS.
Then the camera stream is only available in HTTP in the local ip.
I do have DuckDNS with Nginx with a valid certificate but I could not find a way to integrate it with motioneyeos

Does anyone have a suggestion on how to integrate it and enable a streaming on the HTTPS ?

Thanks,
David.

Posts: 2

Participants: 2

Read full topic

@fowlert wrote:

So I just got Home Assistant up and running and I’m trying to set up a few zwave light switches / dimmers and have a very newbie question. I have clicked around the interface a bit and I’m sure I did something for one light that I have not yet done for the other, but for the life of me I can’t figure out what that was.

I have two identical zwave light switches and when I go to Configuration -> Devices I can see them both. When I look at Configuration -> Entities I see both of them of them listed but then I also see one that I named “Porch”. Back in the Devices tab if I click on one of them I get an info page that has both the original switch plus the “Porch” entity listed in the Entities section. The Porch entity has a light icon + a toggle switch that does work to turn the light on and off. So I have two entities that are related to this one device.

I had to stop playing around with HA for the day and now I can’t figure out how I created the Porch entity in the first place. After clicking around the UI a bit, I just can’t seem to find where you create Entities, only view info about existing ones.

Can someone explain how I created it associated it with the switch Device?

Thx for any help!

Posts: 1

Participants: 1

Read full topic