Anyone working on integrating the nest protect smoke detectors?

@charp07 What was the fix to your Loading issue?

Initial test with @radokristof fork looks good. Doesn’t come up immedately at startTime, but soon after. Guess that has to do with the poll interval.

@yawns Thanks! Yeah that second link seems more or less exactly the same as what I’m trying to do. Looks like it has validated my approach.

@j-e-f-f Hi Jeff, amazing job on the css. Would you please share your files for me to learn? Thanks in advance. Vincent

I’ve hacked away at pretty much every module in order to tailor my display to my liking. While there’s a lot you can do with CSS, you’re limited when everything is laid out with tables, so I’ve found I’ve needed to change the markup in most modules. It would be nice if the modules abstracted the HTML out into a separate template file so that whenever I update a module, I don’t need to do a whole lot of reverse engineering to recreate my changes. Even better would be if you could specify an alternative template file in the module’s config. Then any subsequent update would not overwrite your customizations. I understand this would be a significant upgrade to the current code base, but maybe something to think about for a v3 of MagicMirror. -Jeff

Hello folks. I am in the research phase of my project, and I want to use a TV for my display mainly for the size. Seems the most economical way to get a larger smart mirror. But I have a couple of questions about doing so that I couldn’t find answers by searching. Will the TV respect native power saving commands from the raspberry pi like a normal monitor? e.g.: will it go into / come out of standby via commands through the HDMI connection? Like many here I’d like to use a motion sensor to wake up the display, and then have it go back into stand by after a certain period of time. I’m planing on using libCEC to explicitly issues sleep / wake commands. Will the TV’s native OSD be on the screen? e.g.: will I see text like “HDMI2” to indicate which input is active whenever the TV powers on from standby? When the HDMI signal is dropped, will I see “No Input Signal” on the mirror before the screen goes into standby? Will the TV need to be in the fully powered-on state before powering up the Raspberry Pi in order for the Pi to recognize the connected display? Or - as I’m hoping will be the case - will the Pi issue a wake command to bring the display out of stand by on initial boot? I’m considering the Samsung J5205 32" for this project, and I’ve seen a few tutorial videos that show how to access the service menu. Does anyone know if these tweaks can be only be made to affect either of the above points via the service menu or will the regular options menu cover this off? Alternatively I’m looking at using a BenQ PD3200Q monitor, but I can’t find a definitive answer to whether the Raspberry Pi can drive it at its native resolution of 2560 x 1440. I’ve seen some info to suggest that it may work at 15 Hz, which I think is fine for this application, but if anyone has real insight on this, that would be very helpful. The monitor costs about a third more that the TV, but I think the extra money is worth it if I can make use of the higher resolution. Thanks for any info - -Jeff