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

[Bug] HA log full of errors when mikrotik custom integraton installed #44

Open
Dillton opened this issue Aug 18, 2024 · 17 comments
Open
Labels
bug Something isn't working

Comments

@Dillton
Copy link

Dillton commented Aug 18, 2024

Describe the issue

Hi, I just added portainer and I see these errors in log:
Logger: homeassistant.util.logging
Source: util/logging.py:95
First occurred: 15:18:05 (36 occurrences)
Last logged: 15:19:04

Exception in async_update_controller when dispatching 'update_sensors': (<custom_components.portainer.coordinator.PortainerCoordinator object at 0x7fea06b19b80>,) Traceback (most recent call last): File "/config/custom_components/mikrotik_router/entity.py", line 121, in async_update_controller data = coordinator.data[entity_description.data_path] ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'health'
Exception in async_update_controller when dispatching 'update_sensors': (<custom_components.portainer.coordinator.PortainerCoordinator object at 0x7fea06b19b80>,) Traceback (most recent call last): File "/config/custom_components/mikrotik_router/entity.py", line 121, in async_update_controller data = coordinator.data[entity_description.data_path] ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'ups'
Exception in async_update_controller when dispatching 'update_sensors': (<custom_components.portainer.coordinator.PortainerCoordinator object at 0x7fea06b19b80>,) Traceback (most recent call last): File "/config/custom_components/mikrotik_router/device_tracker.py", line 75, in async_update_controller data = coordinator.data[entity_description.data_path] ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'host'
Exception in async_update_controller when dispatching 'update_sensors': (<custom_components.portainer.coordinator.PortainerCoordinator object at 0x7fea06b19b80>,) Traceback (most recent call last): File "/config/custom_components/mikrotik_router/entity.py", line 121, in async_update_controller data = coordinator.data[entity_description.data_path] ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'script'
Exception in async_update_controller when dispatching 'update_sensors': (<custom_components.portainer.coordinator.PortainerCoordinator object at 0x7fea06b19b80>,) Traceback (most recent call last): File "/config/custom_components/mikrotik_router/entity.py", line 121, in async_update_controller data = coordinator.data[entity_description.data_path] ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'fw-update'

Otherwise everything seems to be working.

How to reproduce the issue

I guess to have installed portainer and mikrotik custom integration together?

Expected behavior

Clean logs.

Screenshots

Software versions

  • Home Assistant version: HA 2024.8.2
  • Portainer integration version: v1.0.2
  • Portainer software version: 2.20.1

Diagnostics data

Traceback/Error logs

Additional context

@Dillton Dillton added the bug Something isn't working label Aug 18, 2024
@Dillton Dillton changed the title [Bug] [Bug] HA log full of errors when mikrotik custom integraton installed Aug 18, 2024
Copy link

github-actions bot commented Sep 2, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Sep 2, 2024
@Dillton
Copy link
Author

Dillton commented Sep 2, 2024

Still a problem

@github-actions github-actions bot removed the stale label Sep 3, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Sep 18, 2024
@Dillton
Copy link
Author

Dillton commented Sep 18, 2024

Still present

Copy link

github-actions bot commented Oct 3, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Oct 3, 2024
@Dillton
Copy link
Author

Dillton commented Oct 3, 2024

still present

@github-actions github-actions bot removed the stale label Oct 4, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Oct 18, 2024
@Dillton
Copy link
Author

Dillton commented Oct 18, 2024

not stale

@github-actions github-actions bot removed the stale label Oct 19, 2024
Copy link

github-actions bot commented Nov 3, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Nov 3, 2024
@Dillton
Copy link
Author

Dillton commented Nov 3, 2024

still issue

@github-actions github-actions bot removed the stale label Nov 4, 2024
@PavelD
Copy link
Contributor

PavelD commented Nov 8, 2024

I have exactly the same issue :-(

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Nov 23, 2024
@Dillton
Copy link
Author

Dillton commented Nov 23, 2024

still issue

@github-actions github-actions bot removed the stale label Nov 24, 2024
Copy link

github-actions bot commented Dec 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Dec 8, 2024
@Dillton
Copy link
Author

Dillton commented Dec 9, 2024

still issue

@github-actions github-actions bot removed the stale label Dec 10, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Dec 25, 2024
@Dillton
Copy link
Author

Dillton commented Dec 26, 2024

still issue

@github-actions github-actions bot removed the stale label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants