Can't speak for Mac Terminal since I have no Apple computers at hand, but maybe we can get through this.
I assume you are trying to "ssh" into your MoOde Player. Let's say its hostname is "moode" and that name can be resolved by your DNS service (otherwise you can use the host's IP address).
You are trying to login to the MoOde Player as user '"pi" so unless this is your username on your local host, have explicitly to tell ssh you want to connect as user "pi". Either
Code:
$ ssh pi@moode
Code:
$ ssh -l pi moode
Code:
pi@moode's password:If you forget and try to "ssh" with your own username, you can get the "Permission denied" message. For example, if my username is "bletch" on the host I'm "ssh"ing from:
Code:
$ ssh moode
bletch@moode's password:
Code:
Permission denied, please try again.
bletch@moode's password:Is this what you are seeing?
Regards,
Kent
Sorry, I forgot to address the first error message you mentioned. This occurs when you try to "ssh" to a new host, e.g., one not known to the system on which you invoked "ssh". You should have been asked if you wanted to add this host. Answer "yes" and drive on.
Google is your friend. Lot's of material is available on line about ssh.
Regards,
Kent
Hi Kent,
thanks for the help.
Yes it behave like you said. I don't know wich username and password to use, I've read root / moode in several thread but sadly:
... found by accident in a lost page that pi / raspberry worked... are they hidden infos not to let butcher as me to get in ? 😉
Now I have to wander the Net to find how to get to that file and edit it...
Thanks!
thanks for the help.
Yes it behave like you said. I don't know wich username and password to use, I've read root / moode in several thread but sadly:
Code:
$ ssh [email]root@moode.local[/email]
Warning: Permanently added the ECDSA host key for IP address '192.168.34.4' to the list of known hosts.
[email]root@moode.local[/email]'s password:
Permission denied, please try again.... found by accident in a lost page that pi / raspberry worked... are they hidden infos not to let butcher as me to get in ? 😉
Now I have to wander the Net to find how to get to that file and edit it...
Thanks!
I can understand your frustration dealing with this Moode Audio Player thread and its ever growing number of messages. Information which was relevant when a message was posted tends to go stale and it's difficult to know at any given point in time if it is still valid.
The default username/password changed at the same time that Tim rebased his work on MoodeOS1.0. Since the new username (pi) and password (raspberry) are stated at the beginning of the Setup Guide (See Note 3) for the release we are discussing, I can't agree that this information is hidden.
In any case, you're past this now. If navigating to and editing the file /etc/network/interfaces sounds challenging, then perhaps you should just wait a little bit for Tim to post his next technical release (see message #2816]). Knowing his track record, I expect it to arrive soon.
Regards,
Kent
Hi Kent,
I was kidding and no offense, I know that this is tons of work and am very grateful for all help =) It's just a hobby afterall 😉
Thank you guys!
Matthieu
I was kidding and no offense, I know that this is tons of work and am very grateful for all help =) It's just a hobby afterall 😉
BTW, the setup guide I've used is in the MoodeAudio website and does not feature these infos http://moodeaudio.org/docs/readme.txtStina Nordenstam said:
Thank you guys!
Matthieu
Tim, i meant that clicking wouldn't ignore the limit, but just set the volume to that limit without displaying the pop up message.
For example:
Limit is set to 40
I'm clicking the dial at the right side
Moode is turning the volume up to 40, but without the warning message.
I'd like that message to be optional (switchable in the config)
Currently it stays at previous volume and displays the message and i need to precisely turn volume up in steps.
Once you've logged in as the pi user,
sudo nano /etc/network/interfaces
Save the changes and reboot.
Hi Phil,
sadly I get what Tim said in #2814, nothing to change.
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
wireless-power off
wireless-essid "WiHiFi"
wireless-key "therightpassword"
I'm being less confident it can work now :'(
sadly I get what Tim said in #2814, nothing to change.
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
wireless-power off
wireless-essid "WiHiFi"
wireless-key "therightpassword"
I'm being less confident it can work now :'(
Just done that Phil, instead of blinking once the dongle blinks 10 times and then off. And no connection.
May I try another supply?
May I try another supply?
Last edited:
Hi,
The problem with this is that typically the limit is set high for example 85. I can't support software automatically setting volume to 85 because of a mistaken mouse click or touch. User can disable warning limit but then must accept that a errant touch on a smartphone might cause full volume.
The usage scenario u are describing sounds more like what I would call "preset volume levels" for example low=10, medium=25, high=40. Something like that. I always end up setting volume to just a few specific settings on my audio systems and only adjust if a particular track or album was recorded at really high or low levels.
Regards,
Tim
Tim,
Yes, you're right here that it might be accidental, but user should be aware of that.
Also, the presets you mention would work, as indeed, in most cases that's what happens: using 1-2 predefined volume levels.
P.s. I'm musician and I'm used to the fact, that hard and software does exactly what i tell it to do, even if is erroneous 🙂 I just tend to switch off the safety locks and just be aware of what I'm doing and what can happen 🙂
Last edited:
Hi,
In /etc/network/interfaces remove the double quotes from the hex WEP key, save the file then reboot.
wireless-key "therightpassword"
if that doesn't work then WEP is probably broken in Linux kernel or in Moode code.
-Tim
@Tim,
I have ditched both RuneAudio and Volumio after stumbling upon Moode. (Currently running the latest 2.6 TR2)
I don't know if this has been requested at some point, but the library tab would be substantially more useful if the following are implemented:
- Search function would look up the entered string in artist and track name as well as album name (as opposed to only album name so far)
- Search would be performed after the user presses the arrow (like in the browse tab)
- Add the possibility to use a wildcard in the search string
- Make the search function insensitive to character variations i.e. when searching for a something including the letter "e", variations including "é" and "ê" would also be found.
The search function as it is right now is so sensitive to tiny differences that it renders it so impractical at to be nearly useless
Another nice to have option is when listening to a track to be able to look up to all the tracks of the album it is from.
Thanks
Nick
I have ditched both RuneAudio and Volumio after stumbling upon Moode. (Currently running the latest 2.6 TR2)
I don't know if this has been requested at some point, but the library tab would be substantially more useful if the following are implemented:
- Search function would look up the entered string in artist and track name as well as album name (as opposed to only album name so far)
- Search would be performed after the user presses the arrow (like in the browse tab)
- Add the possibility to use a wildcard in the search string
- Make the search function insensitive to character variations i.e. when searching for a something including the letter "e", variations including "é" and "ê" would also be found.
The search function as it is right now is so sensitive to tiny differences that it renders it so impractical at to be nearly useless
Another nice to have option is when listening to a track to be able to look up to all the tracks of the album it is from.
Thanks
Nick
I think the quote-marks are a red herring [1]. Isn't the operative issue that the "TheRightPassword" is not a hex key but just a string passphrase? I admit to being rusty on this stuff since most modern WPA2-enabled systems "just work" but I seem to recall there's a syntax for using string passphrases something like
Code:
wireless-key s:TheRightPasswordOtherwise, there are hex-key generator programs available online.
Sorry, but I don't have a spare access point here to set up in WEP mode to experiment with.
Regards,
Kent
[1] for grins, I hand-edited my interfaces file to remove the double-quotes your code places around the wpa-ssid and wpa-psk values and rebooted. Moode Player came up fine in WiFi mode. I'm not advocating not using them, just suggesting something else is going on.
It's great to have more stations, and I'm using the radio more than ever, but the list is getting very long.
Would it be possible to let the user favorite specific stations, and then sort or select only those? I know you can search, but favoriting would be much easier.
Also, a way of showing/selecting the quality or bit-rate of a station would be good as some of the lower bit-rate stations can sound a little rough!
Last edited:
Hi Nick,
Great suggestions and many already on my TODO list. Hopefully in Moode 2.7/2.8 timeframe I'll be able to focus on "collection management" and UI instead of system and OS stuff.
-Tim
Hi Kent,
Based on prior bug reports, dbl quotes seem to be needed around SSID and PSK in case there are spaces or certain other chars.
As far as WEP goes Moode 2.6 code accepts the password as-is and I think it can be either plaintext or hex within specific length ranges. I'm not really sure because I've never used WEP and don't know of any other Moode users that need WEP. I'd have to look back in the Moode 2.5 codebase but I recall it did a bin2hex() conversion of the password for WEP.
I had planned to remove WEP altogether from network config since its essentially equivalent to "no security".
Regards,
Tim
Sorry guys this is not the password wich is hex, that was an example in case my neighbout wanted to use my access 😉
BTW,
removed the quotes, no wifi :'(
So I'll redo it, even re-download Moode and start from scratch; but this time I put my router in: WPA, the last of the list chosen.
Wifi options on the router said: