Skip to content
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 Media player volume buttons disapear #2286

Closed
vukisz opened this issue Sep 20, 2024 · 8 comments · Fixed by #2358
Closed

Bug Media player volume buttons disapear #2286

vukisz opened this issue Sep 20, 2024 · 8 comments · Fixed by #2358
Labels
Bug Identifies an issue where the system is not functioning as expected. Page: media_player Concerns specific to the page's interface or functionality. Validation pending A solution was proposed (maybe in `dev`). Waiting for validation/tests/feedback.
Milestone

Comments

@vukisz
Copy link

vukisz commented Sep 20, 2024

TFT Version

4.3.11

Firmware Version

4.3.11

Blueprint Version

4.3.11

Panel Model

EU

What is the bug?

When entering media page volume up/down buttons is displayed shortly and then hidden. Video: https://photos.app.goo.gl/DJP5r9dFjxWcXYK8A
Media control via HA SS:
image

Steps to Reproduce

  1. Media which I want to control: CCWGTV (chromecast with google tv).
  2. It is playing custom application for live TV (maybe that is the issue) But I can control volume via HA ?

Your Panel's YAML

substitutions:
  # Settings - Editable values
  name: nspanel-stand
  friendly_name: Nspanel Stand
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  nextion_update_url: !secret nspanel_eu"  # Optional


  # Add-on configuration (if needed)
  ## Add-on climate (https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/main/docs/addon_climate.md)
  heater_relay: "1"     # Possible values: "1" or "2"
  temp_units: "°C"      # Temperatures in Fahrenheit
  temp_min: "15"        # Min supported temperature is 15°C
  temp_max: "28"        # Max supported temperature is 28°C
  temp_step: "0.1"        # Temperature granularity is 0.1°C
  heat_deadband: "0.4"  # Temperature delta before engaging heat
  heat_overrun: "0.4"   # Temperature delta before disengaging heat


# Customization area
##### My customization - Start #####
# Enable Home Assistant API
api:
  encryption:
    key: !secret encryption_key_nspanel_stand

wifi:
  manual_ip:
    static_ip: 192.168.86.240
    gateway: 192.168.86.1
    subnet: 255.255.255.0

sensor:
  - id: ha_temperature
    platform: homeassistant
    entity_id: sensor.sonoff_snzb_02d_north_room_temperature   # Please change this by the entity_id of your temperature sensor in Home Assistant
  - id: combined_temperature
    platform: template
    lambda: |-
      if (wifi_component->is_connected() and api_server->is_connected())  // Testing both as WiFi is faster to detect issues
        return ha_temperature->state;
      else
        return temp_nspanel->state;


climate:
  - id: !extend thermostat_embedded
    sensor: combined_temperature
    visual:
      temperature_step: ${temp_step}
##### My customization - End #####

# Core and optional configurations
packages:
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: main
    refresh: 300s
    files:
      - nspanel_esphome.yaml # Basic package
      # Optional advanced and add-on configurations
      # - esphome/nspanel_esphome_advanced.yaml
      # - esphome/nspanel_esphome_addon_ble_tracker.yaml
      # - esphome/nspanel_esphome_addon_bluetooth_proxy.yaml
      # - esphome/nspanel_esphome_addon_climate_cool.yaml
      - esphome/nspanel_esphome_addon_climate_heat.yaml
      # - esphome/nspanel_esphome_addon_climate_dual.yaml
      # - esphome/nspanel_esphome_addon_cover.yaml

ESPHome Logs

[16:28:40][W][component:238]: Components should block for at most 30 ms.
[16:28:41][D][text_sensor:064]: 'NSPanel local event': Sending state '{"page": "buttonpage03", "event": "long_click", "component": "button01"}'
[16:28:41][D][script:077]: Script 'timer_page' restarting (mode: restart)
[16:28:41][D][script:077]: Script 'timer_dim' restarting (mode: restart)
[16:28:41][D][script:077]: Script 'timer_sleep' restarting (mode: restart)
[16:28:41][D][nextion_textsensor:014]: Processed text_sensor "localevent" state "{"page": "buttonpage03", "event": "long_click", "component": "button01"}"
[16:28:41][D][text_sensor:064]: 'Detailed Entity': Sending state 'media_player.android_tv_remote_livingroom_chromecast'
[16:28:41][D][text_sensor:064]: 'Current Page': Sending state 'media_player'
[16:28:41][D][script.page_changed:2644]: New page: media_player
[16:28:41][D][script.page_changed:2669]: Entity shown: media_player.android_tv_remote_livingroom_chromecast
[16:28:41][D][script:077]: Script 'timer_page' restarting (mode: restart)
[16:28:41][D][script:077]: Script 'timer_dim' restarting (mode: restart)
[16:28:41][D][script:077]: Script 'timer_sleep' restarting (mode: restart)
[16:28:41][D][nextion_textsensor:014]: Processed text_sensor "current_page" state "media_player"
[16:28:41][D][text_sensor:064]: 'Detailed Entity': Sending state 'media_player.android_tv_remote_livingroom_chromecast'
[16:28:43][D][sensor:094]: 'ntc_source': Sending state 1.51567 V with 2 decimals of accuracy
[16:28:43][D][resistance:039]: 'resistance_sensor' - Resistance 9513.6Ω
[16:28:43][D][sensor:094]: 'resistance_sensor': Sending state 9513.61816 Ω with 1 decimals of accuracy
[16:28:43][D][ntc:026]: 'Temperature' - Temperature: 26.1°C
[16:28:43][D][sensor:094]: 'Temperature': Sending state 26.12634 °C with 1 decimals of accuracy

Home Assistant Logs

No response

@vukisz vukisz added the Bug Identifies an issue where the system is not functioning as expected. label Sep 20, 2024
@edwardtfn
Copy link
Collaborator

Could you please go to Developer Tools, tab States, then look for the media player entity which fails, then share here it's attributes?
Please remove any sensitive info before sharing.

@vukisz
Copy link
Author

vukisz commented Sep 22, 2024

Sure. Here you go:

app_id: lt.telia.tv
app_name: lt.telia.tv
assumed_state: true
device_class: tv
friendly_name: Android TV Remote Livingroom chromecast
supported_features: 153529

@edwardtfn edwardtfn added this to the v4.4.0 milestone Oct 21, 2024
@edwardtfn edwardtfn added the Work in progress Indicates issues that are actively being worked on by the development team. label Oct 28, 2024
@edwardtfn
Copy link
Collaborator

Hey, I'm sorry for the delay here, but I couldn't get into this earlier.

Are you still facing this issue?

VOLUME_SET is not part of the supported features indicated by your entity, which is causing it to be hidden from the panel, but VOLUME_STEP is supported, so maybe I could use that to show the volume bar.
I will take a look at that.

supported_features: 153529

 => PAUSE = 1
    SEEK = 2
    VOLUME_SET = 4
 => VOLUME_MUTE = 8
 => PREVIOUS_TRACK = 16
 => NEXT_TRACK = 32

 => TURN_ON = 128
 => TURN_OFF = 256
 => PLAY_MEDIA = 512
 => VOLUME_STEP = 1024
    SELECT_SOURCE = 2048
 => STOP = 4096
    CLEAR_PLAYLIST = 8192
 => PLAY = 16384
    SHUFFLE_SET = 32768
    SELECT_SOUND_MODE = 65536
 => BROWSE_MEDIA = 131072
    REPEAT_SET = 262144
    GROUPING = 524288
    MEDIA_ANNOUNCE = 1048576
    MEDIA_ENQUEUE = 2097152

May I ask you to go to Developer Tools, tab Actions, then look for the action "Media Player: Volume Set", select that entity and try to set a volume and please let me know if that works?
If you can use this chance and test also the actions "Media Player: Turn up volume" and "Media Player: Turn down volume" it could give useful info also. 😉

@edwardtfn edwardtfn added 👀Missing information Additional information needed Page: media_player Concerns specific to the page's interface or functionality. labels Oct 28, 2024
@vukisz
Copy link
Author

vukisz commented Oct 29, 2024

Hello. After creating this issue I even upgraded one of my TVs. Now it's not standard chromecast with google tv dongle, but built-in android os.
Media Player: Volume Set works only on standard chromecast with google tv dongle, but not with built-in android os TV (entity does not support this service).
"Media Player: Turn up volume" and "Media Player: Turn down volume" works for both

@edwardtfn edwardtfn removed the 👀Missing information Additional information needed label Oct 29, 2024
edwardtfn added a commit that referenced this issue Oct 31, 2024
@edwardtfn edwardtfn added the Validation pending A solution was proposed (maybe in `dev`). Waiting for validation/tests/feedback. label Oct 31, 2024
@edwardtfn edwardtfn linked a pull request Nov 2, 2024 that will close this issue
@edwardtfn edwardtfn removed the Work in progress Indicates issues that are actively being worked on by the development team. label Nov 11, 2024
@edwardtfn
Copy link
Collaborator

I believe this is fixed in DEV, so I will close this for now, but please feel free to reopen when you have a chance to try with the new version (still to be released) and the issue persists.

@vukisz
Copy link
Author

vukisz commented Nov 15, 2024

I believe this is fixed in DEV, so I will close this for now, but please feel free to reopen when you have a chance to try with the new version (still to be released) and the issue persists.

Thanks will do so. A bit of afraid of new version, as I have not had any nspanel updates yet :-)

@edwardtfn
Copy link
Collaborator

I've worked a lot to make the update process an easy thing, but it still need some manual work, as Home Assistant doesn't offer a way to automate the Blueprint updates. It still a quite straight forward process, but unfortunately cannot be automated.
On the ESPHome side you just re-flash your device and then press to update the TFT and everything should go smoothly. With this new version I'm introducing a switch to enable automatic update of TFT, so after the one, the following versions will be even easier. 😉

But I have to say we have too few people testing on DEV or Beta, so it could happen that right after a big release like this we can have some new bugs. Usually if a couple of days those are all fixed and we have a more stable release.

@vukisz
Copy link
Author

vukisz commented Nov 15, 2024

I've worked a lot to make the update process an easy thing, but it still need some manual work, as Home Assistant doesn't offer a way to automate the Blueprint updates. It still a quite straight forward process, but unfortunately cannot be automated. On the ESPHome side you just re-flash your device and then press to update the TFT and everything should go smoothly. With this new version I'm introducing a switch to enable automatic update of TFT, so after the one, the following versions will be even easier. 😉

But I have to say we have too few people testing on DEV or Beta, so it could happen that right after a big release like this we can have some new bugs. Usually if a couple of days those are all fixed and we have a more stable release.

Thanks for encouragement. Reviewed update docs and looks way simpler, then initial install :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Identifies an issue where the system is not functioning as expected. Page: media_player Concerns specific to the page's interface or functionality. Validation pending A solution was proposed (maybe in `dev`). Waiting for validation/tests/feedback.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants