05-13-2020, 05:07 PM
@mancio61
Not enough technical details given to nail down two of these issues.
You said:
1.
When first booted with no connection to Ethernet but with a WiFi adapter, moOde comes up in AP mode with the AP SSID "moode". Are you saying you couldn't find this AP? Some USB-WiFi adapters don't support the AP host mode. What is the make/model of yours? The make/model (and associated driver) can also have an effect on the WiFi client mode. This may also be an issue with the WiFi access point on your router.
and later
This just reinforces my sense that your WiFi adapter and/or its driver is a problem.
2.
Well, yes it does, if you are querying from a host/OS/app which supports the .local pseudodomain (you can look up mDNS to find out more about this alternative method of resolving a hostname into an IP address). What were you using to use "the moode.local" way? And didn't using just "moode" work to resolve the IP address? If not, there may be an issue with your regular DNS.
3.
Ah, now this one's interesting. I don't use Tidal much any more but last time I checked it was working in the UPnP renderer of three different moOde players with my Tidal account credentials entered into UPnP config. Now it's not, including on the player with the latest version of upmpdcli (1.4.9) installed. This will take some detective work.
Regards,
Kent
Not enough technical details given to nail down two of these issues.
You said:
1.
Quote:My first tentative was to access through wifi (I have a USB dongle for it), but no success at all.
When first booted with no connection to Ethernet but with a WiFi adapter, moOde comes up in AP mode with the AP SSID "moode". Are you saying you couldn't find this AP? Some USB-WiFi adapters don't support the AP host mode. What is the make/model of yours? The make/model (and associated driver) can also have an effect on the WiFi client mode. This may also be an issue with the WiFi access point on your router.
and later
Quote:Wi-Fi access: no way to work. Sometimes it connects, sometimes no (and I try very closed to the router...)
This just reinforces my sense that your WiFi adapter and/or its driver is a problem.
2.
Quote:btw, the moode.local way didn't work, so I had to scan my LAN to find the IP address used by the Raspy...
Well, yes it does, if you are querying from a host/OS/app which supports the .local pseudodomain (you can look up mDNS to find out more about this alternative method of resolving a hostname into an IP address). What were you using to use "the moode.local" way? And didn't using just "moode" work to resolve the IP address? If not, there may be an issue with your regular DNS.
3.
Quote:The whole messages says : "MPD Error ; Failed to decode http://myip:49149/tidal/track?version=1&trackId_34454466; CURL failed; Empty reply from the server "
Ah, now this one's interesting. I don't use Tidal much any more but last time I checked it was working in the UPnP renderer of three different moOde players with my Tidal account credentials entered into UPnP config. Now it's not, including on the player with the latest version of upmpdcli (1.4.9) installed. This will take some detective work.
Regards,
Kent
