I want to have a powerwall, a solar panel and a tesla just to try out this module!
My total bill for the set was over $100k, so I wouldn’t recommend it as purely dev kit. That said, I love them all.
I just upgraded to the latest version, and most of my modules are broken, specifically any module that uses a node_helper. It looks like messages from the modules are reaching the helper, but no responses are coming back to the client.
I tried re-cloning the MM repo and copying over the config/modules with a fresh
npm install, but it produces the same result. I feel like I’m missing something basic here, but I’m not sure what else to check.
@mumblebaj, chart.js needs to come from npm. If you do
npm install chart.js, what does it say?
Also, recent versions have taken a couple of dependencies that require newer Node versions – what version are you running? (
I see the exceptions thrown on retrieving Storm Watch status; I’ve just pushed a commit to ensure that skips if it gets null back for now. However, besides log pollution, that shouldn’t actually be breaking anything – Node will log that it failed and move on to the next message.
Running on a Raspberry Pi 4, and one of my calendar feeds has emoji in the event names. When accessing the MM with a browser, they display fine; on the screen connected to the Pi, however, they’re just little squares.
I know this is more likely an electron, Node, or XWindows issue than MM itself, but has anyone found a solution for getting emoji to render properly?
@NicB72, I’d love to work with you on both of these.
The intent is that the car tile will periodically rotate through the cars on the account; if cars are charging and your TWC is capable of reporting VINs (not all are), then it will show the cars currently charging; otherwise, it rotates through all of them on your Tesla account.
Now, the limiting factor: I only have one Tesla vehicle, so I’ve never been able to test that code path with several. Sounds like it’s not working. Send me a private message, and we can hopefully figure out why. If you’re moderately handy with webdev, you might want to put breakpoints in the functions focusOnVehicles() and advanceToNextVehicle() to figure out why they’re always choosing the same vehicle.
The way I’d expect it to work with MMM-Carousel is that you’ll have multiple instances of MMM-Powerwall, each displaying a single graph. MMM-Carousel would then be responsible for rotating through the several instances, while the messages from the node_helper make them all stay in sync. (Though now that you mention it, there might be a bit of conflict between the CarCharging graph rotating between cars and MMM-Carousel rotating through all of them. Hm.) There’s a fork of MMM-Carousel that has more robust support for multiple instances of the same module in slides mode, though the original might work fine in global or positional mode.
When you say they’re tiny… How tiny? The individual graphs are currently fixed-size at 430x250; if that’s too large for your screen, you might have some success with a CSS scale() transform.
Displays a collection of live graphs with data from your Tesla Powerwall (and TWCManager, if you have one) on your Magic Mirror.
This module implements several different graphs. Currently, these are:
By default, all are displayed. However, as needed by your layout, you can
instantiate multiple instances of this module, each displaying different graphs
or even targeting different Powerwall systems. Multiple instances referencing the same target will still update simultaneously and will not increase the volume of
requests made to either local or cloud endpoints.