@zerodegree79 great - wasn’t sure from your comment whether you’d spotted the option on the config.

After a quick look, I’ve pushed a change to the module which includes virtual activities in the chart stats. Take a look and let me know if this works as expected.

@zerodegree79

You should be able to hide swim activities by adding the following to your config

activities: ["ride", "run"]

Adding other activity types will need some investigation of the Strava API as ActivityStats only returns totals for the three activity types currently available.

I need to look at the module again shortly as there is an change to the API which requires a different authentication mechanism so I’ll try an pick this up then

[card:ianperrin/MMM-NetworkScanner]

After a long time in the wilderness, I have found a little time to review the state of this module. Given other commitments, I’m not able to make any promises that everything will be fixed, but I’d like to see what can be done and at least restore broken functionality.

To kick off, I have pushed a series of updates to the repository as an initial attempt to introduce some fixes. Please feel free to pull these changes and test in your mirror. Due to the state of the current codebase (did I really write this?), it’s possible further issues may be introduced, do please bear with me.

So, here’s a request. If you use the module, but have issues, can you create (or add to an existing) issue on GitHub. Please provide as much info as possible, including a description of the problem, what you were expecting to happen, the config for the module and any errors from the log and/or browser console.

If you’re interesting in helping (re)develop this module - this would be much appreciated - send me a direct message.

Hi @flo269 - are you able to review the console in the browser and see if there are any errors there?

@Henrik

It’s not possible for MMM-ModuleScheduler to affect the behaviour of the modules it hides/shows.

However, it is possible for a modules to ‘react’ to being shown/hidden.

To reduce the API calls the developer of the modules you use could implement/subclass the suspend and resume methods.

@Peter it’s worth noting that the API isn’t immediately updated following each race so hang in there, the data usually updates by the end of the same day of the race

Hi all

Really sorry about the lack of progress/development on this module. I’ve been consumed by renovations at home and starting a new job.

There are clearly still issues with the module. Unfortunately I am not going to be able to look into them for some time yet. So, if there is someone who can pick up the baton and submit a pull request that would be great.

Ian

@Mar - Unfortunately we are in the hands of the API provider as to when the 2017 data is considered ‘current’.

The work around is to make sure you have the latest version of the module then temporarily set the season option to ‘2017’, e.g.

        {
            module: 'MMM-Formula1',
            position: 'top_right',
            header: 'F1 Standings',
            config: {
                season: '2017'
            }
        },

@binderth

Did you restart the mirror after the upgrade?
Are there any errors in the browser console?
What happens if debug is set to true?

@binderth, @pugsly

There is a (currently undocumented) debug config option in the module which minimises the logging. By default it should be set to false, but you can explicitly set it yourself

i.e. debug: false,

In earlier versions it had little effect, but in the latest commit, it should significantly reduce the volume of logging.

See how it goes

@bminer1, @binderth

I’m going to be taking a look at the notifications functionally after the issues with the current release have been resolved.

@derek7467

If you can provide the arp-scan command for this, an option could be added to support it - once the current issues are fixed of course ;)

Cc @bluedoors

@bminer1, @pugsly, @Speedy-one

I’m still working through the issues introduced last weeekend, but have just added a commitwhich attempts to resolve the duplicate devices issue. I’d be grateful if you could try it out and confirm.

Hi all

The updates last week seem to have introduced a few issues - sorry folks!

I’ve quashed one bug with MAC Address scans which you can git pull from the repo to see if that helps, but there still appear to be a few others which need resolving.

I am looking at it but please bear with me ;)

@outjet I’ve not been able to spend much time on the Mirror (or this module) recently but I’ve just updated the module to include @BenNewsome’s additional functionality along with a showLastSeen option

Can you try updating your module and adding this to your config.js file e.g. showLastSeen: true,

@BenNewsome Hi Ben - I’m commited elsewhere at the moment so sorry for not getting back to you sooner. Thanks for the pull request - I’ve accepted it and merged it into the module for all to share!

As @yawns points out its down to the individual modules to implement/subclass the suspend and resume methods which in turn can be used to control when background activity is performed.

This has been around since MM 2.0, so ModuleScheduler doesn’t make any attempt to control the functionality of the modules other than show, hide, dim and send notifications.

Hope this helps

Hi @anatius (Christian)

Okay, I think I see the problem, and a fix is in the works, its just going to take a little time until I can finish it.

I’ve created an issue on github which contains more details on why this is happening.

Until the fix is in place, you have two (understandably sub-optimal) options

• leave the mirror running and it should self-correct after the next 8pm and/or 7/8am depending on when it is started :(
• temporarily use the same expression for all days of the week, e.g.

global_schedule: [ {from: '0 7 * * *', to: '0 20 * * *', dimLevel: '30'} ]

@strawberry-3.141 Any chance you could fix the icon for Sheffield Wednesday in the English Championship too (league 427)?