Please use template to report bugs and problems. Post here your questions when not sure where else to post Only for bugs in the Domoticz application! other problems go in different subforums!
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Perhaps run Domoticz in a docker container. x86_64 is built on an Ubuntu environment ubuntu-latest (currently ubuntu-24.04) so there could be some mismatch with Fedora
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
At this moment I suspecting the rtl_433 receivers, I have two of those one for 433 MHz and one for 868 MHz, especially the 868 gives time outs, changing the receivers does also change these time outs... (so not hardware related)... no clue..
Another step, it seems to occur after Domoticz get's (for some reason) no information from rtl_433, resets the device and than 5 minutes later the watchdog is triggered:
2024-10-14 03:45:04.578 Error: Rx433MHz hardware (28) nothing received for more than 1 Hour!....
2024-10-14 03:45:05.578 Error: Restarting: Rx433MHz
2024-10-14 03:50:05.218 Error: mainworker seems to have ended or hung unexpectedly (last update 301.000000 seconds ago)
2024-10-14 03:50:05.223 Error: Domoticz(1491206) is exiting due to watchdog triggered...
2024-10-14 03:50:05.246 Error: Failed to start gdb, will use backtrace() for printing stack frame
2024-10-14 10:15:10.802 Error: Rx433MHz hardware (28) nothing received for more than 1 Hour!....
2024-10-14 10:15:11.802 Error: Restarting: Rx433MHz
2024-10-14 10:20:11.519 Error: mainworker seems to have ended or hung unexpectedly (last update 301.000000 seconds ago)
2024-10-14 10:20:11.526 Error: Failed to start gdb, will use backtrace() for printing stack frame
(Note: I have a script running that detect that Domoticz has crashed and restarts Domoticz automatically).