The second log seems fine as well… I see that you have your DHCP lease time pretty short (12 hrs), but I also see that the renewing is working.
So this is difficult to debug. To make sure we get a proper log the following would help:
If the situation occurs again and the device is not available again, please connect a cable, go to the webpage and reboot the unit. As RoPieee runs entirely in RAM we need to make sure we get the log when the issue appears. So pulling the cable also wipes the log. Rebooting the unit from the webpage however stores the log.
Write down the time of the event, and send me feedback. I can then search inside the logs.
Oh. On a side-note: can I suggest you set the reboot time from ‘weekly’ to ‘daily’ on the wireless one?
The logs are combined, but the latest one is stored in RAM. So pulling the plug means loosing it.
Is there any chance you can attach a cable when it happens? Because if that’s case we can store the latest log for analysis.
I had this problem recently, with a HifiBerry Pi which had been running fine for some months. The only thing I changed was I upgraded to RopieeeXL.
I discovered my power supply wasn’t powerful enough - I thought my Pi had a 2 amp PSU but in reality it was only 1 amp. I hadn’t noticed with standard Ropieee, presumably because the power requirement is slightly lower.
It was doing the same as yours - working fine for a while, then just dropping off the network and dying. The only fix was to pull the plug and start again.