Weird errors in log after upgrade to 0.82


#1

Hi

After lates upgrade I notices some strange error in the log:

peError: expected bytes, NoneType found
Exception ignored in: 'libopenzwave.str_to_cppstr'
TypeError: expected bytes, NoneType found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     4  100     4    0     0    707      0 --:--:-- --:--:-- --:--:--   800
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     4  100     4    0     0    839      0 --:--:-- --:--:-- --:--:--  1000

Looks like hass is trying to download something again and again…

Anyone has the same issue?


#2

Nothing similar here. Perhaps seeing the whole log may reveal something?


#3

It is visible in docker logs from the container…But not in the home-assistant.log…

After container restart I have:


2018-11-11 01:04:57 INFO (MainThread) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2018-11-11 01:04:57 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
2018-11-11 01:04:57 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2018-11-11 01:04:57 INFO (MainThread) [homeassistant.setup] Setting up recorder
2018-11-11 01:04:57 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
2018-11-11 01:04:57 INFO (MainThread) [homeassistant.loader] Loaded http from homeassistant.components.http
2018-11-11 01:04:57 INFO (MainThread) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2018-11-11 01:04:58 INFO (MainThread) [homeassistant.loader] Loaded api from homeassistant.components.api
2018-11-11 01:04:58 INFO (MainThread) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2018-11-11 01:04:58 INFO (MainThread) [homeassistant.loader] Loaded auth from homeassistant.components.auth
2018-11-11 01:04:58 INFO (MainThread) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
2018-11-11 01:04:59 INFO (MainThread) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
2018-11-11 01:04:59 INFO (MainThread) [homeassistant.loader] Loaded logger from homeassistant.components.logger
2018-11-11 01:04:59 INFO (MainThread) [homeassistant.setup] Setting up logger
TypeError: expected bytes, NoneType found
Exception ignored in: 'libopenzwave.str_to_cppstr'
TypeError: expected bytes, NoneType found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     4  100     4    0     0    272      0 --:--:-- --:--:-- --:--:--   285
2018-11-11 01:05:07 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 10.0.0.119
2018-11-11 01:05:08 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 10.0.0.119. Retrying in 2 seconds
Config directory: /config
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     4  100     4    0     0    269      0 --:--:-- --:--:-- --:--:--   285

And than non stop the weird stuff.

In home-assistant.log the is only

2018-11-11 01:05:07 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 10.0.0.119
2018-11-11 01:05:08 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 10.0.0.119. Retrying in 2 seconds

#4

Found it. It was one of the scripts. :).


#5

can you tell me what the mistake was? I have the same issue and I believe my lovelace ui is extremely lagging due to some sort of bug in my setup


#6

I had two sensors with bash command. It was executing curl. I changed the interval to once per 15 minutes.


#7

hmm seems not to be my problem but I will go through all my sensors and see if I can find any issues there as well.
were your sensors zwave related?


#8

No. It was related to air quality monitoring.


#9

I just upgraded my home assistant from .78 to .82, and am now seeing the error:

TypeError: expected bytes, NoneType found
Exception ignored in: ‘libopenzwave.str_to_cppstr’
TypeError: expected bytes, NoneType found


#10

same issue here, running the latest 0.84.4


#11

Same for me. Z-Wave seems to work, however.


#12

Created https://github.com/home-assistant/home-assistant/pull/19928 to remove the log. It’s harmless though.


#13

Ok, thanks!