I may have figured it out:
Set driver to "Device".
Delete scheduled jobs.
Set driver back to original.
1 Like
That’s why I set up the default time for the automatic switching off of the Debug logs to 24 hours, instead of 30 minutes. Half an hour is not enough time to track issues like battery reporting as an example.
Have you considered moving to Texas? we only get snow every 9 or 10 years. hahaha
@mike.maxwell , I managed to capture a debug log of the event.
I included some later entries because I thought they looked weird.
2 Likes
The 82% value seems invalid and will be removed in the next platform release.
The temperature value is valid, so I can't do anything about that.
2 Likes
Any idea what all that stuff at the top of the snip means?
its ZDO traffic, normal and can be ignored.
1 Like
Thanks for following up on this issue.
1 Like
I tried that last night, thinking maybe it could have an effect on the erroneous level readings.
It seems to have stopped reporting temperature, as designed, for 12 hours or so.
Alas, I got two 82% readings as well, so no effect.
I tried 10 minute reporting intervals overnight.
It was worse than turning it off, as far as erroneous readings go.
The best setting so far has been the default, .5C change.
The temperature reporting interval settings at least work though, and that's a step up from most of the zigbee stuff I've seen.
Can you explain to mean in detail how you created the attribute tile for the level sensor?
I just remembered, under the tutelage of @Big_Bruin , I went into Dashboard/Advanced/CSS and put in the following. There's something additional for kwh for another tile, so ignore that. You have to reference your own tile numbers.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
