janui wrote:Hi jlynton,It is possible that 'lease time' on your router is set to a relatively long time. This could cause it to remember the link between the IP address of your v0.4b Rune and 'runeaudio.local' for longer than you would expect. 'runeaudio.local' could therefore point to the wrong IP address.jlynton wrote:try: http://runeaudio.local or http://runeaudio. or http://runeaudio
Thanks again Janui, but none of those work.
The easiest way to test this is to start v0.5b, access it via it's IP address and change its hostname in the Settings UI. Then try to access it via 'http://your-new-name.local'.
This problem is really puzzling us, hope this helps.
janui
Sorry, been out of town for a bit.
Thanks, I have tried your suggestions, Janui, but still no luck, puzzling, but as I can reach it via the IP address, I am not terribly worried about this.
A new problem has come up though. I am using a Pi 3B with a JustBoom AMP Hat running 0.5beta with gitpull done this morning. At first it appeared to work fine, but suddenly it stopped responding to the volume control and will only play at maximum volume. It is set to Volume Control 'enabled-hardware' and volume knob, 'realtime' (have tried 'on release' as well, same result). If I set it to Volume Control 'enabled-software' the volume control works correctly.
I have tried the same hardware with 'Volumio', and with 'enabled-hardware' the volume control works correctly.