First night with Astroberry on a Raspberry Pi 4b. Everything up and running, guiding solving session etc. After an hour all of a sudden I noticed guiding failed (100% clear sky and no dew). On a closer look, the mount was moving away from the target. I was using phd2 guiding at the time. Stopped, disconnected, reconnected switching to internal guiding, running again and everything working. Another hour and the same thing happened again. Did a simple stop session, plate solve slew to target again and restarted session. Another hour and ran away again.

Any ideas at all on this one? I can't find any obvious settings that might be the cause. It's almost like tracking is just stopping and it's the normal earth rotation moving the target away. It's not doing it at slew speed bit you can see the stars move on the Guide Scope view in guiding if I loop it.

It happened to me recently, but didn't have time for debugging. Does it apply to PHD2 only?

Do you use subframes? I did see similar behavior when using PHD2 and subframe readout on my 290MMmini. Every now and then it would get a blank frame and then start searching the star, driving the pointing away from the target.
Wild guess, I know. Might also have been related to USB connection issues. In the meantime the guide cam has a separate cable to the control computer (before it was through the hub of the ASI1600), and I never had problems again...

Unfortunately it happened with both internal and external guiding.

I did have it on subframe. Ok that's something to try at least. Guide came is the Asi120mm-s Usb3 and is connected directly to the Pi no hub etc.

same! had to switch it off