Core: Kodi Component Issues

Created on 19 Nov 2017  路  10Comments  路  Source: home-assistant/core

Hello,

The Kodi component no longer shows up as a component and running 0.58. Please any help?

All 10 comments

These are the errors I get:

Error while setting up platform kodi
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.5/asyncio/tasks.py", line 400, in wait_for
    return fut.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/media_player/kodi.py", line 174, in async_setup_platform
    timeout=config.get(CONF_TIMEOUT), websocket=websocket)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/media_player/kodi.py", line 276, in __init__
    self._ws_server = jsonrpc_websocket.Server(self._ws_url, **kwargs)
AttributeError: module 'jsonrpc_websocket' has no attribute 'Server'

Does that problem persist with 0.58.1?

@cgtobi yes it does as that's what I am on presently.

Regards

Can you confirm your jsonrpc-websocket version?

Just run in your hass environment:
pip freeze | grep jsonrpc-websocket

Hello @cgtobi ,

it gives the output

jsonrpc-websocket==0.5

Thanks

Hello @cgtobi ,

Thanks I have finally fixed it, was a foolish mistake on my part. Thanks for the help.

Regards

Just out of curiosity, what was the issue? Maybe others will have the same problem.

Hello @cgtobi ,

Actually was a foolish one, kind of used a different name in the component and so couldn't connect. Used a friendly name of "Kodi TV", but referencing component "media_player.kodi". Kind of weird but that's what I later figured out. Once I changed the name to Kodi, everything was fine.

Regards

Thanks for following up! Never know when someone else will end up here from a search when making the same mistake.

No problem @armills, just that the system worked for a while in the previous state, until I upgraded to a particular version. I know it kind of worked till 0.53 or 0.54, so that was what took me off balance so couldn't pin point the fact it could be that.

Thanks for all the works guys.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MartinHjelmare picture MartinHjelmare  路  3Comments

TheZoker picture TheZoker  路  3Comments

arangates picture arangates  路  3Comments

Elmardus picture Elmardus  路  3Comments

missedtheapex picture missedtheapex  路  3Comments