Ben Jones

I think I have a hardware problem. Rebooting the device is no longer solving the problem and it is flicking over to read-only straight away.

New module received and system back up and running. Will close this for now as it seems like it was a h/w fault.

It has happened again only a few days after installing the new CM3 module.. [amplipi-read-only-#2.csv](https://github.com/micro-nova/AmpliPi/files/9414875/amplipi-read-only-.2.csv) Do these logs show any indication of what is going wrong?

Have rebooted and everything is back to normal...for now!

It is identical - I reloaded a config backup from before and have been running that since installing the new module.

I am still seeing my radio station streams locking up after a few days. I am also seeing these `alsa audio output error: cannot open ALSA device ""ch0""` errors in...

I have just updated my automation flows (in NodeRED) to automatically stop/start streams on-demand. So if there are no zones using a particular source/stream it will automatically `stop` that stream....

Would be nice to have a "zone centric" view - i.e. you select a zone and then pick an input to play on that zone. This seems more intuitive to...

FYI - this just happened again, for the first time in about 6 months. SSH and web UI unresponsive and my log monitoring system has reported the file system has...

Interesting observation, the REST API is still responding, but only to GET requests. I have tried POST to `api/reboot` and `api/announce` and they both return 500.