@requiemmg said in MMM-Spotify:

I understand that it is still not possible to display multiple accounts at the same time? (Family account, different devices; e.g. display “x is playing for user y on device z” or so?)

First time I am reading about this request :)
I am unsure how that could be solved - since UI is configured / optimized to display exactly one song. That would mean some massive design changes. In addition, it would need some looking into how to support querying multiple accounts at the same time / in different instances.
For me this is out of scope at the current point in time. You can, of course, create a new issue with an enhancement request and will see how things change in the future, or maybe somebody else wants to contribute code to that idea.

Another feature request: I’d like the module to be hidden when nothing is being played. I am just using this for status display, not for control of spotify. Possible to add in a coming version?

There already is a feature request open for that:
https://github.com/skuethe/MMM-Spotify/issues/176
However, I did not yet have time to work on it.

I really like this module, especially with touch screen usage.
The implementation is easy but still very powerful.

F.e. I added support for the following two modules:

• https://github.com/TeraTech/MMM-WiFiPassword
• https://github.com/skuethe/MMM-Spotify

In MMM-Spotify it is used to display account / device selection popups on screen. The available callback payload function makes this work in the first place, as we (of course) need to react on the made user selections :)

So again, great module, thanks!

Hi everybody. I am the new owner of this module (as of last year October). I haven’t monitored these forums / this post for problems so far. If you do have technical problems with this module please be so kind to directly open an issue in the git repo:

https://github.com/skuethe/MMM-Spotify/issues

It makes working on issues a lot easier. Thanks!

As to some of the open topics / questions here of the last weeks:

• @Abstr @razserv2010 I’ve recently re-worked the multi user authentication and fixed some problems with it:
  https://github.com/skuethe/MMM-Spotify/releases/tag/v2.0.1
• @crisvdn I am using it with MMM-Touch (which, of course, requires a touch screen) - it is a very powerful module
• @luizcarlosnery there is no direct option to do this. But you can definitely get something to work. There is a build-in config option to send custom notifications on suspend / resume:
  notificationsOnSuspend and notificationsOnResume - see README for more details
  You could, for example, use it in addition with MMM-pages which has some nice options to handle suspending / resuming special modules based on different pages

I hope that helps for now. I have some more fixes and improvements in the pipe that will be merged in the next comming weeks.

@requiemmg said in MMM-Spotify:

I understand that it is still not possible to display multiple accounts at the same time? (Family account, different devices; e.g. display “x is playing for user y on device z” or so?)

First time I am reading about this request :)
I am unsure how that could be solved - since UI is configured / optimized to display exactly one song. That would mean some massive design changes. In addition, it would need some looking into how to support querying multiple accounts at the same time / in different instances.
For me this is out of scope at the current point in time. You can, of course, create a new issue with an enhancement request and will see how things change in the future, or maybe somebody else wants to contribute code to that idea.

Another feature request: I’d like the module to be hidden when nothing is being played. I am just using this for status display, not for control of spotify. Possible to add in a coming version?

There already is a feature request open for that:
https://github.com/skuethe/MMM-Spotify/issues/176
However, I did not yet have time to work on it.

@hango said in MMM-Modal:

I make my modal:

this.sendNotification("OPEN_MODAL", {
	template: "templates/MyModal.njk",
	data: {
		title: "Test modal",
		message: "Test message"
	},
	options: {
		isDialog: true
	}
});

in console I get this:

nunjucks.min.js:4 GET http://localhost:8081/modules//modal/templates/modal.njk?s=1634300311396 404 (Not Found)

templates/MyModal.njk doesn’t really fit with the error message templates/modal.njk?! Sure you have specified the correct path?
Referencing it to within your module path works just fine: template: "templates/MyModal.njk",

If this is possible…

That seems a bit rude. Just look at the linked modules in this thread which have this implemented successfully.

Just released a new version of the module, which improves usage for systems without UI (running in a container f.e.):
https://github.com/skuethe/MMM-Spotify/releases/tag/v2.1.0

As there are updated dependencies, be sure to execute

git pull && npm install

inside the MMM-Spotify folder.

Again, if anybody is running into problems, please open issues in the github repo.

Update your MagicMirror² to the latest version: v2.15.0

@lavolp3 said in MMM-Spotify:

@lavolp3 said in MMM-Spotify:

Also, Volume is always at 100% for me. Played from the android app. API issue?

Confirmed API issue. Spotify API returns volume 100%, which is not the case in the app itself. Unfortunately.
Am I the only one having this issue?

Interesting. I have no issues with volume display and even the volume control (via touch). Works fine on all the different devices - haven’t tried android though.

• font sizes are hardcoded here, I would rather use the MM classes as reference from main.css. Meaning: giving the module and sub-elements a class “small”, “xsmall” by including the config option classes. I have done that already and works well.
• adjustable cover size.
• option to hide module when nothing is played
• spotify label small and more dimmed (like in MMM-NowPlayingOnSpotify

Let me know what you like to see as PR

Feel free to submit a PR for all those topics if you see them as a valid improvement!

@lavolp3 Hey there. Thanks for the feedback.

About the style: "mini" settings:

• what adjustments did you do to the picture and text sizes? This is currently still an open topic on my side - so if it is some general improvement for the module feel free to also create a PR for that
• I unfortunately don’t know what you exactly mean by “the scrolling title”. Could you elaborate?

About the minibar mode:
In my opinion this design breaks completely with the other two styles as it feels and looks completely different. In addition the implementation in the code is almost completely separated, which makes maintaining it an unnecessary effort.

To be honest - I don’t even know if it is still working or if some of the changes in the past broke usage of it.
I try to get feedback from people using it - if they want to keep it etc.

About the account name issue:
Great thanks - looking forward for your PR

Hi everybody. I am the new owner of this module (as of last year October). I haven’t monitored these forums / this post for problems so far. If you do have technical problems with this module please be so kind to directly open an issue in the git repo:

https://github.com/skuethe/MMM-Spotify/issues

It makes working on issues a lot easier. Thanks!

As to some of the open topics / questions here of the last weeks:

• @Abstr @razserv2010 I’ve recently re-worked the multi user authentication and fixed some problems with it:
  https://github.com/skuethe/MMM-Spotify/releases/tag/v2.0.1
• @crisvdn I am using it with MMM-Touch (which, of course, requires a touch screen) - it is a very powerful module
• @luizcarlosnery there is no direct option to do this. But you can definitely get something to work. There is a build-in config option to send custom notifications on suspend / resume:
  notificationsOnSuspend and notificationsOnResume - see README for more details
  You could, for example, use it in addition with MMM-pages which has some nice options to handle suspending / resuming special modules based on different pages

I hope that helps for now. I have some more fixes and improvements in the pipe that will be merged in the next comming weeks.

I really like this module, especially with touch screen usage.
The implementation is easy but still very powerful.

F.e. I added support for the following two modules:

• https://github.com/TeraTech/MMM-WiFiPassword
• https://github.com/skuethe/MMM-Spotify

In MMM-Spotify it is used to display account / device selection popups on screen. The available callback payload function makes this work in the first place, as we (of course) need to react on the made user selections :)

So again, great module, thanks!

@sdetweil
Thank you for the hint to MMM-ImagesPhotos, I didn’t stumble on that until now.

I will take a shot at it with the express server route. Thanks!

Hi everyone,

I started to play around with MM² just some weeks ago, and am currently in the phase of modifying a Module which displays background images from different sources.

One of these sources is a webdav behind basic authentication. Another source would be a “local directory” on the raspberry pi.

My approach is currently the following:

1. Start module, if source is set to “webdav” or “localdirectory” source, issue a sendSocketNotification to node_helper.js
2. node_helper is verifying the sources and creating an array of all images in that source. The array will contain the paths / URLs to each image, so f.e.:

imageList = [
  "https://WEBDAVHOST/path/to/some/image.jpg",
  "https://WEBDAVHOST/path/to/some/otherimage.jpg",
}

3. This array is returned via a new sendSocketNotification to the module
4. The module now has two different approaches:
   4.1 if it is webdav WITHOUT authentication, get one of the image src from the array and use it in getDom()
   4.2 Run a special function if it is webdav WITH authentication OR localdirectory. This special function is basically just base64 encoding one of the images from array and using that for the img srcattribute

4.2 is using base64 encoded images as

• we can’t reference local images from remote systems and
• I don’t want to add basic authentication as “https://USERNAME:PASSWORD@WEBDAVHOST” into the img src

Question / Problem
My problem occurs with 4.2, actually running the function to encode the image. As I only return an array with all the image paths / urls from node_helper and not the acutal images in base64 encoded data (which would probably blow up at some point, f.e. referencing a lot of 4k images), I have to encode them “just in time”. So on each request (images are just shown one at a time as background).

Now to my understanding (and testing) I am unable to add something like const fs = require("fs"); inside the main module, right? How could I actually fetch local files from the main module then?
Or, if this is not possible, how can I send a request from main module to node_helper and wait for its return / callback?

The same with the basic auth webdav option.
I tried using jQuery to inject basic auth header on image load, but that just fails with CORS (because the webdav solution currently has a bug with requiring -X OPTIONS call to be authenticated - which is wrong).
Nevertheless, I could be able to “work around” this bug with using nodes require("https"). But again, I am unable to include / load this into the main module and would need to wait for direct feedback of the node_helper on “just in time encoding”.

Am I going into a completly wrong direction here? Any suggestions how to handle this?