Max2Play Home › Forums › Max2Play Add-ons › trying to get wifi going, keep getting errors › Reply To: trying to get wifi going, keep getting errors
That was just about eternally frustrating. I followed your instructions this morning and got connected. the one thing I did differently this time is I left the ethernet plugged in until after I was disconnected from power. I left it connected today and monitored it remotely. It appeared to stay connected.
When I got home and started working on it about two hours ago I was trying to use the Spotty app to play via Spotify Connect to the max2play device. No sound. I had power lights, and the optical light was lit, but no sound. Max2play appeared in the LMS web UI. So I swapped out the optical cable and some sound started coming through intermittently. That seemed really odd to me. I was switching the cable back, and the power came disconnected. That set me off on two hours of fiddling around. Something timed out at some point and I had to start over with a new image. Not a big deal, right, probably worthwhile. So I start from scratch, get it all set up. Get through it all and I CANNOT get the wifi to connect. Again, I am walking back and forth trying to get this going. Every time I am on ethernet I can hit http://max2play/ immediately. As soon as I shut down and power up I can not connect to wifi. I double and triple check the wifi settings. Nothing.
I do not want to be without music, so I pull the old squeezebox duet from the drawer and I have that connected and playing within 20 minutes. On that note – I should say that I also have a SB Touch on this network and it works flawlessly.
As a last ditch effort I try WPS with the max2play (which was not working yesterday) and it connected. This makes no sense to me.
I am not smart enough to put some sort of monitoring on the digi+ to try to figure out why it is not working. I mean, just when I decide the wifi on the rpi3 must be broken, I get connected. Like I am right now. That reminds me – you know what is the WORST? At one point after I was ready to shutdown from the ethernet, I decided I did not want to unplug from power and walk over to my desk and plug into that power for the switch to wifi… so I left it on the power by the router… And I connected to wifi. Awesome… unplug, walk over to the computer, hook to power… nothing. But that power supply is the one that it is connected to right now, working. So it is not the power supply.
My last recent post was on Feb 24. It ran flawlessly until yesterday. Basically three months. And then flawlessly ceases to exist.
If you have any pointers or diagnostics I can run, I am open to ideas.
I coped this at one point, when I was connected to ethernet:
#### FILESYSTEM ####
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 29441240 1734508 26486584 7% /
devtmpfs 435668 0 435668 0% /dev
tmpfs 440276 0 440276 0% /dev/shm
tmpfs 440276 6176 434100 2% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 440276 0 440276 0% /sys/fs/cgroup
/dev/mmcblk0p1 61384 22808 38576 38% /boot
tmpfs 88056 4 88052 1% /run/user/1000
#### LOAD AVERAGE ####
0.27 0.14 0.05 1/200 2525
#### KERNEL ####
Linux max2play 4.9.39-v7+ #1020 SMP Sat Jul 22 14:21:01 BST 2017 armv7l GNU/Linux
#### LINUX-VERSION ####
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
And then this just now that it is on wifi:
#### FILESYSTEM ####
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 29441240 1732732 26488360 7% /
devtmpfs 435668 0 435668 0% /dev
tmpfs 440276 0 440276 0% /dev/shm
tmpfs 440276 6164 434112 2% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 440276 0 440276 0% /sys/fs/cgroup
/dev/mmcblk0p1 61384 22808 38576 38% /boot
tmpfs 88056 4 88052 1% /run/user/1000
#### LOAD AVERAGE ####
0.13 0.04 0.01 1/193 4286
#### KERNEL ####
Linux max2play 4.9.39-v7+ #1020 SMP Sat Jul 22 14:21:01 BST 2017 armv7l GNU/Linux
#### LINUX-VERSION ####
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie