cryptk / cryptk/haomnilogic-local

[BUG] - Constant Flapping to Unavailable (possibly same as #234)

Open
#271 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
47
Forks
22
Avg merge
1m
Merged PRs (30d)
1

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues
- [x] I have added [diagnostic data](https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics) file as an upload at the end of the form or. I understand that the ability to assist IS limited without it (please upload diagnostics if at all possible).

- [x] I have either added [debug logs](https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging) or to the section marked "Debug Logs" or attached the debug log file as an upload at the end of the form. I understand that the ability to assist IS limited without it (add debug logs if at all possible).

### Bug Description

The integration for all entities flaps back and forth from unavailable to the proper status. I suspect this is similar to #234. This is on wifi, ethernet not possible. If possible I'd like to be able to hold the current status through more retries. As it stands most of the unavailable statuses resolve within 120 seconds.

### Reproduction Steps

1.
2.
3.
...

### Debug Logs

```text

```

### How is your OmniLogic connected to the network?

Wi-Fi

### Attachments

[config_entry-omnilogic_local-01KJ4F5DQ4J8MSTVHHVTA9P3H4.json](https://github.com/user-attachments/files/29970919/config_entry-omnilogic_local-01KJ4F5DQ4J8MSTVHHVTA9P3H4.json)
[Screenshot 2026-07-13 102531.jpg](https://github.com/user-attachments/assets/2001000a-80c8-4e09-aa78-4ea39d706e2e)
[home-assistant_omnilogic_local_2026-07-13T14-43-14.901Z.log](https://github.com/user-attachments/files/29971135/home-assistant_omnilogic_local_2026-07-13T14-43-14.901Z.log)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the attached diagnostic JSON and debug log, then compare the behavior with issue #234. Identify what causes the OmniLogic entities to alternate between unavailable and their normal status over Wi-Fi, and verify that the entities remain available through the reported retry period without introducing incorrect state.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.