Ropieee does not recognise roon core until reboot

Audio Gear Talk RoPieee
1

I use Ropieee on 2 devices – one in a Holo Red as an audio renderer connected to a dac, and the second in a raspberry pi 3b with a display and a flirc as a display and control for the Red. My usual practice is to switch everything off at night and everything gets switched on in the morning, i.e. the roon core, the dac, amp and the display Ropieee. Recently the display Ropieee doesn’t recognise the roon core unless I reboot the display Ropieee – then no problems and all is fine. It used to work fine, but recently it wont recognise anything until I reboot the display Ropieee.

It might be to do with timing, i.e. I switch the roon core and Ropieee display devices on at the same time, so is there any way of delaying the startup of the Ropieee display? I also tried telling the display ropieee to reboot at a specific time of day but it doesn’t do it. Any ideas? Here is some feedback before the reboot of the display Ropieee: 13304cd9df26b61b

Thanks in advance – all the effort in developing Ropeee is much appreciated – I have tried other things but none are as good as Ropieee.

2

Hi Steve,

There is no dependancy in startup order: your RoPieee unit(s) should be able act on the events that take place (roon server comes available etc.), so that’s not the issue.

I do see in your logs however, an issue with time synchronization. That is potentially an issue: so have you changed something in your firewall or router?

3

Thanks very much - I looked at the router and I dont think NTP was working properly (the date in the system log was 5 May and it is 3 May today) so I set a new NTP server. The router now looks like it has the right time. No change on the display Ropieee until I rebooted and then it worked fine - here is some feedback after the reboot 4e8783e81a00dd09 - hopefully there are no time sync errors now. Thanks again for the help.