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

Updating state for sensor.ltibber - please creat a bug report #50

Open
5 tasks done
j1gg3 opened this issue Oct 7, 2024 · 1 comment
Open
5 tasks done

Updating state for sensor.ltibber - please creat a bug report #50

j1gg3 opened this issue Oct 7, 2024 · 1 comment

Comments

@j1gg3
Copy link

j1gg3 commented Oct 7, 2024

Checklist

  • I have followed the install preparation procedure - including the verification part I, II & III.
  • I have installed the latest release (or BETA) version of the integration and home assistant.
  • I have prepared DEBUG log output (for technical issues) | In most of the cases of a technical error/issue I would have the need to ask for DEBUG log output of the integration. There is a short tutorial/guide 'How to provide DEBUG log' here
  • I am aware that rotating the tibber pulse reading head anti clockwise can improve data quality | See this user comment and the next comment as well
  • I confirm it's really an issue | In the case that you want to understand the functionality of a certain feature/sensor Please be so kind and make use if the discussion feature of this repo (and do not create an issue) - TIA

Add a description

I am just raising that report as requested.

Add your DEBUG log output

Logger: homeassistant.helpers.entity
Quelle: helpers/entity.py:1180
Erstmals aufgetreten: 08:02:49 (1 Vorkommnisse)
Zuletzt protokolliert: 08:02:49

Updating state for sensor.ltibber_0100010800ff_in_k (<class 'custom_components.tibber_local.sensor.TibberLocalSensor'>) took 0.436 seconds. Please create a bug report at https://github.com/marq24/ha-tibber-pulse-local/issues
@marq24
Copy link
Owner

marq24 commented Oct 7, 2024

thanks for your report - but I don't see anything that I can fix here...

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