Disclaimer
Application version
0.5.8
System version
0.2.8
Device model
JetKVM
Extension model
ATX Power Control
Remote device Hardware
Generic PC
Remote device OS
Proxmox
Bug description
I'm running into an issue where my JetKVM becomes unreachable on the network after roughly 1-2 weeks of uptime. A power cycle (unplug/replug) resolves it every time, but obviously that's not a real fix.
When it started:
This began after I configured MQTT and Home Assistant discovery. Before that, I hadn't noticed this issue, though I can't rule out that it was already present and just went unnoticed.
Details:
Firmware: App 0.5.8 | Sys 0.2.8
I don't know whether the device is still otherwise functioning normally (e.g. still serving KVM video/input locally) when it drops off the network, since I can only access it remotely — I only know it's unreachable over the network at that point. However on an ethernet link level is does still seem to be connected according to my network switch.
Questions:
Could this be related to the MQTT/HA discovery feature specifically (e.g. a memory leak, thread hang, or reconnect loop over time)?
Alternatively, could this be temperature related? If so, what are the acceptable temperature thresholds for the device, and is there a way to check historical temperature via MQTT or logs after the fact (since I can't view the display in person)?
Any recommended way to get logs or diagnostics after a hang like this?
Happy to enable Developer Mode / dig into the shell if that helps troubleshoot, just let me know what to run next time it happens.
Also, I enabled the memory sensor (which is disabled by default) and started monitoring it through home assistant. I rebooted the JetKVM at 03:00 last night and I can confirm a slight increase in memory usage over time as can be seen in this graph. I'll continue to monitor if this trend continues even further.
Disclaimer
Application version
0.5.8
System version
0.2.8
Device model
JetKVM
Extension model
ATX Power Control
Remote device Hardware
Generic PC
Remote device OS
Proxmox
Bug description
I'm running into an issue where my JetKVM becomes unreachable on the network after roughly 1-2 weeks of uptime. A power cycle (unplug/replug) resolves it every time, but obviously that's not a real fix.
When it started:
This began after I configured MQTT and Home Assistant discovery. Before that, I hadn't noticed this issue, though I can't rule out that it was already present and just went unnoticed.
Details:
Firmware: App 0.5.8 | Sys 0.2.8
I don't know whether the device is still otherwise functioning normally (e.g. still serving KVM video/input locally) when it drops off the network, since I can only access it remotely — I only know it's unreachable over the network at that point. However on an ethernet link level is does still seem to be connected according to my network switch.
Questions:
Could this be related to the MQTT/HA discovery feature specifically (e.g. a memory leak, thread hang, or reconnect loop over time)?
Alternatively, could this be temperature related? If so, what are the acceptable temperature thresholds for the device, and is there a way to check historical temperature via MQTT or logs after the fact (since I can't view the display in person)?
Any recommended way to get logs or diagnostics after a hang like this?
Happy to enable Developer Mode / dig into the shell if that helps troubleshoot, just let me know what to run next time it happens.
Also, I enabled the memory sensor (which is disabled by default) and started monitoring it through home assistant. I rebooted the JetKVM at 03:00 last night and I can confirm a slight increase in memory usage over time as can be seen in this graph. I'll continue to monitor if this trend continues even further.