-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
- Confirm the panel and Home Assistant are on networks that can reach each other.
- Check the panel IP on the OLED or in your router.
- Use Add by IP in the Manager when Windows or the network blocks mDNS.
- Confirm TCP port 6053 is allowed between the panel and Home Assistant.
Connect the Manager to Home Assistant, select a discovered panel, and wait for its matching saved device profile to load. A preflashed panel without the matching API key cannot be added securely by the Manager. Use the key from that panel's original configuration or reflash it as a new panel.
The core ESPHome integration and Device Builder are separate. First add the panel to Home Assistant, then select it in the Manager and choose Add to Device Builder. The Manager will not overwrite an unmanaged YAML project with the same name.
- Confirm VCC and GND polarity.
- Confirm SDA is GPIO21 and SCL is GPIO22.
- Check ESPHome logs for an I2C device at address
0x3C. - Confirm the display is CH1115 or SH1106 compatible. An SSD1306 needs a different model setting.
- Confirm both Home Assistant entity IDs exist.
- Confirm their states are numeric, not
unknownorunavailable. - Confirm the ESPHome API connection to Home Assistant is active.
- Review and reinstall the panel configuration after changing sensor sources.
- Use the panel's direct IP instead of its
.localhostname. - Keep the computer and panel on the same reachable LAN.
- Confirm the correct OTA credentials belong to the selected panel.
- Do not interrupt power during an active installation.
Keep the CH1115 display in SH1106 128x64 compatibility mode and use the supplied controller-native rotation logic. The project keeps one clear edge pixel in both orientations.
Open a GitHub issue with the Manager version, panel firmware version, ESPHome version, and redacted logs. Never post Wi-Fi passwords, Home Assistant tokens, API keys, OTA passwords, or fallback AP credentials.