core: Log filled with error messages : [websocket] error from callback [...] on_message() missing 1 required positional argument: 'message'

Home Assistant release with the issue:

Home Assistant 0.91.4

Last working Home Assistant release (if known):

No problem found on HomeAssistant v0.91.1 (and maybe 0.91.2) Problem occured since v0.91.3+

Operating environment (Hass.io/Docker/Windows/etc.):

ArchLinuxARM Kernel: armv7l Linux 5.0.7-1-ARCH Board Odroid-U3 (armv7) HassIO installation (using odroid-xu official docker image: armv7)

Component/platform:

Concerns both Home Assistant (standalone, or HASSIO installation)

Description of problem:

The log is filled by error messages related to WebSocket: missing 1 required positional argument: ‘message’ Check the log below. Maybe related to issue https://github.com/home-assistant/home-assistant/issues/17532

Traceback (if applicable):

[...]
2019-04-17 13:06:08 ERROR (Thread-3) [websocket] error from callback <bound method Listener.on_message of <Listener(Thread-4, initial daemon)>>: on_message() missing 1 required positional argument: 'message'
2019-04-17 13:06:38 ERROR (Thread-3) [websocket] error from callback <bound method Listener.on_message of <Listener(Thread-4, initial daemon)>>: on_message() missing 1 required positional argument: 'message'
2019-04-17 13:07:08 ERROR (Thread-3) [websocket] error from callback <bound method Listener.on_message of <Listener(Thread-4, initial daemon)>>: on_message() missing 1 required positional argument: 'message'
2019-04-17 13:07:38 ERROR (Thread-3) [websocket] error from callback <bound method Listener.on_message of <Listener(Thread-4, initial daemon)>>: on_message() missing 1 required positional argument: 'message'
2019-04-17 13:08:08 ERROR (Thread-3) [websocket] error from callback <bound method Listener.on_message of <Listener(Thread-4, initial daemon)>>: on_message() missing 1 required positional argument: 'message'

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 24 (2 by maintainers)

Most upvoted comments

The error flood went away when I disabled the Pushbullet integration

rv-kip on Nov 20, 2020

Thanks for the tip. No more garbage in my log file 😉

nicolasvila on Sep 10, 2019

alright well.

I fixed my issue, _app.py line 339 to 351 change to:

    def _callback(self, callback, *args):
        if callback:
            try:
                callback(self, *args)
            except Exception as e:
                _logging.error("error from callback {}: {}".format(callback, e))
                if _logging.isEnabledForDebug():
                    _, _, tb = sys.exc_info()
                    traceback.print_tb(tb)

This code is from an older version that i kept seeing referenced with this issue… its working fine for me now, your results may vary, Enjoy.

source: https://github.com/websocket-client/websocket-client/blob/v0.48.0/websocket/_app.py

ctrl50 on Jun 2, 2019

Thank you @ctrl50. I have disabled Pushbullet notifications platform and those pesky msgs went away.

ccorderod on Jun 1, 2019