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 Chips are not working #2451

Open
andreas-bulling opened this issue Dec 31, 2024 · 10 comments
Open

Bug Chips are not working #2451

andreas-bulling opened this issue Dec 31, 2024 · 10 comments
Labels
Bug Identifies an issue where the system is not functioning as expected.

Comments

@andreas-bulling
Copy link

TFT Version

4.3.12

Firmware Version

4.3.12

Blueprint Version

4.3.12

Panel Model

EU

What is the bug?

Chips are simply not working. Whatever I set in the respective configuration group in the blueprint, nothing is shown at the top. The only thing that is shown are the little boxed 1 and 2 when pressing the physical buttons.

Steps to Reproduce

No response

Your Panel's YAML

No response

ESPHome Logs

No response

Home Assistant Logs

No response

@andreas-bulling andreas-bulling added the Bug Identifies an issue where the system is not functioning as expected. label Dec 31, 2024
@edwardtfn
Copy link
Collaborator

edwardtfn commented Dec 31, 2024

Do you have any error message related to this in your Home Assistant logs (Settings > System > Logs)?

@andreas-bulling
Copy link
Author

Not related to Chips as far as I can see. But two others ones that I posted under the other issue

@umrath
Copy link

umrath commented Jan 3, 2025

I have the same issue.
I have set up 3 new NSPanels yesterday and today and no Chips are visible on either device.

@andreas-bulling
Copy link
Author

@edwardtfn are chips working for you? Can you send us a minimally working example that we could try?

@edwardtfn
Copy link
Collaborator

Sorry, I've been sick those days and haven't had time to work at this, but I can confirm chips are working properly with my panel running v4.3.12.

@edwardtfn
Copy link
Collaborator

Chips will be visible only when the state of the entity assigned to it is 'true' (or equivalent).
Could you please double check the state of the entity on Developer Tools > States?

@andreas-bulling
Copy link
Author

Does it have to be "on" or is a state that is a number, e.g. AC input or current solar power, also fine?

@edwardtfn
Copy link
Collaborator

I'm pretty sure any value different than 0 will be considered true, but I have to double check this info later.

@andreas-bulling
Copy link
Author

I've tried to use different entities, incl. some that definitely return a value (such as ac_input). But the chips don't work. I'll try a binary_sensor next.

BTW - what is the intended use case for these chips?

@kroessig
Copy link

kroessig commented Jan 6, 2025

I've tried to use different entities, incl. some that definitely return a value (such as ac_input). But the chips don't work. I'll try a binary_sensor next.

BTW - what is the intended use case for these chips?

i use the chips to

  • indicate whether and which garbage can is next.
  • whether the heating is on
  • the symbol changes depending on whether the battery is being charged or discharged.
  • I made a timer that plays a melody on the panel when it expires. To see if the timer is on, I also use a chip.

Most chips also change their color depending on their condition. it's simple like:

alias: Farbe Batteriesymbol steigt
sequence:
  - condition: state
    entity_id: sensor.symbol_batterie
    attribute: icon
    state: mdi:battery-arrow-up
  - data:
      component: icon_top_06
      foreground:
        - 0
        - 255
        - 0
      background: []
    action: esphome.panelwozi_set_component_color
mode: single
icon: mdi:battery-arrow-up

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.
Projects
None yet
Development

No branches or pull requests

4 participants