core: Platform support not supported openhome - Volumio / Openhome integration
The problem
Just updated to Home Assistant 2023.7.0 Supervisor 2023.07.1 Frontend-versie: 20230705.0 - latest
I get this repair notification:
Platform support not supported
The openhome platform for the media_player integration does not support platform setup.
Please remove it from your configuration and restart Home Assistant to fix this issue.
What version of Home Assistant Core has the issue?
2023.7.0
What was the last working version of Home Assistant Core?
2023.6.X (all)
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Openhome
Link to integration documentation on our website
https://www.home-assistant.io/integrations/openhome/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.components.media_player
Source: helpers/entity_platform.py:211
Integration: Mediaspeler (documentation, issues)
First occurred: 22:18:46 (2 occurrences)
Last logged: 22:18:46
The openhome platform for the media_player integration does not support platform setup. Please remove it from your config.
### Additional information
Well, I do not have this anywhere in the config.
I do not use openhome for media players. I do not have them in configuration.yaml and not in the UI integrations.
It looks, like this comes from the integration it self. Volumio provides discoverable Openhome players. They are ignored in my config.
This problem is reported by more users here: https://community.home-assistant.io/t/platform-support-not-supported-openhome/588760
I'm available for contact and guided deeper diagnose, if needed.
Thank you all in advance. ;-)About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 32 (15 by maintainers)
I am using BubbleUPnP Server to make some streaming devices Openhome compatible
No problem at all - my pleasure in fixing. After all - I broke it 🤣
🍻
Thank you very much for your super-fast and skillful reaction.
Where can I buy you a beer?
Yep! That’s because any discovery component discovered
openhomedevices will be ignored by default.openhomeis now a configurable through the UI.Due to that line I mentioned earlier, openhome devices with certain product versions were getting discovered by the old discovery component and failing with an error. But they were also getting discovered by the new UI configuration and being offered for configuration.
I’ve managed to recreate the issue.
This line needs deleted from the discovery component: https://github.com/home-assistant/core/blob/master/homeassistant/components/discovery/__init__.py#L63
Can you try adding
There’ll be one served up over the network. It’s possible your home assistant logs will say something like found device at X and you can load that address in a browser to get the description.
The xml will most likely be a generated as it’ll contain information about the device services available and their location on the network.
I’ll have a look to see if I can run either bubbleds or volumio and see where the issue is.
It’ll be an xml file served up from the device itself. Maybe a volumio dev could link to one.
Best case is I’ll see if I can install volumio later tonight and replicate this issue.
Is volumio responding to ssdp searches for openhome devices? If that’s the case then it’s possible the registration of the openhome configflow might fail as the device description may differ. It would be useful to get a device description for volumio so it can be excluded.
Is this effecting the use of volumio?
@home-assistant unassign volumio