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

High CPU consumption after Bluetti shut-down #44

Open
PortInnovator opened this issue Mar 4, 2024 · 2 comments
Open

High CPU consumption after Bluetti shut-down #44

PortInnovator opened this issue Mar 4, 2024 · 2 comments

Comments

@PortInnovator
Copy link

When I updated to HAOS 12 and HA Core 2024.2.4 I noticed that the CPU-level ist raising to about 20% (from close to zero) after shut-down of my Bluetti P200MAX or when the BT-Connection is broken. After restart of bluetti2mqtt everything is alright again.

<img width="978" alt="image

@PortInnovator PortInnovator changed the title High CPU-Level after Bluetti shut-down High CPU consumption after Bluetti shut-down Mar 5, 2024
@nevaleft77
Copy link

I have the same issue with the addon since an update. As soon as my EB3A turns off, the addon completely exhaust one CPU core, like its stuck in a endless loop. But there are no relevant infos about that in the addon logs.

@nevaleft77
Copy link

The delayed reconnect does not seem to work, i guess its a bug in the original bluetti2mqtt tool and not this addon itself.
2024-03-07 19:58:57 DEBUG Connecting to device @ F5:11:3A:31:53:A9 2024-03-07 19:58:57 DEBUG Connecting to BlueZ path /org/bluez/hci0/dev_F5_11_3A_31_53_A9 2024-03-07 19:58:57 DEBUG _cleanup_all(/org/bluez/hci0/dev_F5_11_3A_31_53_A9) 2024-03-07 19:58:57 DEBUG Error connecting to device F5:11:3A:31:53:A9: Not found 2024-03-07 19:58:57 DEBUG Connecting to device @ F5:11:3A:31:53:A9 2024-03-07 19:58:57 DEBUG Connecting to BlueZ path /org/bluez/hci0/dev_F5_11_3A_31_53_A9 2024-03-07 19:58:57 DEBUG _cleanup_all(/org/bluez/hci0/dev_F5_11_3A_31_53_A9) 2024-03-07 19:58:57 DEBUG Error connecting to device F5:11:3A:31:53:A9: Not found 2024-03-07 19:58:57 DEBUG Connecting to device @ F5:11:3A:31:53:A9 2024-03-07 19:58:57 DEBUG Connecting to BlueZ path /org/bluez/hci0/dev_F5_11_3A_31_53_A9 2024-03-07 19:58:57 DEBUG _cleanup_all(/org/bluez/hci0/dev_F5_11_3A_31_53_A9) 2024-03-07 19:58:57 DEBUG Error connecting to device F5:11:3A:31:53:A9: Not found 2024-03-07 19:58:57 DEBUG Connecting to device @ F5:11:3A:31:53:A9 2024-03-07 19:58:57 DEBUG Connecting to BlueZ path /org/bluez/hci0/dev_F5_11_3A_31_53_A9 2024-03-07 19:58:57 DEBUG _cleanup_all(/org/bluez/hci0/dev_F5_11_3A_31_53_A9) 2024-03-07 19:58:57 DEBUG Error connecting to device F5:11:3A:31:53:A9: Not found 2024-03-07 19:58:57 DEBUG Connecting to device @ F5:11:3A:31:53:A9 2024-03-07 19:58:57 DEBUG Connecting to BlueZ path /org/bluez/hci0/dev_F5_11_3A_31_53_A9 2024-03-07 19:58:57 DEBUG _cleanup_all(/org/bluez/hci0/dev_F5_11_3A_31_53_A9) 2024-03-07 19:58:57 DEBUG Error connecting to device F5:11:3A:31:53:A9: Not found 2024-03-07 19:58:57 DEBUG Connecting to device @ F5:11:3A:31:53:A9

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