Posts made by michael5r

@JohnBachini said in MMM-Nest-Status - New module for your Nest thermostats and protect smoke detectors!:

@michael5r
Is this the same token obtained doing this .??

https://github.com/USA-RedDragon/badnest

No - the token my module needs is the old “Works with Nest API”-token.

@jasim Sorry, I don’t speak German - can you please post in english?

@jasim Yeah, but you must have set it up at some time - for instance, I use pm2 on my mirrors, so I can do pm2 stop mm to stop my magic mirror instance.

@jasim You already have another instance of Magic Mirror running (that’s the EADDRINUSE error) - you’ll need to stop that before running npm start dev. How do you normally start/stop your mirror?

@jasim You need to be in the folder of your Magic Mirror installation when you run these commands.

@jasim said in MMM-Hue-Lights - new module for your Philips Hue lights!:

@michael5r said in MMM-Hue-Lights - new module for your Philips Hue lights!:

@jasim said in MMM-Hue-Lights - new module for your Philips Hue lights!:

I updated the module and tested it for several hours. The module fails after 45 - 60 minutes (API ERROR) and no longer works.
And not only that, the entire mirror no longer works.
After removing the module from the mirror, the mirror works again.

Can you try running your mirror in dev mode and post some logs?

Would you tell me what to do, I am a layperson and not a professional.

Instead of running npm run start in your Magic Mirror folder to start the mirror, try running npm start dev which will open a browser console next to your mirror instance. Then look for any errors (marked in red) in there.

@jasim said in MMM-Hue-Lights - new module for your Philips Hue lights!:

I updated the module and tested it for several hours. The module fails after 45 - 60 minutes (API ERROR) and no longer works.
And not only that, the entire mirror no longer works.
After removing the module from the mirror, the mirror works again.

Can you try running your mirror in dev mode and post some logs?

I’ve released a new 1.4.0 version of this module that will hopefully help with the refresh issue - it now automatically reschedules an update, no matter whether there’s an error or not. Thanks to @ulrichwisser for pushing this fix.

Please download the version and see if that solves your issues.

@jordes said in MMM-Energy-Saver - an easy way to suspend/resume modules based on a PIR sensor.:

how should the MMM-Pir-Sensor be set up for this module to work?
This is my code:

  {
                module: 'MMM-PIR-Sensor',
                config: {
sensorPin: "23",
                        // See 'Configuration options' for more information.
                }
        }, 


{
    module: "mmm-energy-saver",
    config: {
triggerMonitor: "true",
timeoutInSeconds: "3",
        // ... whatever configuration options you want to use
    }
},

This is how I have mine set up:

{
    module: 'MMM-PIR-Sensor',
    config: {
        sensorPin: 17,
        powerSavingDelay: 0,
        powerSavingNotification: false,
        powerSaving: false // Should the monitor be turned off if no user is present? (via HDMI or relay)
    }
},

@kash said in MMM-Nest-Status - New module for your Nest thermostats and protect smoke detectors!:

@michael5r
i have not migrated to a google account yet and still have a existing developers account. how do i get the token?

Download the previous version of the module:
https://github.com/michael5r/mmm-nest-status/tree/fcbf291a26374e32901e993f9e109465819f59bf

It has the shell script that allows you to get a token.