Hello,
I’ve created a quick module for an advent calendar. Is is customizable and the images can be chosen individual.
I’ve made this module quite quick after I got the ideas yesterday morning. I’ll refine it a little but I did’t want to let you wait any longer g
It could contain some bugs and may not be perfect at this time. Let me know what you notice, and I will try to improve it.
Hello,
finally I finished my first MM-module. I was struggling with the existing shelly modules so I decided to create a new one which uses only the cloud-api in order to be independent from the device itself.
The MMM-ShellyStatusTable module displays the switch status and power consumption of multiple Shelly devices in a table on the MagicMirror², including a total consumption sum. It regularly updates the data via the Shelly Cloud API Gen 1 and Gen 2+. So it should be independed from the devices in your smart home.
It is currently hard to say if every device is considered correctly. I have the following devices and it works:
Currently no translation is available. It will follow in the next days. But it is not hard to fix by your own, I hope.
I’m not really a module developer but ChatGPT finally fixed it :-)
Please try and give me a feedback if you discover some problems. Maybe I can help, but I’m no sure at all :laugh:
@KristjanESPERANTO Done. I’m not yet completely happy with the style. I’ll work on it next Summer :)
Hello,
After creating my first Shelly MMM module, I knew it was time for an upgrade. I wanted something with a more polished, visually appealing look than a basic table. Introducing my new module:
Example:
This module can also more or less replace the MMM-ShellyStatusTable. If a device is switched on or off it is dynamic displayed in the list.
Give it a try and give me Star ;)
Cheers,
Chris.
Hello,
I’m using EVCC for load PV surplus. Currently I’m using parts of the EVCC dashboard in an I-Frame. This is not as nice as it could be.
For all who don’t know what it is: EVCC.
Has anyone tried to create something for the MM project?
BR Chris.
Hello,
I’ve added one nice interactions to the module now. This took me some days to get it fully running. But now I’m quite happy with the result, so I also share it here again:
The state is written in the state.json file. So now your kids can “really” open a door in the morning and if you shut down your mirror in the night it has the same state after a reboot.
If you’re already running the module delete the state.json file if you feel that something does not work correct (I deleted it quite often during development so I can’t say if there could be an issue).
The update sounds easy but believe me for me it was not ;-)
@sdetweil Wow, thank you so much! Perfect :folded_hands: :grinning_face_with_big_eyes:
@0m4r There is a problem with the token. I think, I’m stupid, but:
You write for the config token: [YOUR_TOKEN]
So I’ve tried token:[1234567890], With this I get an error in the config.js and the mirror does not start up.
Then I’ve tried token:1234567890,. Same issue.
Then I’ve tried token:"1234567890", Then the config.js is okay and electron starts. But in this case I get an error message:
[ERROR] MMM-euro2024 fetchTeams 2018 {"message":"Your API token is invalid.","errorCode":400}
…of course I received a real API-key from Daniel. Copy+paste, so the key real in my config is okay.
How should I enter the API-Key? :thinking_face:
@roysim11 See the css in the calendar module. If this is Ext3 you’ll find this:
.CX3 .event.passed {
filter: brightness(0.8) grayscale(0.5);
opacity:0.5;
}
Then for example to this:
.CX3 .event.passed {
/* filter: brightness(0.8) grayscale(0.5);
opacity:0.5; */
}
Cheers,
Chris
Hello,
I’ve added one nice interactions to the module now. This took me some days to get it fully running. But now I’m quite happy with the result, so I also share it here again:
The state is written in the state.json file. So now your kids can “really” open a door in the morning and if you shut down your mirror in the night it has the same state after a reboot.
If you’re already running the module delete the state.json file if you feel that something does not work correct (I deleted it quite often during development so I can’t say if there could be an issue).
The update sounds easy but believe me for me it was not ;-)
@KristjanESPERANTO Done. I’m not yet completely happy with the style. I’ll work on it next Summer :)
Hello,
I’ve created a quick module for an advent calendar. Is is customizable and the images can be chosen individual.
I’ve made this module quite quick after I got the ideas yesterday morning. I’ll refine it a little but I did’t want to let you wait any longer g
It could contain some bugs and may not be perfect at this time. Let me know what you notice, and I will try to improve it.
@visionmaster Danke für die Antwort. Die Module sind in GitHub aktualisiert.
So, issue closed until new devices pop up ;-)
@visionmaster
Vielleicht einfacher als gedacht. Wieder als node_helper.js übernehmen:
const NodeHelper = require("node_helper");
const axios = require("axios");
module.exports = NodeHelper.create({
start: function () {
this.config = {};
setTimeout(() => {
console.log("MagicMirror is ready. Fetching ShellyPV status...");
this.fetchShellyPVStatus();
}, 15000); // Delay to ensure MagicMirror is fully loaded
},
socketNotificationReceived: function (notification, payload) {
if (notification === "CONFIG") {
this.config = payload;
if (this.config.shellysPV && Array.isArray(this.config.shellysPV)) {
console.log("Configuration received, fetching ShellyPV status...");
this.fetchShellyPVStatus();
}
} else if (notification === "GET_SHELLYPV_STATUS") {
this.fetchShellyPVStatus();
}
},
fetchShellyPVStatus: async function () {
const results = [];
if (!this.config.shellysPV || !Array.isArray(this.config.shellysPV)) {
console.error("No valid shellysPV configuration found or 'shellysPV' is not an array.");
return;
}
for (const shellyPV of this.config.shellysPV) {
try {
const response = await axios.post(
`${this.config.serverUri}/device/status`,
`id=${shellyPV.id}&auth_key=${this.config.authKey}`
);
const data = response.data?.data?.device_status;
if (data) {
let isOn = false;
let power = null;
// Check for Gen 1/2 structure (relay-based devices)
if (data.relays) {
const channel = parseInt(shellyPV.ch || 0, 10);
isOn = data.relays[channel]?.ison || false;
power = data.meters?.[channel]?.power || null;
}
// Check for Gen 3 structure (pm1:0 devices)
else if (data["pm1:0"]) {
isOn = true; // Assume true if data exists for the device
power = data["pm1:0"].apower; // Use 'apower' from pm1:0
}
// Check for "switch:0" structure
else if (data["switch:0"]) {
isOn = data["switch:0"].output; // Use 'output' for on/off status
power = data["switch:0"].apower; // Use 'apower' for power
}
// Check for RGB Shelly structure (lights array)
else if (data.lights) {
const light = data.lights[0]; // Assume single channel for RGB device
isOn = light?.ison || false;
power = light?.power || null;
}
results.push({
name: shellyPV.name,
isOn: isOn,
power: power !== undefined ? power : null,
statusClass: isOn ? 'on' : 'off', // Dynamically set status class
});
} else {
results.push({
name: shellyPV.name,
isOn: false,
power: null,
statusClass: 'off', // Default to off if no data found
});
}
} catch (error) {
console.error(`Error fetching status for ${shellyPV.name}:`, error);
results.push({
name: shellyPV.name,
isOn: false,
power: null,
statusClass: 'off', // Default to off on error
});
}
}
this.sendSocketNotification("SHELLYPV_STATUS_UPDATE", results);
},
});
In der config wieder wie üblich einrichten.
@visionmaster
Perfekt. Freut mich! Morgen probiere mich an der RGB Shelly. Kann es aber noch nicht versprechen. Wenn das läuft aktualisiere ich die Module für Table und PV bei Github.
Hi,
please replace the node_helper.js in the module MMM-ShellyPV with the following code. If you receive an error, please describe what you see or what error messages you get. Since I do not have such a device yet it is not possible for me to test it.
At first I start with the Shelly 2.5 device. The “shellyrgbw2” is then the next step!
The config must be like this for these specific 2.5 devices:
shellysPV: [
{ name: "Kueche 1", id: "dcda0cb93bb8", ch: "1" }, // Channel 1 (relay[0])
{ name: "Kueche 2", id: "dcda0cb93bb8", ch: "2" } // Channel 2 (relay[1])
]
I’ve used 1 and 2 instead of 0 and 1. It is easier for my head :-)
And next the updated node_helper.js file:
const NodeHelper = require("node_helper");
const axios = require("axios");
module.exports = NodeHelper.create({
start: function () {
this.config = {};
setTimeout(() => {
console.log("MagicMirror is ready. Fetching ShellyPV status...");
this.fetchShellyPVStatus();
}, 15000); // Delay to ensure MagicMirror is fully loaded
},
socketNotificationReceived: function (notification, payload) {
if (notification === "CONFIG") {
this.config = payload;
if (this.config.shellysPV && Array.isArray(this.config.shellysPV)) {
console.log("Configuration received, fetching ShellyPV status...");
this.fetchShellyPVStatus();
}
} else if (notification === "GET_SHELLYPV_STATUS") {
this.fetchShellyPVStatus();
}
},
fetchShellyPVStatus: async function () {
const results = [];
if (!this.config.shellysPV || !Array.isArray(this.config.shellysPV)) {
console.error("No valid shellysPV configuration found or 'shellysPV' is not an array.");
return;
}
for (const shellyPV of this.config.shellysPV) {
try {
const response = await axios.post(
`${this.config.serverUri}/device/status`,
`id=${shellyPV.id}&auth_key=${this.config.authKey}`
);
const data = response.data?.data?.device_status;
if (data) {
let isOn = false;
let power = null;
// Handle multi-channel devices
if (data.relays && shellyPV.ch) {
const channelIndex = parseInt(shellyPV.ch, 10) - 1; // Convert to zero-based index
if (channelIndex >= 0 && channelIndex < data.relays.length) {
const relay = data.relays[channelIndex];
const meter = data.meters?.[channelIndex];
isOn = relay.ison;
power = meter?.power || 0;
} else {
console.error(`Invalid channel index for ${shellyPV.name}: ${shellyPV.ch}`);
}
}
// Handle single-channel devices (or default behavior for Gen 1/2)
else if (data.relays) {
isOn = data.relays[0].ison;
power = data.meters ? data.meters[0].power : null;
}
// Handle Gen 3 devices (pm1:0 structure)
else if (data["pm1:0"]) {
isOn = true; // Assume true if data exists
power = data["pm1:0"].apower;
}
// Handle switch:0 structure
else if (data["switch:0"]) {
isOn = data["switch:0"].output;
power = data["switch:0"].apower;
}
results.push({
name: shellyPV.name,
isOn: isOn,
power: power !== undefined ? power : null,
statusClass: isOn ? 'on' : 'off', // Dynamically set status class
});
} else {
results.push({
name: shellyPV.name,
isOn: false,
power: null,
statusClass: 'off', // Default to off if no data found
});
}
} catch (error) {
console.error(`Error fetching status for ${shellyPV.name}:`, error);
results.push({
name: shellyPV.name,
isOn: false,
power: null,
statusClass: 'off', // Default to off on error
});
}
}
this.sendSocketNotification("SHELLYPV_STATUS_UPDATE", results);
},
});
For devices without a ch parameter, the logic defaults to using the first relay and meter (relays[0], meters[0]), ensuring compatibility with single-channel or older devices.
If a ch parameter is specified in the config, the code now accesses the corresponding relays and meters arrays for the specific channel.
@visionmaster Hi, werde es mir morgen anschauen. Danke für die Infos.
@visionmaster Hi, sehe ich mir an. Solche Geräte habe ich im Moment noch nicht im Einsatz. Schicke in der Console mal diesen Befehl an die entsprechende Shelly und poste mir die Antwort:
curl -X POST https://<server_uri>/device/status -d "id=<device_id>&auth_key=<auth_key>"
In der Antwort Deinen Auth-key löschen!
Vielleicht werden hier mehrere Infos zurückgeschickt.
@roysim11 See the css in the calendar module. If this is Ext3 you’ll find this:
.CX3 .event.passed {
filter: brightness(0.8) grayscale(0.5);
opacity:0.5;
}
Then for example to this:
.CX3 .event.passed {
/* filter: brightness(0.8) grayscale(0.5);
opacity:0.5; */
}
Cheers,
Chris