If it was the MMM-GoogleMapsTraffic module that you’re seeing errors with, I had to comment out the console.log line noted in this commit, which fixed the black screen issue I was having. https://github.com/vicmora/MMM-GoogleMapsTraffic/pull/24/commits/90f51f6f7a155241a4371106ea3ca899b20a7380

Hi, I’m Darren. I’m pretty new to MagicMirror, but am spending a lot of time on the forum trying to learn more about the project and learn to develop modules. I just posted up my first module (MMM-Smartthings). I also do administration for a woodworking forum (familywoodworking.org) so can offer some experience as to what we’ve done to mitigate spam. I’m happy to help out if you need me.

Yup, learning that. I had used someone else’s example and determined that wasn’t the correct way. I figured it’s worth admitting one’s mistakes as well as accomplishments. ;-)

I was just finishing up a new module and noticed other modules I had loaded weren’t looking quite right. Turns out my new module had a .title class that was adjusting the font size. Upon inspection in dev console the .title for other modules that had loaded prior to my new module were using my new module’s .title class.

Just thought it was worth mentioning that the custom css for modules can affect other modules in the event someone else is seeing css issues if your using common class names.

Ok, I think I’ve gotten things to where it’s ready to share, I posted it up on the modules forum…Thanks again for all the feedback.

https://forum.magicmirror.builders/topic/11270/mmm-smartthings

This is a module to display status information for devices connected to a Samsung Smartthings hub account.

https://github.com/buzzkc/MMM-Smartthings

Currently it’s limited to the following device capabilities: “switch”, “contactSensor”, “lock”, “temperatureMeasurement”, “relativeHumidityMeasurement”, & “motionSensor”

The frequency you update will depend on the number of devices you have. The api is limited to 250 requests per minute per app or device.

If you have issues or want to request additional features, please submit a bug report on the github repository.

[card:buzzkc/MMM-Smartthings]

I’ve fixed the duplication, added an excluded device name list, fixed some timing issues, and cleaned it up.

I’m not entirely happy with the way I’m getting all the data, but I haven’t quite figured out a good way to wait for all the promises returned from the smartthings-node library. I have to loop the capabilities, make a request to get devices by capability, wait for that promise, then loop devices to get the statuses for each, once those promises return I need to pair up the status with its device.

So the ugly of it is that I’m just pushing all the data via sockets for each status request into an array that gets updated, then it gets fed to the getDom(). Not pretty, but it’s working.

Well, looks like it’s duplicating some of the items in the array. I’ll get a patch uploaded for it soon.

Edit: Found this was due to having more than one browser open, each instance was updating the global array. Working on a fix.

I’ll start a new thread for this, but if anyone wants to try it out or PR it, keep in mind, it’s my first module. ;-)
https://github.com/buzzkc/MMM-Smartthings

Currently I’m only supporting a subset of device capabilities. I can only run one instance of the module also since everything is returned to a global array. More than one instance all the devices from each module instances get put into the array and the full list of devices displays on all instances rather than what was specified for that instance.

For multiple capabilities in the list, the display is sorted by device name, then by capability alphabetically.

It also displays devices for all locations, I’ll see if I can make this selective in the future, but fits my needs as it is.

Still working on getting things to refresh, but here is a teaser…

Let me know if the pic isn’t showing or disappears, using google photos

That looks nice!

Thanks Sam, That does help explain things. The grandkids are visiting, so will be a day or so before I get back to this, unless I just can’t sleep tonight. ;-)

I’ve made a little more progress on this, but nothing to display the device info yet. I found the node-smarthings library uses promises to return results, which I’ve not worked with specifically, so been struggling with tying the device information to the device capability status results. I think I’ve finally worked passed it, but still have some testing to do.

I’ve been trying to pass the device object from the first call to the call back function for the capability status, but not figured out how to do that. All of the status results were tied to the last device processed from the device callback. I did finally move the looping of devices to where only one device was sent to the socket notification that calls the capability status and seems to be working that way.

Thanks for creating this, my wife really likes seeing the progress on her projects.

Looks nice. I’m not using any glass either, just a wood frame around the monitor screen.

You probably can either show the map image or an iframe in MM. Use the querystring params to update the marker parameters…

https://developers.google.com/maps/documentation/maps-static/dev-guide

I’m finally starting to make some progress on this. I’ve been doing development in a docker instance and found editing files while the container is running corrupts files. :-)

So I have it connecting and bringing back device information at this point. I still need to parse that info. I’m working through the steps get all the info in the correct order to model it (get device ids>>get device components>>get device capabilities>>statuses etc.)

I do have two hubs and found that it brings back devices for all hubs, so I’ll need to get the hub info too.

Sorry, google photos don’t seem to stay around that long…

This is the css I use in my custom.css file to get a semi transparent shadowbox with rounded corners on my modules to make them easier to read over the slideshow background.

 .normal,
 .dimmed,
 header,
 body {
        color: #fff;
 }

 .module {
        background: rgba(0, 0, 0, 0.4);
        border-radius:15px;
        padding: 10px;
 }