Should work but keep two things in mind:

• The area outside of the monitor has to be covered from behind with something dark or you will be able to see through it, if there’s even a little bit of light behind it.
• The screen’s shape itself might still be visible because, unless you have an expensive LED screen where black means black, since there will always be some backlighting or clouding.

A good screen might have a good enough contrast so that you could use some tinted wrap on the whole backside of the mirror (or just on the screen) to counter that backlighting.

@cornusandu said in work in progress:

the raspberry will be running continuous until it will die i guess.

@cornusandu said in work in progress:

Any advice on raspberry power? Should I cut electricity 12 hours a night with a smart plug? Or run it 24/7? Which is better for longer life?

As everyone else said, leave it running, don’t cut the power without shutting the RasPi down safely first. Two advices I would give you:

1. When everything is set up and running, and everytime you add a new feature/module, make an image of your sd card as backup!
2. Think about a UPS, Uninterruptible Power Supply. There are some add ons that combine a batterie that provides power for a few minutes and a circuit that will detect the power outage and initiate a safe shutdown. And when the power goes back on, it will go back to normal.

I learned both the hard way, but I’m still not done finding/setting up a good UPS solution.

Sorry, but that doesn’t work. (It throws response.statusCode = 403, forbidden.) And it’s not surprising. As I said, the API source server doesn’t allow CORS and is not serving JSONP. So JavaScript calls are blocked.

There are a lot of fine tools for specific jobs, XMLHttpRequest, fetch, request, fs, …, and they work if CORS is set up correctly on the server, allowing you access, or it’s giving you JSONP to handle, but PHP’s file_get_contents is the hammer in your toolbox. If everything else fails, you still can throw this at your problem (provided you have allow_url_fopen).

And I know, it’s not always wise to use (or even throw) a hammer, access might be forbidden (to scripts) for a reason. But if you can read it in your browser, PHP can read, stringify and proxy it to your JS.

Nice, that looks really good! Hidden cables are the best! ;)

Love the floorplan, I’m working on something like that, too.

The API doesn’t allow CORS, so JS can’t get to it.

I’m from Hamburg, too. Cool module. Can’t really use it right now as I’m rarely using the HVV, but I might check it out and maybe play around with it a little.

That’s probably it. The developer console would probably have hinted at that, saying something like the next thing after the comma was expected to be something else.

While you’re removing the last comma in the clock module’s settings, also remove the three empty lines that follow.

{
     module: "clock",
     position: "top_left" // no comma
},

another example:

{
     module: "clock",
     position: "top_left", // comma, because "config" follows
     config: {
          displayType: "digital" // no comma
     } // no comma
},

Can you edit that and put the tags for code around it?

Might be the calendar’s settings, then. Google calendar?

That’s not how it works. The order in the config doesn’t matter, except for the order in wich they are loaded (within milliseconds). But all the modules have a “position” value as you noticed: “top_left” or “middle_center” That attached a class to the module and by that class, positions are dealt with.

These positions are set in the css/main.css but don’t change that file. If it’s not already there, set up a file named “custom.css” and edit it with a text editor. When you want to move “middle_center”, find it in the main.css, not it’s value and change it in the custom.css. You can copy and paste it.

.region.middle.center {
  top: 50%;
}

That means it’s positioned 50% down from the top of the screen, halfway in the middle. Play around with the percentage until it fits.

But you said “send it back” so I’m wondering if something changed its original position, maybe another module has some weird css settings that influences these settings or some changes happened before that messed up the original settings? If that’s the case it’s better to find out and change it back then to add new changes on top.