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

systemmonitor - network_in resets (sort of) after HA restarts #34804

Closed
agneevX opened this issue Apr 28, 2020 · 3 comments
Closed

systemmonitor - network_in resets (sort of) after HA restarts #34804

agneevX opened this issue Apr 28, 2020 · 3 comments

Comments

@agneevX
Copy link

agneevX commented Apr 28, 2020

The problem

The network_in integration inside systemmonitor resets (to random values) each time HA is restarted.
Oddly enough, network_out behaves correctly...

In this screenshot, you can see that network_in did not reset to 0, but in earlier cases, it reset to 0.

image

Environment

Raspberry Pi 4B (4GB) running Raspbian Buster - HA venv install.

  • Home Assistant Core release with the issue: 0.108.5
  • Last working Home Assistant Core release (if known):
  • Operating environment (Home Assistant/Supervised/Docker/venv):
  • Integration causing this issue: systemmonitor
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/systemmonitor/

Problem-relevant configuration.yaml

  - platform: systemmonitor
    resources:
      - type: network_in
        arg: eth0
      - type: network_out
        arg: eth0

Traceback/Error logs

Additional information

@stale
Copy link

stale bot commented Jul 27, 2020

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 27, 2020
@agneevX
Copy link
Author

agneevX commented Jul 27, 2020

This ain't fixed, my bot.

@stale stale bot removed the stale label Jul 27, 2020
@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

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

No branches or pull requests

2 participants