Flood of ESPHome ping logs in Hubitat

37kdeep · August 18, 2026, 7:55pm

Continuing the discussion from Firmware update:

How do I do that?

37kdeep · August 18, 2026, 8:53pm

I don’t see this anywhere on my mobile app.

37kdeep · August 18, 2026, 11:45pm

Found this on Gemini. It answers my questions.

No, you cannot update a non-Pro Konnected Alarm Panel (6-zone) to Ethernet or v1.8 firmware.

The non-Pro board and the Alarm Panel Pro are entirely different physical hardware platforms:

Hardware Limitations: The non-Pro Konnected board relies on an ESP8266 microcontroller chip, which only supports 2.4 GHz Wi-Fi. It completely lacks the physical RJ45 Ethernet port, PHY transceiver chip (such as the RTL8201 introduced on the Pro v1.8), and Power-over-Ethernet circuitry present on the Pro boards.
Firmware Compatibility: The v1.8 firmware build is created explicitly for the Alarm Panel Pro board hardware. Attempting to flash Pro v1.8 firmware onto a non-Pro board will result in a flash error or render the non-Pro board unbootable, as the ESP8266 cannot run ESP32/Ethernet-specific binaries.

The impetus for trying to update my Alarm Panel board was to be able to change it’s logging status in Hubitat from full to error. My Hubitat logs are full of useless ESPHome log entries.

37kdeep · August 19, 2026, 8:13am

Any suggestions on how to stop these logs would be welcome. I am getting the following in my Hubitat log many times a day. Multiple attempts (>10) to change the logging with the Konnected app, updating firmware, results in unresponsive boards that require flashing again. Because of the location of the boards, I have to disconnect them from my system and bring them to my desktop to do the USB flashing, again…..

37kdeep · August 25, 2026, 7:52pm

Do I need to toss out both of my non-pro boards and upgrade to the Pro in order to get the hubitat log spamming under control? The boards work fine. But the logging has exploded recently. I have read and read and read on firmware updates and device settings in Hubitat and I continue to get tons of logs like the above and even more PING entries for both boards. I have attempted every firmware/ESPHome update that I can find. I am getting very frustrated with all of this. Hubitat device info for both boards below.

37kdeep · August 28, 2026, 12:29am

WOW! 60 views……………….

nate · August 29, 2026, 1:33pm

Those logs in Hubitat are not coming from the Konnected panel. They’re coming from the ESPHomeApiHelper library. The library was updated about a month ago to quiet down the noisy communication logging that was added by an open-source contributor.

Make sure you’ve updated the library in your Hubitat instance, and that debug logging toggle is off.

github.com/bradsjm/hubitat-public

ESPHome/ESPHome-API-Library.groovy

main

/**
 *  MIT License
 *  Copyright 2022 Jonathan Bradshaw (jb@nrgup.net)
 *
 *  Permission is hereby granted, free of charge, to any person obtaining a copy
 *  of this software and associated documentation files (the "Software"), to deal
 *  in the Software without restriction, including without limitation the rights
 *  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 *  copies of the Software, and to permit persons to whom the Software is
 *  furnished to do so, subject to the following conditions:
 *
 *  The above copyright notice and this permission notice shall be included in all
 *  copies or substantial portions of the Software.
 *
 *  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 *  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 *  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 *  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 *  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 *  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

This file has been truncated. show original

Also see:

37kdeep · August 29, 2026, 2:06pm

Nate, thanks for helping me here. I have updated the ESPHome/ESPHome-API-Library.groovy and I have turned off the debug logging for both of my 6-zone boards. Also, I used the app to update my firmware on both boards (I THINK it worked) and set the Logging to Warn for both. Will that take care of the pings and the ESPHome log entries?

37kdeep · August 29, 2026, 2:35pm

Still getting lots of ping log entries. Is this correct?

37kdeep · August 29, 2026, 2:56pm

Nate, I don’t know what else to do. I did as you suggested above. Actually, I had already tried that. And yet, here are my most recent logs….

37kdeep · August 29, 2026, 8:42pm

This is NOT fixed or I am missing something…

37kdeep · August 29, 2026, 10:11pm

Ok, I deleted the Alarm Panel driver and ESPHome/ESPHome-API-Library.groovy and re-installed them from the site above. I have turned off all of the log switches on both cards. And I am still getting a flood of logs.

nate · August 30, 2026, 12:30am

That “INFO Konnected XX is online: ping response” line should only show once after the device comes online after being offline. Which makes it seem like your device is constantly going offline and then online again. That’s why you would be seeing it repeatedly

I would suggest turning on debug logging temporarily to help figure out why it’s going offline so frequently. That’s not normal.

37kdeep · August 30, 2026, 12:36am

Could it have something to do with a weak wifi signal? WiFi Signal RSSI -67 -70 both boards.

nate · August 30, 2026, 12:49am

Definitely could be. Please share some logs with the debug toggle enabled and that might give us more clues.

37kdeep · August 30, 2026, 1:26am

dev:25042026-08-29 21:22:14.743debug
ESPHome scheduling healthCheck in 32s
dev:25042026-08-29 21:22:14.741debug
ESPHome send msg type #8 with [:]
dev:24952026-08-29 21:21:59.988debug
ESPHome scheduling healthCheck in 47s
dev:24952026-08-29 21:21:59.986debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:78602.7890625, hasState:true]
dev:24952026-08-29 21:21:59.269debug
ESPHome scheduling healthCheck in 38s
dev:24952026-08-29 21:21:59.267debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]
dev:24952026-08-29 21:21:59.237debug
ESPHome scheduling healthCheck in 57s
dev:24952026-08-29 21:21:59.235debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]
dev:25042026-08-29 21:21:41.084debug
ESPHome scheduling healthCheck in 51s
dev:25042026-08-29 21:21:41.082debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-68, hasState:true]
dev:25042026-08-29 21:21:41.054debug
ESPHome scheduling healthCheck in 56s
dev:25042026-08-29 21:21:41.052debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:64, hasState:true]
dev:25042026-08-29 21:21:40.154debug
ESPHome scheduling healthCheck in 34s
dev:25042026-08-29 21:21:40.152debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:48123.3515625, hasState:true]
dev:24952026-08-29 21:21:31.109debug
ESPHome scheduling healthCheck in 56s
dev:24952026-08-29 21:21:31.107debug
ESPHome send msg type #8 with [:]
dev:25042026-08-29 21:21:14.607debug
ESPHome scheduling healthCheck in 31s
dev:25042026-08-29 21:21:14.572debug
ESPHome send msg type #8 with [:]
dev:24952026-08-29 21:20:59.986debug
ESPHome scheduling healthCheck in 36s
dev:24952026-08-29 21:20:59.984debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:78542.7890625, hasState:true]
dev:24952026-08-29 21:20:59.271debug
ESPHome scheduling healthCheck in 45s
dev:24952026-08-29 21:20:59.269debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]
dev:24952026-08-29 21:20:59.241debug
ESPHome scheduling healthCheck in 59s
dev:24952026-08-29 21:20:59.239debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]
dev:25042026-08-29 21:20:41.217debug
ESPHome scheduling healthCheck in 42s
dev:25042026-08-29 21:20:41.215debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-68, hasState:true]
dev:25042026-08-29 21:20:41.191debug
ESPHome scheduling healthCheck in 37s
dev:25042026-08-29 21:20:41.189debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:64, hasState:true]
dev:25042026-08-29 21:20:40.139debug
ESPHome scheduling healthCheck in 60s
dev:25042026-08-29 21:20:40.137debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:48063.3515625, hasState:true]
dev:24952026-08-29 21:20:31.123debug
ESPHome scheduling healthCheck in 57s
dev:24952026-08-29 21:20:31.107debug
ESPHome scheduling healthCheck in 53s
dev:24952026-08-29 21:20:31.105debug
ESPHome ping response received — rescheduling healthCheck
dev:24952026-08-29 21:20:31.103debug
ESPHome received: [platform:network, type:state, state:online, reason:ping response]
dev:24952026-08-29 21:20:31.101info
Konnected 64 is online: ping response
dev:24952026-08-29 21:20:31.099trace
ESPHome executing espHomePingResponse
dev:24952026-08-29 21:20:31.009debug
ESPHome send msg type #7 with [:]
dev:24952026-08-29 21:20:30.992debug
ESPHome sending keepalive ping
dev:24952026-08-29 21:20:30.990debug
ESPHome healthCheck: online=true queueEmpty=true
dev:25042026-08-29 21:20:14.421debug
ESPHome scheduling healthCheck in 55s
dev:25042026-08-29 21:20:14.419debug
ESPHome send msg type #8 with [:]
dev:24952026-08-29 21:19:59.975debug
ESPHome scheduling healthCheck in 31s
dev:24952026-08-29 21:19:59.973debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:78482.7890625, hasState:true]
dev:24952026-08-29 21:19:59.259debug
ESPHome scheduling healthCheck in 60s
dev:24952026-08-29 21:19:59.257debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]
dev:24952026-08-29 21:19:59.224debug
ESPHome scheduling healthCheck in 39s
dev:24952026-08-29 21:19:59.222debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]
dev:25042026-08-29 21:19:41.081debug
ESPHome scheduling healthCheck in 51s
dev:25042026-08-29 21:19:41.079debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-68, hasState:true]
dev:25042026-08-29 21:19:41.046debug
ESPHome scheduling healthCheck in 33s
dev:25042026-08-29 21:19:41.044debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:64, hasState:true]
dev:25042026-08-29 21:19:40.146debug
ESPHome scheduling healthCheck in 52s
dev:25042026-08-29 21:19:40.144debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:48003.3515625, hasState:true]
dev:24952026-08-29 21:19:31.706debug
ESPHome scheduling healthCheck in 39s
dev:24952026-08-29 21:19:31.705debug
ESPHome send msg type #8 with [:]
dev:25042026-08-29 21:19:14.281debug
ESPHome scheduling healthCheck in 52s
dev:25042026-08-29 21:19:14.279debug
ESPHome send msg type #8 with [:]
dev:24952026-08-29 21:18:59.994debug
ESPHome scheduling healthCheck in 52s
dev:24952026-08-29 21:18:59.992debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:78422.7890625, hasState:true]
dev:24952026-08-29 21:18:59.276debug
ESPHome scheduling healthCheck in 49s
dev:24952026-08-29 21:18:59.274debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]
dev:24952026-08-29 21:18:59.242debug
ESPHome scheduling healthCheck in 46s
dev:24952026-08-29 21:18:59.240debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]
dev:25042026-08-29 21:18:41.089debug
ESPHome scheduling healthCheck in 47s
dev:25042026-08-29 21:18:41.086debug
ESPHome received: [type:state, platform:sensor, key:2654868797, state:-67, hasState:true]
dev:25042026-08-29 21:18:41.052debug
ESPHome scheduling healthCheck in 48s
dev:25042026-08-29 21:18:41.050debug
ESPHome received: [type:state, platform:sensor, key:513204495, state:66, hasState:true]
dev:25042026-08-29 21:18:40.153debug
ESPHome scheduling healthCheck in 49s
dev:25042026-08-29 21:18:40.151debug
ESPHome received: [type:state, platform:sensor, key:1324261225, state:47943.3515625, hasState:true]
dev:24952026-08-29 21:18:31.588debug
ESPHome scheduling healthCheck in 37s
dev:24952026-08-29 21:18:31.586debug
ESPHome send msg type #8 with [:]
dev:24952026-08-29 21:13:31.076info
Konnected 64 is online: ping response
dev:24952026-08-29 21:01:32.200info
Konnected 64 is online: ping response
dev:25042026-08-29 21:01:12.199info
Konnected 65 is online: ping response
dev:24952026-08-29 20:57:32.050info
Konnected 64 is online: ping response
dev:25042026-08-29 20:54:12.180info
Konnected 65 is online: ping response
dev:25042026-08-29 20:51:12.270info
Konnected 65 is online: ping response
dev:24952026-08-29 20:48:32.019info
Konnected 64 is online: ping response
dev:25042026-08-29 20:48:15.195info
Konnected 65 is online: ping response
dev:24952026-08-29 20:29:31.031info
Konnected 64 is online: ping response
dev:25042026-08-29 20:24:13.189info
Konnected 65 is online: ping response
dev:24952026-08-29 20:20:31.034info
Konnected 64 is online: ping response
dev:24952026-08-29 20:19:32.094info
Konnected 64 is online: ping response
dev:24952026-08-29 20:11:32.981info
Konnected 64 is online: ping response
dev:25042026-08-29 20:03:12.142info
Konnected 65 is online: ping response
dev:24952026-08-29 19:58:32.043info
Konnected 64 is online: ping response
dev:24952026-08-29 19:54:32.927info
Konnected 64 is online: ping response
dev:25042026-08-29 19:51:12.532info
Konnected 65 is online: ping response
dev:25042026-08-29 19:50:15.164info
Konnected 65 is online: ping response
dev:25042026-08-29 19:37:12.165info
Konnected 65 is online: ping response
dev:24952026-08-29 19:19:31.024info
Konnected 64 is online: ping response
dev:25042026-08-29 19:17:13.184info
Konnected 65 is online: ping response
dev:24952026-08-29 19:14:32.036info
Konnected 64 is online: ping response
dev:25042026-08-29 19:14:16.224info
Konnected 65 is online: ping response
dev:24952026-08-29 19:13:45.112info
Konnected 64 is online: ping response
dev:25042026-08-29 19:11:19.218info
Konnected 65 is online: ping response
dev:24952026-08-29 19:10:47.886info
Konnected 64 is online: ping response
dev:25042026-08-29 19:10:20.103info
Subscribing to ESPHome device states
dev:25042026-08-29 19:10:20.101info
Subscribing to ESPHome INFO logging
dev:25042026-08-29 19:10:20.099info
Subscribing to ESPHome HA services
dev:25042026-08-29 19:10:19.799info
Konnected 65 is online: connection completed
dev:25042026-08-29 19:10:19.797info
ESPHome API 1.15 fast path — no ConnectResponse expected
dev:25042026-08-29 19:10:19.795info
ESPHome sending connect request (no password)
dev:25042026-08-29 19:10:19.793info
ESPHome device name: konnected-2cf43256afa8
dev:25042026-08-29 19:10:19.791info
ESPHome server info: 2026.8.1
dev:25042026-08-29 19:10:19.789info
ESPHome API version: 1.15
dev:25042026-08-29 19:10:19.588info
ESPHome requesting API version
dev:25042026-08-29 19:10:19.307info
Konnected 65 is connecting: host 192.168.0.65:6053
dev:24952026-08-29 19:07:52.271info
Konnected 64 is online: ping response

nate · August 30, 2026, 9:36pm

@37kdeep thanks for the log details. This was helpful.

There was a bug in the Alarm Panel driver that was causing this. Fixed now in release 2026.8.1 which you can download/install from there or get from HPM.

After tracing this, I don’t think it was actually your device disconnecting, there was a bug that was causing the connection status to not track properly.

37kdeep · August 31, 2026, 12:48am

Awesome that you found it. I will install the new driver and get back to you. Thank you very much!

37kdeep · August 31, 2026, 7:30am

Here is the Hubitat log for the last 6-8 hours after I updated to release 2026.8.1

37kdeep · September 1, 2026, 12:00am

So I turned on logging for both boards for a short period of time. Is all of this normal?

dev:25042026-08-31 19:59:18.179

debug

ESPHome scheduling healthCheck in 37s

dev:25042026-08-31 19:59:18.176

debug

ESPHome send msg type #8 with [:]

dev:24952026-08-31 19:59:03.301

debug

ESPHome scheduling healthCheck in 54s

dev:24952026-08-31 19:59:03.299

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:246422.984375, hasState:true]

dev:24952026-08-31 19:59:02.581

debug

ESPHome scheduling healthCheck in 48s

dev:24952026-08-31 19:59:02.579

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]

dev:24952026-08-31 19:59:02.552

debug

ESPHome scheduling healthCheck in 38s

dev:24952026-08-31 19:59:02.550

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]

dev:25042026-08-31 19:58:43.802

debug

ESPHome scheduling healthCheck in 40s

dev:25042026-08-31 19:58:43.800

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-71, hasState:true]

dev:25042026-08-31 19:58:43.768

debug

ESPHome scheduling healthCheck in 42s

dev:25042026-08-31 19:58:43.766

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:58, hasState:true]

dev:25042026-08-31 19:58:42.903

debug

ESPHome scheduling healthCheck in 49s

dev:25042026-08-31 19:58:42.866

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:215943.546875, hasState:true]

dev:24952026-08-31 19:58:37.158

debug

ESPHome scheduling healthCheck in 35s

dev:24952026-08-31 19:58:37.156

debug

ESPHome send msg type #8 with [:]

dev:25042026-08-31 19:58:18.105

debug

ESPHome scheduling healthCheck in 44s

dev:25042026-08-31 19:58:18.076

debug

ESPHome send msg type #8 with [:]

dev:24952026-08-31 19:58:03.352

debug

ESPHome scheduling healthCheck in 43s

dev:24952026-08-31 19:58:03.350

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:246362.984375, hasState:true]

dev:24952026-08-31 19:58:02.627

debug

ESPHome scheduling healthCheck in 45s

dev:24952026-08-31 19:58:02.625

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]

dev:24952026-08-31 19:58:02.602

debug

ESPHome scheduling healthCheck in 36s

dev:24952026-08-31 19:58:02.600

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]

dev:25042026-08-31 19:57:43.690

debug

ESPHome scheduling healthCheck in 37s

dev:25042026-08-31 19:57:43.688

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-71, hasState:true]

dev:25042026-08-31 19:57:43.670

debug

ESPHome scheduling healthCheck in 52s

dev:25042026-08-31 19:57:43.668

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:58, hasState:true]

dev:25042026-08-31 19:57:42.769

debug

ESPHome scheduling healthCheck in 35s

dev:25042026-08-31 19:57:42.767

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:215883.546875, hasState:true]

dev:24952026-08-31 19:57:37.059

debug

ESPHome scheduling healthCheck in 46s

dev:24952026-08-31 19:57:37.057

debug

ESPHome send msg type #8 with [:]

dev:25042026-08-31 19:57:17.975

debug

ESPHome scheduling healthCheck in 59s

dev:25042026-08-31 19:57:17.973

debug

ESPHome send msg type #8 with [:]

dev:25042026-08-31 19:57:05.794

debug

ESPHome scheduling healthCheck in 56s

dev:25042026-08-31 19:57:05.786

debug

ESPHome received: [type:state, platform:binary, isDigital:false, key:2131827574, state:false, hasState:true]

dev:25042026-08-31 19:57:03.994

debug

ESPHome scheduling healthCheck in 48s

dev:25042026-08-31 19:57:03.984

debug

ESPHome received: [type:state, platform:binary, isDigital:false, key:2131827574, state:true, hasState:true]

dev:24952026-08-31 19:57:03.384

debug

ESPHome scheduling healthCheck in 53s

dev:24952026-08-31 19:57:03.382

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:246302.984375, hasState:true]

dev:24952026-08-31 19:57:02.667

debug

ESPHome scheduling healthCheck in 33s

dev:24952026-08-31 19:57:02.665

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]

dev:24952026-08-31 19:57:02.635

debug

ESPHome scheduling healthCheck in 53s

dev:24952026-08-31 19:57:02.633

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]

dev:25042026-08-31 19:56:43.715

debug

ESPHome scheduling healthCheck in 47s

dev:25042026-08-31 19:56:43.713

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-71, hasState:true]

dev:25042026-08-31 19:56:43.690

debug

ESPHome scheduling healthCheck in 43s

dev:25042026-08-31 19:56:43.688

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:58, hasState:true]

dev:25042026-08-31 19:56:42.789

debug

ESPHome scheduling healthCheck in 44s

dev:25042026-08-31 19:56:42.787

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:215823.546875, hasState:true]

dev:24952026-08-31 19:56:36.929

debug

ESPHome scheduling healthCheck in 54s

dev:24952026-08-31 19:56:36.927

debug

ESPHome send msg type #8 with [:]

dev:25042026-08-31 19:56:17.809

debug

ESPHome scheduling healthCheck in 49s

dev:25042026-08-31 19:56:17.807

debug

ESPHome send msg type #8 with [:]

dev:24952026-08-31 19:56:03.370

debug

ESPHome scheduling healthCheck in 55s

dev:24952026-08-31 19:56:03.368

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:246242.984375, hasState:true]

dev:24952026-08-31 19:56:02.649

debug

ESPHome scheduling healthCheck in 33s

dev:24952026-08-31 19:56:02.647

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-60, hasState:true]

dev:24952026-08-31 19:56:02.620

debug

ESPHome scheduling healthCheck in 40s

dev:24952026-08-31 19:56:02.618

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:80, hasState:true]

dev:25042026-08-31 19:55:43.733

debug

ESPHome scheduling healthCheck in 39s

dev:25042026-08-31 19:55:43.729

debug

ESPHome received: [type:state, platform:sensor, key:2654868797, state:-71, hasState:true]

dev:25042026-08-31 19:55:43.679

debug

ESPHome scheduling healthCheck in 56s

dev:25042026-08-31 19:55:43.677

debug

ESPHome received: [type:state, platform:sensor, key:513204495, state:58, hasState:true]

dev:25042026-08-31 19:55:42.778

debug

ESPHome scheduling healthCheck in 57s

dev:25042026-08-31 19:55:42.776

debug

ESPHome received: [type:state, platform:sensor, key:1324261225, state:215763.546875, hasState:true]

dev:24952026-08-31 19:55:36.775

debug

ESPHome scheduling healthCheck in 31s

dev:24952026-08-31 19:55:36.772

debug

ESPHome send msg type #8 with [:]

Topic		Replies	Views
Alarm Panel Pro frequent reboot Konnected Alarm Panels esphome , firmware-updates , alarm-panel-pro	4	89	December 12, 2025
Struggling to Upgrade to ESPHome with Hubitat Konnected Alarm Panels esphome , firmware-updates	10	317	October 17, 2025
Hubitat - Disconnect/Connect Konnected Garage Door Opener	6	71	December 12, 2025
ESPHome firmware for Hubitat Hubitat esphome , firmware-updates , alarm-panel-pro	54	1422	February 3, 2025
ESP Home Adoption Failure ESPHome esphome , alarm-panel-pro , dashboards	20	1128	June 22, 2024

Flood of ESPHome ping logs in Hubitat

Related topics