0.39.2 - Major Problems with Media Player component

Development
1

Hey’all: I wanted to report kind of a big issue with 0.39 and the media player component. I went to login to the interface, and I have roughly 120 duplicate Roku TV component’s and an equal number of Plex components as well. Upon reviewing the log I have the specific arbitrarily different exceptions being thrown back and forth throughout my log

17-03-02 16:35:00 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback <function async_subscribe.<locals>.async_mqtt_topic_subscriber at 0x7f11840b78c8>
Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 49, in uvloop.loop.Handle._run (uvloop/loop.c:48380)
  File "/usr/src/app/homeassistant/components/mqtt/__init__.py", line 204, in async_mqtt_topic_subscriber
event.data[ATTR_PAYLOAD], event.data[ATTR_QOS])
  File "/usr/src/app/homeassistant/core.py", line 246, in async_run_job
target(*args)
  File "/usr/src/app/homeassistant/components/light/mqtt.py", line 170, in brightness_received
device_value = float(templates[CONF_BRIGHTNESS](payload))
ValueError: could not convert string to float: 'null'
17-03-02 16:35:00 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback <function async_subscribe.<locals>.async_mqtt_topic_subscriber at 0x7f11840b78c8>
Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 49, in uvloop.loop.Handle._run (uvloop/loop.c:48380)
  File "/usr/src/app/homeassistant/components/mqtt/__init__.py", line 204, in async_mqtt_topic_subscriber
event.data[ATTR_PAYLOAD], event.data[ATTR_QOS])
  File "/usr/src/app/homeassistant/core.py", line 246, in async_run_job
target(*args)
  File "/usr/src/app/homeassistant/components/light/mqtt.py", line 170, in brightness_received
device_value = float(templates[CONF_BRIGHTNESS](payload))
ValueError: could not convert string to float: 'null'
17-03-02 17:00:37 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback <function async_subscribe.<locals>.async_mqtt_topic_subscriber at 0x7f11840b78c8>
Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 49, in uvloop.loop.Handle._run (uvloop/loop.c:48380)
  File "/usr/src/app/homeassistant/components/mqtt/__init__.py", line 204, in async_mqtt_topic_subscriber
event.data[ATTR_PAYLOAD], event.data[ATTR_QOS])
  File "/usr/src/app/homeassistant/core.py", line 246, in async_run_job
target(*args)
  File "/usr/src/app/homeassistant/components/light/mqtt.py", line 170, in brightness_received
device_value = float(templates[CONF_BRIGHTNESS](payload))
ValueError: could not convert string to float: 'null'

Then It’ll randomly throw this exception

17-03-02 16:47:41 WARNING (MainThread) [homeassistant.components.media_player] Updating roku media_player took longer than the scheduled update interval 0:00:10
17-03-02 16:54:32 WARNING (MainThread) [homeassistant.components.media_player] Updating roku media_player took longer than the scheduled update interval 0:00:10
17-03-02 16:54:42 WARNING (MainThread) [homeassistant.components.media_player] Updating roku media_player took longer than the scheduled update interval 0:00:10
17-03-02 16:54:53 WARNING (MainThread) [homeassistant.components.media_player] Updating roku media_player took longer than the scheduled update interval 0:00:10
17-03-02 16:59:36 WARNING (MainThread) [homeassistant.components.media_player] Updating roku media_player took longer than the scheduled update interval 0:00:10

It will either be roku.media_player or plex.media_player, but they exception is the same. I have the discovery component enabled along with MQTT discovery. Amy ideas??

2

Disabling discovery is a temp workaround.

3

happening to me too. I’ve disabled discovery as you said for a temp workaround.

4

having the same issue.

5

Release 0.39.3 addresses this issue, did you update?

6

Updated to 39.3 and still throwing the exception in the log, but the multiple instances appear to have stopped spawning. I’m having weird MQTT discovery problems too. The log keeps bitching about the MQTT component itself in line 170

4:15:35 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback <function async_subscribe.<locals>.async_mqtt_topic_subscriber at 0x7f5c3e389840>

Traceback (most recent call last):
File “uvloop/cbhandles.pyx”, line 49, in uvloop.loop.Handle._run (uvloop/loop.c:48380)
File “/usr/src/app/homeassistant/components/mqtt/init.py”, line 204, in async_mqtt_topic_subscriber
event.data[ATTR_PAYLOAD], event.data[ATTR_QOS])
File “/usr/src/app/homeassistant/core.py”, line 246, in async_run_job
target(*args)
File “/usr/src/app/homeassistant/components/light/mqtt.py”, line 170, in brightness_received
device_value = float(templatesCONF_BRIGHTNESS)
ValueError: could not convert string to float: ‘null’

I’ve reviewed my config file (along with completely rewriting it) along with looking at the mqtt broker and the component itself in HASS, I don’t have any MQTT devices throwing a NULL brightness back (naturally this would cause the exception as it can’t change a null string to a float integer).