Scheduler card/custom component

Cadster · September 30, 2020, 3:53pm

When i debug i get:

Fout tijdens het ophalen van een originele bron: NetworkError when attempting to fetch resource.
Bron-URL: webpack:///chunk.27e04144babbf2091a6d.js

Gepauzeerd bij uitzondering
NotFoundError: IDBDatabase.transaction: 'mdi-icon-store' is not a known object store name

Is this something you can work with?

neliss · September 30, 2020, 3:58pm

Niet echt
Maar komt goed

neliss · September 30, 2020, 4:23pm

@Cadster I fixed it in release v1.6.1.
The issue affected fan, input_select and media_player entities as far as I can see.

Cadster · September 30, 2020, 4:36pm

Great! Thanks for the quick fix!

Ih8rain2 · September 30, 2020, 4:49pm

I am using IOS-Dark-mode custom theme which can be installed by HACS.

I added a background picture in my Lovelace.yaml and adapted the transparency in the ios-dark-mode just as Kendell is indicating.

ASNNetworks · September 30, 2020, 5:19pm

@neliss so far I’m really loving this new update! One thing though, I notice the docs are confusing with some variables, especially customize. In the overview it states you need to use customize

However, further down, these examples are given:

This one says entities (which is the old one I believe) and doesn’t work, the card throws an error.

entities:
  light.my_lamp:
    name: "Dining light"
    icon: ceiling-light
    actions:
      - service: turn_on
        service_data:
          brightness: 100 # note that brightness is from 0-255 so 100 = 40%
        name: "Turn on at 40%"
        icon: lightbulb-on-outline

This one uses customize like the overiew instead of entities, but the variables under the entity is in a list with a - sign (see service)

customize:
  fan.xiaomi_purifier:
    - service: xiaomi_miio.fan_set_favorite_level
      name: "set speed"
      variable:
        field: level
        name: "Speed"
        min: 1
        max: 16

And then this one doesn’t have the variables under the entity in a list.

customize:
  climate.my_thermostat:
    name: My thermostat
    icon: thermometer
    actions:
      - service: set_hvac_mode
        name: Set mode
        icon:
        variable:
          field: hvac_mode
          name: Operation mode
          options:
            - value: heat
              icon: fire
            - value: cool
              icon: snowflake
            - value: 'off'
              icon: power

I tried different stuff, but I can’t seem to get customize work. This is what I tried now:

customize:
  light.woonkamer_plafond:
    name: "Woonkamer Plafond"

Perhaps I’m just missing something very obvious. Can you clarify this for me?

neliss · September 30, 2020, 5:35pm

Honestly I didn’t have the time to test things properly.
I only worked a couple of hours on this update and most went into the UI editor.
But I’m fine with people reporting bug issues…
I will patch them in the next couple of days.

As long as things stay between acceptable annoyance levels.
If not, then I would like to hear it.
I could choose a more slow and steady way of working as well, but I like to give quick updates to you guys

neliss · September 30, 2020, 5:38pm

And yes. I know which problem you are having.
“Which of the turn on’s do I need?”
Capture2

neliss · September 30, 2020, 6:09pm

@ASNNetworks Release v1.6.2 is dedicated to you
I also fixed your remarks in the readme.

guims78 · September 30, 2020, 6:56pm

Very good Job.
I think scheduler-card will be as effective as “agenda” in Jeedom.

Canaletto · September 30, 2020, 7:02pm

Ca c’était bien dans Jeedom… (That was good in Jeedom…)

Currently I manage all my thermostats with either Automations and inputs, or on another installation with Google Calendar, both are ok. But an integrated agenda will be much better, especially when it has the conditions, workday, etc…

ASNNetworks · September 30, 2020, 7:30pm

You are amazing! I will update tomorrow morning and try it out!

Edit: couldn’t wait. It works great now!

Ih8rain2 · September 30, 2020, 10:53pm

I am going backwards guys. What has changed in the meanwhile that I get this:

Ok sorry. I didn’t read the thread. I am on it now

And so far pretty smooth

guims78 · October 1, 2020, 7:17am

Ce sont tes articles qui m’ont fait basculer vers Home Assistant.
(entre autres)

tonioa · October 1, 2020, 9:51am

HI @neliss

Thanks for your work

trying to set up it but i am block

- type: 'custom:scheduler-card'
  title: Planification
  discover_existing: true
  standard_configuration: true
  time_step: 1 
  groups:
    - name: "Lumières"
      icon: lightbulb-on-outline 
      include:
        - light.bureau    
    - name: "Volets"
      icon: window-shutter

I didn’t see the light.bureau appear on my group “Lumières” ?

neliss · October 1, 2020, 10:09am

You should include the entities first to the card, then to the group.
This is because groups are optional (they are automatically generated for you if you do don’t configure)

- type: 'custom:scheduler-card'
  title: Planification
  discover_existing: true
  standard_configuration: true
  time_step: 1 
  include:
    - light.bureau
  groups:
    - name: "Lumières"
      icon: lightbulb-on-outline 
      include:
        - light.bureau

tonioa · October 1, 2020, 10:30am

Thanks it’s ok

Canaletto · October 1, 2020, 2:08pm

A small bug…
I have two themostats

climate.climate_chb
climate.climate_chbs

If I only select the first one, the second one appears too, a bit like a wilcard…

Isablend · October 1, 2020, 2:44pm

Seems to have solved the issue with titles for multiple schedule cards - thanks.

neliss · October 1, 2020, 3:04pm

This is not really a bug.
If an entity_id contains the word that you provide in the include and it starts with it, it is allowed.
Perhaps this is not ideal though, I could change it to only check for the domain or the complete entity_id.