@Cr4z33 said in Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream:

MMM-RTSPStream

The position is incorrect. There is no middle\_center position.

@mumblebaj

Update v2.1.3 - Released

• Added animation to the lines to show a visual effect of charging or discharging. Have been wanting to do this for a while and only had the chance to implement this.

The above change is on my dev branch being tested by myself. I welcome others to checkout the dev branch and assist with testing. Everything looks good thus far. If no issues raised against the dev branch then I will release to main over the weekend.

Couple of examples below showcasing the changes.

@com1cedric MMM-page-indicator was updated recently so you do not have to use the nth-child stuff anymore. Checkout the latest version and the readme. I have added some samples of how you can use it. You should reference the svg as either @sdetweil or @karsten13 has shown and it should work.

@dathbe I have cleaned up a bit of the old code and done some changes. Before submitting the PR, do a git pull and test first.

@dathbe I replaced node-fetch a while back. Maybe do a git pull first.

@dathbe I have updated and pushed update v1.3.2. Please test and advise.

@dathbe Hi. Unfortunately I did not get those notifications. You can submit a PR and I will review for you.

@evroom *.lock should not cause an issue. I have same on my system and no issues with it. I agree with the wayland-1 change to wayland-0.

@ChrisLeduex Never use sudo to install anything on your mirror. Ideally you want to be in the module folder that requires request, i…e cd ~/MagicMirror/modules/MMM-PetFinder/. Once in the folder you want to then install request , npm i request. You can ignore the funding stuff.

@Sam-0 Can you run the following from the command line and she your results:
wlr-randr
ls -als /run/user/1000/wayland*

Share your results. Either the wayland-1 is different as indicated by @evroom or HDMI-A-1 is actually a different version on your system.

Share the results from the above and we take it from there. Also, @evroom has indicated the there is supposed to be a space before /home on the crontab.

@sdetweil And just to note, MMM-pages is zero based. This will need to be updated as well. If I understand MMM-Carousel correct, it is also zero based.

@sdetweil Yes, that is correct. I added a classname page-${i}. But the standard code was always zero based and I do not want to update that. It is tied in with MMM-pages and seems like it works with others as well.

start() {
  this.curPage = 0;
  this.mmmPagesDetected = false;
},

@Xx_Codeur_xX You could have a look at some of the modules that already does this. They get the weather from the default weather module, no need to redo this as it is already available.

See either of the below.
https://github.com/fruestueck/MMM-WeatherDependentClothes
or
https://github.com/Lavve/MMM-WeatherOutfit/tree/main

@sdetweil Yeah, i would agree. Changing that logic now may have some repercussions for users already using the module.

@sdetweil Correct. Although, MMM-page-indicator is 0 based, same as MMM-pages, so page-0 would be page 1 etc.

@sdetweil Not sure if I understand you properly but the other pages would default to the standard circle. The changes I made allows you to target specific pages if you want to change the icon, add animations etc. A little easier to target individuals.

@com1cedric I have submitted a PR for MMM-page-indicator which should give more flexibility per page. See example below:

.MMM-page-indicator .fa.indicator.page-2::before {
    content:"\f005";
    color: orange !important;
}

.MMM-page-indicator .indicator.active-page {
   animation: pulse 1.2s ease-in-out infinite;
}

If PR is accepted you should be able to target specific page indicators as shown in example above from custom.css.

You could use this fork in the meanwhile:
MMM-page-indicator

@Sam-0 Have a look at my post about this.

https://forum.magicmirror.builders/topic/19116/having-trouble-with-screen-on-and-off-here-are-some-tips-that-could-help?_=1743776945326

@veny Just restarting the MM does not resolve the issue with the weather module freezing. We need to find why the weather module freezes. Maybe turn on Debug in the config and then see if there are any errors on the next freeze?

@chichi1887 I have seen that the node-tado-client npmjs package has been updated to v1.0.0 to cater for the new OAuth2 flow. I would suggest opening an issue on the module Github page for the module developer to fix.