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

Hi,

I installed the module today with my Deconz gateway (not Hue).
Everything works fine but I´m not able to use my defined groups.
Lights are working great but the Hue bridge uses rooms and not groups, I think thats my problem.
The Deconz gateway uses only lights and groups.

The module MMM-Hue works great with the Deconz gateway but it´s basic. The new module looks much better.
Is there a way to fix this problem?

Regards,

Christian

Sure - open up the mmm-hue-lights.js file and go to line 670.

You’ll see a comment saying for the groups, let's immediately filter out anything that doesn't have a type of 'Room' and a code block that looks like this:

Object.keys(data.groups).forEach(function(key) {
    var itemType = data.groups[key].type.toLowerCase();
    if (itemType !== 'room') {
        delete data.groups[key];
     }
});

If you delete or uncomment that code block, it will no longer filter out anything that isn’t a room.

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

isnt updateinterval in ms?cause if it is then 60000 ms = 1min…

My bad - you’re right, it’s 1 minute :)

@costascontis You configuration looks fine - the updateInterval is set to 60000, so it’s only pulling data every 10 minutes.

What exactly do you mean that it “stops updating”?

@sean said in One-line switch to enable / disable modules:

@rudibarani @michael5r

Here is my version. No need to list all modules.

const pre_disabled = {
  "UNLISTED": true, // default value for unlisted other modules.
  "alert":false,
  "clock": false,
  "MMM-Remote-Control":false,
 }

var DISABLED = new Proxy(pre_disabled, {
  get (receiver, name) {
    return name in receiver ? receiver[name] : receiver["UNLISTED"]
  }
})

Lovely :thumbs_up_light_skin_tone:

@himuura said in Magic Mirror ServerOnly:

so michael if im using the AssistantMk2 module, i wont get charged right? how can i confirm that? And on the second part, i dont have the google home app, how can it read the system temperature of the mirror? any idea?

If you set up your Google project according to the instructions in the AssistantMk2 module, you’re only enabling the Google Assistant API - but you can always check the metrics for the Cloud Speech API just to be sure. Go to your project dashboard on the console.cloud.google.com site, click APIs & Services in the navigation to the left, then the Cloud Speech API to see whether you’re actually using any data.

(No matter what, Google is very nice about giving you tons of warnings before you hit any API limits, so you shouldn’t be worried about suddenly facing a huge bill.)

What do you mean by system temperature? Are you talking about the actual CPU/GPU temperature of your raspberry pi - like the data displayed by the MMM-Tools module?

It’s Google’s Cloud Speech API that costs money after the first 60 minutes - the Google Assistant API is free (well, the API limits are so high they’re pretty much non-existent).

I’m using MMM-AssistantMk2 with the MMM-Hotword module and have yet to find any reason to use the cloud speech API - the google assistant API works just fine.

In regards to your last question, if you’re using the google assistant API through MMM-AssistantMk2 you can get any sort of info that your google assistant has access to normally - eg. if you’re using the Google Home app and have added your thermostat in there, the assistant will be able to give you updates about the temperature.

Your version of npm is way too old - install the latest version through the terminal:
sudo npm install -g npm

In case someone else has this problem, instead of rebooting just run the following in your terminal:

kill -9 $(lsof -t -i :8080)

That’ll kill the current process on port 8080.

@eawalker1 You could try my nest-cameras module:
https://github.com/michael5r/mmm-nest-cameras

It autoplays the video.

Bear in mind that if you want to view a Nest camera video stream, the camera will need to be publicly shared - it doesn’t matter which MM module you use, there’s no getting around this currently.

@j-e-f-f Sure, that’s the magic of the overflow: hidden style. But what puzzles me is this:

An example:
If you run a webpage in fullscreen mode (either through Electron using Chromium or in a regular browser), and style the body like this:

body {
    background-color: #333;
    width: 100vw;
    height: 100vh;
    padding: 0;
    margin: 0;
    overflow: hidden;
}

you will have a grey area that takes up the entire width & height of your screen.

If, on the other hand, you styled the body tag like this:

body {
    background-color: #333;
    width: calc(100vw-10px);
    height: calc(100vh-10px);
    padding: 0;
    margin: 0;
    overflow: hidden;
}

you will have a grey area that is 10px shorter and narrower than the available screen space.

The only reason this wouldn’t be the case is if the html tag has a margin or padding (which would restrict the amount of space available to the body tag) or if you’ve specified a specific screen size directly in Electron (using electronOptions.width and electronOptions.height).

It’s no different than the standard body styles defined in MagicMirror’s main.css file - in there, a margin of 60px is set and then the height & width are set with width: calc(100%-120px) and height: calc(100%-120px) respectively.