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 ;)