i think both frequently used apis (darksky and weatherunderground) have both gone to pay for use models…

I am not aware of another free api

if you got an api key before IBM closed free access, the api key still works (for how long I don’t know)… mine still does

Description

Enable MagicMirror sleep from external (camera) sources

If you are running the MM on a non PI device, or want to control sleep/wake without having to wire up another device, this module will take external info and signal MM to sleep or wake up.

I use a Webcam camera for the motion detection, driven by the github Motion project.
That project allows for a script to be run when motion starts and ends. I provide a script that
creates a file for both events, and the module detects those files.

the module supports sleep and wake 3 different ways… On PI using the tvservice command, or the exec dpms command if not using HDMI, or hiding all modules if using an energystar monitor (like my tv)

I have submitted changes to MMM-voice and HelloLucy to allow our modules to know about the others processing… so voice Go To Sleep and motion wakeup work… if using the Hide method, modules already hidden at sleep will remain hidden on wakeup.

Download:

[card:sdetweil/MMM-SleepWake]

---

Version 1.0

@teitlebot you didn’t post the script

this fix is now added to the develop branch, and will be merged to master at some time.
Thanks Mitch

@andurii npm has a remove operation

npm remove electron
npm install electron@1.7.9

I had to uninstall electron and install version 1.7.9 to get rid of the blank screen

ok, this is a bug/limitation… the js/main.js.hideModule() method doesn’t call the callback if there is no dom content…, and there is no dom content if no module position is defined… (per UpdateDom not working)

my module has no dom content, but I need the suspend notification

i have opened issue 1308

this Debian Stretch: deactivate screen blanking

says

add those lines to

/home/pi/.config/lxsession/LXDE-pi/autostart 

note that is a file that is USER based…

@strawberry-3-141 said in MMM-voice wont register commands:

@sdetweil the original idea was that every supported module has it’s on mode, so modules can have the same commands without conflicts. And then you enter the mode and you can use commands of that module as long as you dont change the mode.

To change the mode you need to say the name of the mode as the first thing in your sentence, only the keyword can be before if necessery. Otherwise it will not detect a change mode

ok, so mode is really ‘context’ so you could speak to a single module