question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bug: binary input in v0.11.0

See original GitHub issue

After update to latest version v0.11.0 card refuse to use day/night binari sensor.

message

mini-graph-card
Entity not available: input_number.nighttime

In version v0.10.0 there was no problem.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:11

github_iconTop GitHub Comments

1reaction
ildar170975commented, Jan 23, 2022

But how is changed from sensor.day_night to input_number.nighttime?

Use the same entity in the card as you specified in configuration for this purpose. Otherwise the issue is meaningless and is not supposed to be even raised.

What you can do is:

  1. Define a template sensor:
sensor:
  - platform: template
    sensors:
      night:
        icon_template: mdi:power-sleep
        value_template: >-
          {% if is_state('sun.sun','above_horizon') -%}
          {{ 0 | int }}
          {%- else -%}
          {{ 1 | int }}
          {%- endif %}
  1. Add the sensor on the graph as a background:
      - entity: sensor.night
        color: some semi transparent color (darkish for light theme)
        unit: ''
        show_state: false
        show_indicator: false
        show_graph: true
        show_line: false
        show_fill: true
        show_points: false
        show_legend: false
        state_adaptive_color: false
        fixed_value: false
        aggregate_func: last
        y_axis: secondary

Surely you may use a binary_sensor alternatively + state_map but the state_map is currently not supported per-entity and you’ll see warnings in the browser then.

1reaction
jlsjonascommented, Jan 23, 2022

You would need something like a state_map to do this within mini-graph-card https://github.com/kalkih/mini-graph-card#non-numeric-sensor-states

Could it be that you accidentally deleted your input_number.nighttime which was providing day/night as a simple 1/0 numeric value?

p.s.: Binary input doesn’t have ideal support yet (#505) but your case just seems to be a string; not a binary

Read more comments on GitHub >

github_iconTop Results From Across the Web

Possible Bug Tensorflow in v0.11 - Invalid argument: input ...
Starting from a working ML.NET sample scoring the standard TensorFlow Inception v3 model (it was working on 0.9 and 0.10) after migrating to ......
Read more >
Upgrade to v0.11.0 - WasmEdge Runtime
Supported the user-defined error code in host functions. Developers can use the new API wasmedge.NewResult() to generate a wasmedge.Result struct with wasmedge.
Read more >
Scenic.Primitive.Style.Input — Scenic v0.11.0-beta.0
The data for the input style is the type of input you want to receive when the cursor is positioned over the primitive....
Read more >
Bug listing with status RESOLVED with resolution FIXED as at ...
Bug listing with status RESOLVED with resolution FIXED as at 2022/12/24 19:46:07.
Read more >
Default DataChecks in AutoML — EvalML 0.11.0 documentation
DefaultDataChecks when ; automl.search() is called to check that inputs are valid before running the search and fitting pipelines. Currently, ; DefaultDataChecks ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found