So this problem will hopefully be resolved when an update of max2play will be launched.
For the time being I will stay with DHCP activated: the IP address seems to be ‚fixed‘ even after a reboot / restart.
You may get into problems as soon as you disable DHCP… it is quite confusing anyway…
I have just put a brand new class 10 SD card into the Raspberry with the most recent version of the max2play image.
For now it runs fine after having carried out all updates and configurations.
The red LED on the Raspberry is always lit, the green LED is flashing shortly from time to time (approx. 6 times in a minute).
The CPU load is 0.14 at this moment, the SD card usage is 15 % (16 GB size), CPU temp. will not exceed 50 deg. (playing for 1/2 hr. from boot).
I will check this from time to time, and I will keep you updated!
I have added the above mentioned text to the /etc/dhcpcd.conf file, but it still does not work properly.
The ‚fixed‘ IP address as set in the file and in the LAN configuration of max2play changes after a while into another address, and all services are stopped.
So I cannot get access to the ’system‘ after that, and I have to disconnect the power supply (which I hate to do because of the risk of a corrupted SD card)…
This happens all the time, so for now I will leave the DHCP service active. I cannot use a fixed IP address, strange behaviour…
I hope that someone can resolve this issue..
For the rest max2play works great on my Squeezebox devices with the Logitech Media Server and Spotty (for Spotify).
This reply was modified 7 years, 1 month ago by tomsat50.
This reply was modified 7 years, 1 month ago by tomsat50.