You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: