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

Lightning Count toggles briefly to unknown at GMT 0:00 (midnight) #55

Open
StormyKnight17 opened this issue Jun 2, 2022 · 3 comments
Open

Comments

@StormyKnight17
Copy link

Clipboard01

Note my Timezone is +10 so 10am is UTC Midnight for me.

I found this by using an automation trigger for the counter of From: 0 To: (BLANK)
The idea was to trigger on change from 0 to any other number, but it seems that it goes to 'unknown' at this time of day each day. It doesn't do it at any other time.

Can anyone else confirm this is happening for them?

I have an automation that advises me on any change of the counter value for testing. It is triggering each day at UTC 0:00

alias: TEMP - Lightning Counter Monitor
description: ''
trigger:
  - platform: state
    entity_id:
      - sensor.blitzortung_lightning_counter
condition:
  - condition: not
    conditions:
      - condition: numeric_state
        entity_id: sensor.blitzortung_lightning_counter
        above: '0'
action:
  - service: notify.mobile_app_iphone
    data_template:
      message: |
        {{states('sensor.blitzortung_lightning_counter')}} 
      title: Lightning Count Change In Value
mode: single
@snarlingllama
Copy link

Same issue.

@snarlingllama
Copy link

Curious though, shouldn't your not condition be set to below 1?

@StormyKnight17
Copy link
Author

Curious though, shouldn't your not condition be set to below 1?

This is just a test automation. It triggers when the state changes anytime except if the state is above 0 i.e. lightning is about.

So it will trigger anytime it changes to undefined or to zero or to any other state not equal to 1 or higher number.

It was to see what & when the non numeric states were occurring to see if there was a pattern & how long it stayed undefined for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants