@Desaydrone The error message suggest the plugin is not able to find a Sonos device on the network. Although, it automatically retries until it finds one.

Is there any other messages like this on the logs? Are you sure your speakers are on the same LAN?

@PH1TCH I don’t want to have to support something that I don’t use so I’m afraid I’m going to decline.

However, seems you are lucky as someone created a fork that includes the album cover: https://github.com/armybean/MMM-Sonos

@Mahieedaboss not sure what you mean by more slides?

@PaulB I use the antenna that came with the USB dongle. Works like a charm

Thanks @seramik, @Fozi. I already planned to have a white cable, it just hasn’t arrived yet so I used a black one as a temporary measure.

I’ll consider upgrade to glass but later, once I get bored of the current version.

@bhepler Thanks! The slots fo the mirror give a neat finish but I’m sure there are easier technics to achieve this effect without the hassle (it wasn’t the easiest job to do the frame assembly)

That being said, it was good woodworking practice :)

I always wanted to try building a magic mirror for myself, but I really started the journey about 6 months ago. The goal for this build was to have something simple and minimalist.

My first step was to sort out the software part (easier for me as I am a software engineer during daylight) then move on to the hardware.

Software

I have a couple of raspberry pis lying around at home. I took one and installed MagicMirror on it without any troubles. I also started to look at modules that were available: weather, calendar and clock were of course in the final bracket. But I wanted something beyond that.

I’m living in Edinburgh and commuting by bus, so a module to display the live time data from the bus stops around the house was a must-have. It didn’t exist so I created MMM-LothianBuses.
I can see planes from the kitchen windows. As my wife is really curious, she always wants to know what planes they are so I built MMM-FlighTracker module which does exactly that.
A late addition to the the curated list of modules I’m running was to know what current song is playing on my Sonos network. In the spirit of having a minimalist setup I also created another MMM-Sonos module as the other one didn’t suit my needs.

Hardware

With the software out of the way, I started to build the frame for my mirror. I bought an old 21’’ monitor from which I took all my measurements. The plan was to enclose this screen into a wooden frame, sandwiched between the mirror and angle brackets to secure it in place. I have a wood recycling center close-by home, went there and bought a 1.8cm plywood sheet from which I cut strips to do the frame. I used dove-tail joints to provide enough mechanical strength to support the weight of the final product.

Initially, I wanted to keep the frame bare with a light stain, as the plywood layers give a nice feature. But I did sort of a mess when I cut the strips, and the plywood shipped quite a bit. At the end, I had to use some filler + paint to have an nice finish. Next, I made a channel with my router on each strip to slide the mirror in. This provides a nice look but it also means that once glued, the mirror cannot be extracted or changed without breaking the frame.

After the assembly of the frame + mirror, I did a couple of coats of filler, then paint. I pushed down the screen against the mirror and secured it with 3D printed angled brackets. I also soldered power leads to have a nice 3 pins IEC connector at the bottom of the screen. That way, I have a nice single unit that I can plug anywhere (bonus point of my screen is that the 2 USB ports are always delivering 5V even though the screen is “off”, so the raspberry pi can be plugged there directly rather then needed an external power source)

To hanged the mirror, I used a very simple french cleat within the frame which makes the mirror completely flushed with the wall. Here is the result!

After thoughts

I’m super happy with the way it turned out, and it gave me so much satisfaction when I finished the project. However there a couple of things that I might do differently if I had to do it again:

• not using the channel to slide the mirror in, for reasons explained above. I would rather do a simpler design for the frame.
• use a glass mirror. I have a pretty decent acrylic mirror. It looks good but unfortunately, it:
  • wrapped a bit.
  • reduces the brightness of the text quite a lot.
  • reduces the viewing angles significantly.
• spend more time onto the smaller details like “externalised” the screen buttons (I have all the hardware but need to wire them up) + do a an integrated on/off and reset buttons for the raspberry pi. Although this can be added later on.

@AvatarED007 If there is no error at start up, that means the module is able to fetch the groups fine. But based on the latest logs you shared, it fails to fetch again the groups when the change, which would indicate that somehow the module (hence the mirror) loose the connection to the speakers later on. Maybe your mirror has a flaky connection?

Unfortunately, I cannot reproduce this so it’s going to be impossible to assist further :(

@AvatarED007 Hum, it doesn’t make any sense. The discover should retry even if there is an error, something is wrong here.

Can post the entire log file please? Also, are you sure all your sonos devices are up to date?

@AvatarED007 Do you have more logs after what you shared? Did the module managed to connect to at least one Sonos device?

FYI, error 503 and 405 suggest that the module is trying to discover a device on your network and get the groups, but fails at doing so. There are quite a lot possibilities why this can happen:

• Is your mirror on the same network as your Sonos devices?
• Are your Sonos devices on and connected?
• Are your Sonos devices up to date?

Alright, so I took a deeper look and it turns out that my code to display groups had a bug which made devices reappear even though they were part of a group. That should be fixed now with version 1.2.0.

I also added a new config flag to display the group’s full name, see README.md

Regarding your comment @eliah on group volume, I disagree. The volume displayed is the global volume of group, which is exactly what the sonos app displays. Displaying volume of all members wouldn’t make sense here as this module doesn’t control the speakers (again, the sonos app does exactly this, it displays the group volume, then display individual speaker volume when, and only when, you change the volume)
That’s why I’m going to skip your request. However if you strongly feel it should be there, the code is open source on GitHub so feel free to fork the repo and implement it :)

And finally, simply git fetch origin && git pull origin master within MMM-Sonos folder to update the module. Enjoy!

@hweigel Thanks, that’s very much appreciated!

The module specifies classes for each element, like this one for the track so you can customise the font size via your custom.css

@sonicgoose Yeah, I thought this would happen at some point. Need to think about how I can implement this.

Can I ask you a favour? Could you create issues on GitHub for the long list and the feature feature? Would be easier for me to track the different things. Thanks in advance :)

@sonicgoose said in MMM-FlightTracker - Real time plane tracker using ADS-B systems:

@tbouron said in MMM-FlightTracker - Real time plane tracker using ADS-B systems:

Hi @sonicgoose.

It’s already available since v1.1.0. Check out the “setup” section of the README.md, it explains how to set it up.

Wow. How did I miss that?! I’ve been following this module’s progress but clearly not close enough. Now I want to go home and try it! (Stupid work prevents me, though.) Thanks!

Ahah no problem. To be fair, I released this version only 7 days ago :)

Glad you get excited about it! Although, the module might not work as good as expected for you, given the volume of planes you track. You see, my module handles huge volume by… not handling it 😅 There is currently no limit in place in the number of planes returned by the socket or displayed on the mirror.

This is mainly due to my lack of good antenna (hence not a lot of planes to display) But I would be curious to hear how you think this should be done, especially how the filtering and ordering should be performed?

Let me know what you think @sonicgoose :)

Hi @sonicgoose.

It’s already available since v1.1.0. Check out the “setup” section of the README.md, it explains how to set it up.

Hi again.

I just release v1.2.0 of the module which adds support for the distance and heading` from your current coordinates to the planes displayed. See the README.md for the new configuration + how it looks like.

To update, simply do a git checkout master && git fetch origin && git pull origin master

@eliah I’ll see what I can do. But in the meantime, feel free to open issues and/or PRs on the GitHub repo for potential fixes

@eliah Awesome! Thanks for the feedback, I’ll cleanup and push the changes as soon as possible :)

Regarding the other issues:

Value for song length minutes has no leading zero, so when a song’s length is 2:04 it shows 2:4.

I already fixed that, it’s in a branch since Christmas but I was waiting for your feedback on the group scan issue to release it.

any of speakers are used directly by AirPlay, it shows (null) (null). Maybe it’s better to ignore AirPlay mode if no information is available for it?

I assume you are talking about the second line for artist and album right? I already have sort of partial fix for that (not displaying the album if null). I could do the same thing for the artist. When you are using airplay, is the first line displayed correctly? What does it say? I unfortunately cannot know if something comes through airplay or not, it’s all unified through the Sonos library.

Not sure if it is a bug of a module or Sonos library behind it, but for some reason the group names are sometimes become incorrect. For example, if I start a playlist on three speakers in the same group, first it shows something like “Kitchen+2” (and that’s correct), but after some time it becomes just “Kitchen” (same 3 speakers are playing).

That would be a bug in the underlying Sonos library. I just listening for events and display whatever comes from there.

And additionally, if more than one speaker is playing in the same group, each of them can have its own volume. In this case the single volume indicator that your module outputs to the screen becomes useless.

The Sonos library doesn’t give me this information unfortunately so that won’t be possible to do for now.

Hi there.

I just release v1.1.0 of the module. See the README.md for the new configuration + how it looks like.

To update, simply do a git checkout master && git fetch origin && git pull origin master && npm i

@Jas No problem. Feel free to add an issue on GitHub. If enough people really want it and +1 the issue, I’ll consider doing it ;)