New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] core simulator web ui not working with media_player sound_mode_list or source_list - real remote web ui working fine #272
Comments
Well, sorry for wasting your time. I only updated the images with "docker-compose pull" and forgot to recreate the containers. So my image was 5 month old. It now works fine :) Also, i had the same issue with the predefined list values not showing on my real remote. A reboot somehow made them available on my real remote. Restarting the core-simulator container after adding the entity also brings up the list with the predefined source and sound mode values. Should i create another ticket for this minor bug? |
No worries. Another issue is the sequence of request messages the remote is supposed to send. That's how it should work, first a The Python integration library moves the entities from available to configured if it receives a Looking at the Python example logs, the
Issue: the Since the messages are swapped, the I'll fix the message sequence and retest all integrations. We can keep this issue open until it's fixed in the Simulator. We might also change the |
Message sequence order is fixed in core-simulator v0.39.10, which resulted in empty drop-down lists. |
Fixed message sequence order is included in the just released version 1.6.4 |
Is there an existing issue for this?
Description
It looks like the core simulator web ui does not support sound_mode_list and source_list of the media_player entity. The real remote with current firmware does support it.
This has been discovered using the python integration library and a minimal example.
How to Reproduce
hello_integration.py.txt
Expected behavior
System version
No response
What part of the system affected by the problem?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: