# \[APP\]\[Pro\] Dashboard Studio - A completely free-form dashboard designer

**URL:** <https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169>\
**Category:** Apps\
**Tags:** dashboard, homey-pro\
**Created:** [February 15, 2026, 7:45pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169 "2026-02-15T19:45:30Z")\
**Posts on this page:** 20\
**Page:** 78

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 23, 2026, 12:11pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1560 "2026-10-23T12:11:29Z")

</div>

A user sent in two crash reports, but because these are submitted anonymously, I cannot reach out directly to ask follow-up questions.

One clear pattern in the logs is that the app crashed right while serializing a massive SVG graph (looks like a rain radar / forecast chart with timestamps) transmitted via a flow card. Homey gives apps a strict memory ceiling of about 64 MB. Because Dashboard Studio caches recent topic values in memory so dashboards can immediately display them on load/reload, caching and serializing such a large SVG pushed the memory over the edge and forced Homey to restart the app. My guess is that user @Amersfoort is mistreating his poor Homey? 😉

An oversight on my end was never anticipating that custom event topic payloads would be anywhere near this large. From the V1, the largest expected datasets were just Insight graphs and status values.

I have several memory optimizations lined up for the upcoming version. However, on the user side, keeping dynamic SVG or image payloads lean before pushing entire SVG codebases through flow events will definitely help keep Homey happy as well.

Either way, these crash logs are very helpful. If you sent them in, please drop a message in this thread describing what you where doing that lead to the crash. That makes it much easier to pinpoint the exact flow, ask clarifying questions, and get things sorted quickly.

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [October 23, 2026, 1:57pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1561 "2026-10-23T13:57:37Z")

</div>

So many memory usage numbers, I am confused:

- Windows Chrome says 853 MB memory usage for the Viewer (no extensions active)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/f/6f29290f6dfb2cdaa809df84e463ad819dba186c.png)
- The DS Diagnostics says 181.1 MB alloc and JS Heap 119.9 MB (Editor, else I can’t show this number)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/d/8d297a6cf29a1e0c6d1cc9eaedeb8b3a28bcd3ec.png)

> [@Satoer](#):
>
> Homey gives apps a strict memory ceiling of about 64 MB.

- The Homey app on Android says memory usage of DS is 118.9 (or is that a different memory?)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/5/6599aec96570da1ae4ccad3f733ff67ba34836b5.jpeg)

> [@Satoer](#):
>
> Every hour???

Yes, I restart the DS app every hour via a flow. I now can see the memory gets cleaned after a few minutes(?), without a restart. Could a memory clearance of a page immediately after closing a page be a solution, or is this already happening?

> [@Satoer](#):
>
> And what machine becomes unresponsive.

The tablet (8 GB of internal memory) and the PC (64 GB of internal memory) behave as expected; however, after opening many pages, the SVG or Markdown content sometimes fails to display, while the rest of the screen remains visible.

> [@Satoer](#):
>
> A user sent in two crash reports, but because these are submitted anonymously, I cannot reach out directly to ask follow-up questions.

I experienced 2 crashes in DS this week, but I did not click the “send crash report” button. Apparently, data is being sent regardless. It is no longer reproducible.

> [@Satoer](#):
>
> My guess is that user @Amersfoort is mistreating his poor Homey? 😉

I would like to rephrase this: poor user @Amersfoort has been mistreated by the hard- and/or software. 😇

> [@Satoer](#):
>
> From the V1, the largest expected datasets were just Insight graphs and status values.

I recently replaced \>10 Insights with SVGs because I couldn’t get the y-axis values ​​on the charts to display correctly (they resulted in unwanted, unusual intervals, making them difficult to read). I have reported this issue several times, but unfortunately, there is no solution (yet).

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 23, 2026, 3:39pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1562 "2026-10-23T15:39:20Z")

</div>

> [@Amersfoort](#):
>
> - Windows Chrome says 853 MB memory usage for the Viewer (no extensions active)
> 
> - The DS Diagnostics says 181.1 MB alloc and JS Heap 119.9 MB (Editor, else I can’t show this number)

It is only showing the memory JavaScript (JS) is using. The 853 MB is the whole dashboard, including all images, fonts, and on-screen graphics etc.

I made that page so users could easily send me setup details. I regularly ask for things like console errors or OS and browser info, so I figured a single click doing that would be much more useful than trying to teach people how to open developer tools 😅

> [@Amersfoort](#):
>
> Apparently, data is being sent regardless. It is no longer reproducible.

I don’t think so, because there was a user comment attached to one report.

> [@Amersfoort](#):
>
> > [@Satoer](#):
> >
> > Homey gives apps a strict memory ceiling of about 64 MB.
> 
> - The Homey app on Android says memory usage of DS is 118.9 (or is that a different memory?)

Yes and no. The 64 MB limit is specifically what the app itself can use inside the JavaScript runtime, not the total OS memory footprint. That figure might also differ a bit between the Homey 2019, 2023, and 2026 models though (I have not investigated this, so I could be wrong)

> [@Amersfoort](#):
>
> I recently replaced \>10 Insights with SVGs because I couldn’t get the y-axis values ​​on the charts to display correctly (they resulted in unwanted, unusual intervals, making them difficult to read).

Well, that is probably the main culprit behind the crashes and huge memory spike 😅

> [@Amersfoort](#):
>
> I have reported this issue several times, but unfortunately, there is no solution (yet).

I understand, but as I mentioned earlier, I am already building an improved graph widget that supports multiple data streams, and this fix will be included with it. It just isn’t ready yet. It turned out to be more complex than anticipated, especially handling edge cases where users feed in wild time ranges, mismatched intervals, or live streams.

I will roll it out as soon as it is solid, but I cannot commit to a hard timeline. Over the past month I have already poured more than full-time hours into this project. Because the development of DS is between paid projects, progress can pause without much notice. Lately my primary focus has been performance optimization and general usability, and since not many folks reported frustration with the Y-axis tick intervals, it ended up lower on the priority pile.

Could you share the code you used to render those SVGs? If it handles the Y-axis distribution nicely, maybe I can adapt parts of your approach.

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [October 24, 2026, 8:17am UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1563 "2026-10-24T08:17:42Z")

</div>

> [@Satoer](#):
>
> Could you share the code you used to render those SVGs? If it handles the Y-axis distribution nicely, maybe I can adapt parts of your approach.

Result in house air quality graphs:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/e/0edbb175a577c22953ed261d357cb6d39d083d11.jpeg)  
Flows creating SVGs:  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/2/72eb1f3922f8203b0665a855b452d7c3afb519fb.png)  
Homey script creating SVG (largely generated by AI in Dutch):

```auto
/**
 * Homey Script voor het ophalen van Insights data en het genereren van een dynamische SVG-lijngrafiek.
 * Controleert de 6 configuratieparameters en toont bij een fout een SVG-foutmelding in plaats van defaults.
 *
 * Nieuw: de grafieklijn kan worden afgevlakt met een voortschrijdend gemiddelde.
 * Stel de sterkte van de afvlakking in met de constante 'afvlakkingVenster' (sectie 2).
 */

// ==========================================
// 1. INPUT VERWERKING & PARAMETER CONTROLE
// ==========================================

// De invoer komt binnen als eerste argument van de flow (JSON-object of JSON-tekst)
let dataInput = args[0];

// Als de invoer een tekst is, proberen we deze om te zetten naar een object
if (typeof dataInput === 'string') {
    try {
        // Enkele aanhalingstekens vervangen door dubbele, zodat de tekst geldige JSON wordt
        let gefixteJson = dataInput.replace(/'/g, '"');
        dataInput = JSON.parse(gefixteJson);

        // Tijdelijke variabele direct vrijgeven voor de Garbage Collector
        gefixteJson = null;
    } catch (fout) {
        console.error('Fout bij het parsen van input JSON:', fout);
        return genereerSvgFoutmelding('Fout bij parsen van input JSON.');
    }
}

// Validatie of dataInput een geldig object is (geen null, geen array, geen tekst)
if (!dataInput || typeof dataInput !== 'object' || Array.isArray(dataInput)) {
    console.error('Ongeldige input: args[0] moet een JSON-object zijn.');
    return genereerSvgFoutmelding('Ongeldige input: Geen geldig JSON-object ontvangen.');
}

// Uitlezen van de 6 verplichte configuratieparameters
let grafiekTitel = dataInput.grafiekTitel;
let yAsTitel = dataInput.yAsTitel;
let xAsTitel = dataInput.xAsTitel;
let apparaatId = dataInput.apparaatId;
let capabilityNaam = dataInput.capabilityNaam;
let inzichtenResolutie = dataInput.inzichtenResolutie;

// Strenge controle of alle 6 parameters aanwezig en niet leeg/ongeldig zijn
if (!grafiekTitel || typeof grafiekTitel !== 'string' || grafiekTitel.trim() === '') {
    return genereerSvgFoutmelding('Configuratiefout: \'grafiekTitel\' ontbreekt of is leeg.');
}
if (!yAsTitel || typeof yAsTitel !== 'string' || yAsTitel.trim() === '') {
    return genereerSvgFoutmelding('Configuratiefout: \'yAsTitel\' ontbreekt of is leeg.');
}
if (!xAsTitel || typeof xAsTitel !== 'string' || xAsTitel.trim() === '') {
    return genereerSvgFoutmelding('Configuratiefout: \'xAsTitel\' ontbreekt of is leeg.');
}
if (!apparaatId || typeof apparaatId !== 'string' || apparaatId.trim() === '') {
    return genereerSvgFoutmelding('Configuratiefout: \'apparaatId\' ontbreekt of is leeg.');
}
if (!capabilityNaam || typeof capabilityNaam !== 'string' || capabilityNaam.trim() === '') {
    return genereerSvgFoutmelding('Configuratiefout: \'capabilityNaam\' ontbreekt of is leeg.');
}
if (!inzichtenResolutie || typeof inzichtenResolutie !== 'string' || inzichtenResolutie.trim() === '') {
    return genereerSvgFoutmelding('Configuratiefout: \'inzichtenResolutie\' ontbreekt of is leeg.');
}

// ==========================================
// 2. OVERIGE CONFIGURATIE & VARIABELEN
// ==========================================

// Lettergrootte instellingen (pt)
const fontGrootteTitel = 23;
const fontGrootteLabels = 18;
const fontGrootteTitelsAssen = 18;

// Kleurinstellingen (CSS / Hex)
const kleurLijn = '#80B3FF';
const kleurVulling = '#1D4ED8';
const transparantieVulling = 0.25;
const kleurAssen = '#FFFFFF';
const kleurGridLijnen = '#ffffff44';

// Canvas afmetingen en marges
const canvasBreedte = 900;
const canvasHoogte = 340;

const margeLinks = 95;
const margeRechts = 20;
const margeBoven = 25;
const margeOnder = 60;

// Marge boven en onder de data, als fractie van het databereik (0.05 = 5%)
const margeFractieData = 0.05;

// Y-as intervallen instellingen
const streefAantalYStappen = 5;
const minimaalAantalYStappen = 3;
const maximaalAantalYStappen = 8;
const strafPerAfwijkendeStap = 0.04;

// Afvlakking van de grafieklijn: aantal meetpunten waarover een voortschrijdend
// gemiddelde wordt genomen. Gebruik bij voorkeur een oneven getal.
// 1 = geen afvlakking (ruwe data)
// 5 = licht afgevlakt
// 9 = gemiddeld afgevlakt
// 15 = sterk afgevlakt
// 25 = zeer sterk afgevlakt (alleen de hoofdlijn blijft over)
// Een even getal werkt als het volgende oneven getal (8 geeft hetzelfde als 9).
const afvlakkingVenster = 9;

// ==========================================
// 3. OPHALEN VAN INSIGHTS DATA
// ==========================================

// Tijdelijke variabelen voor het ophalen van de data
let logboeken = null;
let doelLog = null;
let inzichtenData = null;

// Hulparray met per meetpunt: l = x-aslabel (uurnummer of null), v = gemeten waarde
let meetResultatenLijst = [];

try {
    // Stap 1: Haal alle beschikbare Insights logboeken op
    logboeken = await Homey.insights.getLogs();

    // Converteer naar een array (de API geeft soms een object terug)
    const logsArray = Array.isArray(logboeken) ? logboeken : Object.values(logboeken || {});

    // Stap 2: Zoek het juiste logboek op basis van de device ID en capability
    doelLog = logsArray.find(log =>
        log && log.uri && log.uri.includes(apparaatId) && log.uri.includes(capabilityNaam)
    );

    if (doelLog) {
        // Stap 3: Haal alle datapunten op basis van de resolutie
        inzichtenData = await Homey.insights.getLogEntries({
            id: doelLog.id,
            uri: doelLog.uri,
            resolution: inzichtenResolutie
        });

        if (inzichtenData && inzichtenData.values && inzichtenData.values.length > 0) {
            // Onthoudt het vorige uurnummer, zodat een label alleen bij een uurwisseling komt
            let vorigUur = null;

            // Stap 4: Loop door alle metingen heen
            for (const punt of inzichtenData.values) {
                const datum = new Date(punt.t);

                // Formatteer naar Nederlandse tijd om het juiste uurnummer te krijgen
                const nlTijdString = new Intl.DateTimeFormat('nl-NL', {
                    timeZone: 'Europe/Amsterdam',
                    hour: 'numeric',
                    hour12: false
                }).format(datum);

                const huidigUurNummer = Number(nlTijdString);

                // Alleen bij een nieuw uur krijgt het punt een x-aslabel
                let tijdVeld = null;

                if (huidigUurNummer !== vorigUur) {
                    tijdVeld = String(huidigUurNummer);
                    vorigUur = huidigUurNummer;
                }

                // Rond de waarde af op 1 decimaal
                const afgerondeWaarde = Number(punt.v.toFixed(1));

                // Voeg toe aan de hulparray
                meetResultatenLijst.push({
                    l: tijdVeld,
                    v: afgerondeWaarde
                });
            }
        } else {
            return genereerSvgFoutmelding('Geen datapunten gevonden in de opgegeven periode.');
        }
    } else {
        return genereerSvgFoutmelding('Het gevraagde Inzicht logboek kon niet worden gevonden.');
    }
} catch (fout) {
    return genereerSvgFoutmelding('Fout bij ophalen van inzichten: ' + fout.message);
} finally {
    // Geheugen vrijmaken voor de Garbage Collector
    logboeken = null;
    doelLog = null;
    inzichtenData = null;
}

// Zonder meetpunten kan er geen grafiek getekend worden
if (meetResultatenLijst.length === 0) {
    return genereerSvgFoutmelding('Geen meetpunten beschikbaar voor de grafiek.');
}

// ==========================================
// 3B. AFVLAKKEN VAN DE METINGEN
// ==========================================
// Elk meetpunt wordt vervangen door het gemiddelde van zichzelf en zijn buren.
// Het gemiddelde wordt snel berekend met een cumulatieve som (geen dubbele lus).
// De afvlakking gebeurt VOOR de y-as berekening, zodat de schaal meebeweegt.
if (afvlakkingVenster > 1 && meetResultatenLijst.length > 2) {
    let aantalMeetpunten = meetResultatenLijst.length;

    // Aantal punten links en rechts van het huidige punt dat meedoet in het gemiddelde
    let halfVenster = Math.floor(afvlakkingVenster / 2);

    // Cumulatieve som: cumulatieveSom[n] = som van de eerste n waarden
    let cumulatieveSom = new Array(aantalMeetpunten + 1);
    cumulatieveSom[0] = 0;
    for (let meetpuntIndex = 0; meetpuntIndex < aantalMeetpunten; meetpuntIndex++) {
        cumulatieveSom[meetpuntIndex + 1] = cumulatieveSom[meetpuntIndex] + meetResultatenLijst[meetpuntIndex].v;
    }

    // Per punt het gemiddelde over het venster berekenen.
    // Aan het begin en einde van de reeks wordt het venster automatisch smaller.
    let afgevlakteWaarden = new Array(aantalMeetpunten);
    for (let meetpuntIndex = 0; meetpuntIndex < aantalMeetpunten; meetpuntIndex++) {
        let beginIndex = Math.max(0, meetpuntIndex - halfVenster);
        let eindIndex = Math.min(aantalMeetpunten - 1, meetpuntIndex + halfVenster);
        let aantalInVenster = eindIndex - beginIndex + 1;
        let somInVenster = cumulatieveSom[eindIndex + 1] - cumulatieveSom[beginIndex];
        afgevlakteWaarden[meetpuntIndex] = somInVenster / aantalInVenster;
    }

    // Afgevlakte waarden terugschrijven (de x-aslabels 'l' blijven ongewijzigd)
    for (let meetpuntIndex = 0; meetpuntIndex < aantalMeetpunten; meetpuntIndex++) {
        meetResultatenLijst[meetpuntIndex].v = afgevlakteWaarden[meetpuntIndex];
    }

    // Geheugen vrijmaken voor de Garbage Collector
    cumulatieveSom = null;
    afgevlakteWaarden = null;
}

// ==========================================
// 4. BEREKENINGEN & GELIJKE Y-INTERVALLEN
// ==========================================

// Beschikbare ruimte voor de grafiek zelf (canvas min de marges)
let tekenBreedte = canvasBreedte - margeLinks - margeRechts;
let tekenHoogte = canvasHoogte - margeBoven - margeOnder;

// Alle Y-waarden uit de dataset halen (nu dus de afgevlakte waarden)
let yWaarden = meetResultatenLijst.map(function(meetpunt) {
    return meetpunt.v;
});

let yMinAbsoluut = Math.min.apply(null, yWaarden);
let yMaxAbsoluut = Math.max.apply(null, yWaarden);

// Totale spreiding van de data
let bereikY = yMaxAbsoluut - yMinAbsoluut;

// Bepaal de minimale y-as waarde: 10% van het bereik (of van de waarde zelf als bereik 0 is)
// lager dan de laagste datawaarde, maar nooit < 0 (tenzij data zelf negatief is)
let toegestaneOnderkant = yMinAbsoluut >= 0 ? 0 : yMinAbsoluut - (Math.abs(yMinAbsoluut) * 0.1);
let yMinRauw = yMinAbsoluut - (bereikY > 0 ? bereikY * 0.1 : Math.max(Math.abs(yMinAbsoluut) * 0.1, 1));

if (yMinRauw < toegestaneOnderkant && yMinAbsoluut >= 0) {
    yMinRauw = 0;
}

// Marge boven de hoogste datawaarde
let yMargeStap = bereikY * margeFractieData;
let yMaxRauw = yMaxAbsoluut + yMargeStap;

// Vangnet voor een vlakke lijn (alle waarden gelijk)
if (yMaxRauw - yMinRauw <= 0) {
    yMinRauw = yMinAbsoluut - 0.5;
    if (yMinAbsoluut >= 0 && yMinRauw < 0) yMinRauw = 0;
    yMaxRauw = yMaxAbsoluut + 0.5;
}

let yTotaalBereikRauw = yMaxRauw - yMinRauw;

// Kandidaat-stapgroottes: 1, 2 en 5 keer een macht van tien ("mooie" getallen)
let mooieVermenigvuldigers = [1, 2, 5];
let startExponent = Math.floor(Math.log10(yTotaalBereikRauw / maximaalAantalYStappen)) - 1;

// Beste combinatie tot nu toe (begint met een simpele schatting)
let gekozenStap = yTotaalBereikRauw / streefAantalYStappen;
let aantalYStappen = streefAantalYStappen;
let yMin = yMinRauw;
let besteScore = Infinity;

// Probeer alle kandidaten en kies de combinatie met de laagste score
for (let exponentTeller = 0; exponentTeller < 8; exponentTeller++) {
    let macht = Math.pow(10, startExponent + exponentTeller);

    for (let vermenigvuldigerIndex = 0; vermenigvuldigerIndex < mooieVermenigvuldigers.length; vermenigvuldigerIndex++) {
        let kandidaatStap = mooieVermenigvuldigers[vermenigvuldigerIndex] * macht;
        let kandidaatMin = Math.floor((yMinRauw / kandidaatStap) + 1e-9) * kandidaatStap;

        // Zorg dat kandidaatMin nooit onder 0 komt als de dataset niet negatief is
        if (yMinAbsoluut >= 0 && kandidaatMin < 0) {
            kandidaatMin = 0;
        }

        let kandidaatAantalStappen = Math.ceil(((yMaxRauw - kandidaatMin) / kandidaatStap) - 1e-9);

        // Te veel stappen: kandidaat overslaan
        if (kandidaatAantalStappen > maximaalAantalYStappen) {
            continue;
        }

        // Te weinig stappen: opvullen tot het minimum
        if (kandidaatAantalStappen < minimaalAantalYStappen) {
            kandidaatAantalStappen = minimaalAantalYStappen;
        }

        // Score = overschot aan ongebruikte ruimte + straf voor afwijking van het streefaantal
        let kandidaatTotaalBereik = kandidaatAantalStappen * kandidaatStap;
        let kandidaatOverschot = (kandidaatTotaalBereik - yTotaalBereikRauw) / yTotaalBereikRauw;
        let kandidaatStrafStappen = Math.abs(kandidaatAantalStappen - streefAantalYStappen) * strafPerAfwijkendeStap;
        let kandidaatScore = kandidaatOverschot + kandidaatStrafStappen;

        if (kandidaatScore < besteScore - 1e-9) {
            besteScore = kandidaatScore;
            gekozenStap = kandidaatStap;
            aantalYStappen = kandidaatAantalStappen;
            yMin = kandidaatMin;
        }
    }
}

// Bovenkant van de y-as volgt uit de onderkant plus alle stappen
let yMax = yMin + (gekozenStap * aantalYStappen);

// Afrondingsfouten van floating point getallen wegwerken
yMin = Number(yMin.toFixed(10));
yMax = Number(yMax.toFixed(10));

// Aantal decimalen voor de y-aslabels, afgeleid van de stapgrootte
let yDecimalen = Math.max(0, -Math.floor(Math.log10(gekozenStap) + 1e-9));
let yTotaalBereik = yMax - yMin;

// ==========================================
// 5. SVG OPBOUWEN VIA ARRAYS
// ==========================================

// Alle SVG-regels worden eerst in een array verzameld (push) en daarna met join samengevoegd.
// Dat is geheugenefficienter dan steeds een lange tekst aan elkaar plakken.
let svgOnderdelen = [];

svgOnderdelen.push('<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 ' + canvasBreedte + ' ' + canvasHoogte + '" width="100%" height="100%" style="background: transparent;">');
svgOnderdelen.push(' <defs>');
svgOnderdelen.push(' <style>');
svgOnderdelen.push(' @import url(\'https://fonts.googleapis.com/css2?family=Exo+2:wght@200;400&amp;display=swap\');');
svgOnderdelen.push(' text { font-family: \'Exo 2\', sans-serif; }');
svgOnderdelen.push(' </style>');
svgOnderdelen.push(' </defs>');

// Hoofdtitel bovenaan, gecentreerd
if (grafiekTitel && grafiekTitel.length > 0) {
    svgOnderdelen.push(' <text x="' + (canvasBreedte / 2) + '" y="24" fill="' + kleurAssen + '" font-size="' + fontGrootteTitel + 'pt" font-weight="400" text-anchor="middle">' + grafiekTitel + '</text>');
}

// Horizontale gridlijnen, streepjes en Y-as labels
for (let gridIndex = 0; gridIndex <= aantalYStappen; gridIndex++) {
    let verhouding = gridIndex / aantalYStappen;
    let yPositie = margeBoven + (tekenHoogte * (1 - verhouding));
    let yWaardeLabel = (yMin + (gridIndex * gekozenStap)).toFixed(yDecimalen);

    // Gridlijn over de volle breedte van de grafiek
    svgOnderdelen.push(' <line x1="' + margeLinks + '" y1="' + yPositie + '" x2="' + (canvasBreedte - margeRechts) + '" y2="' + yPositie + '" stroke="' + kleurGridLijnen + '" stroke-width="0.5" />');

    // Klein streepje links van de y-as
    svgOnderdelen.push(' <line x1="' + (margeLinks - 5) + '" y1="' + yPositie + '" x2="' + margeLinks + '" y2="' + yPositie + '" stroke="' + kleurAssen + '" stroke-width="1" />');

    // Waardelabel naast het streepje
    svgOnderdelen.push(' <text x="' + (margeLinks - 10) + '" y="' + (yPositie + 4) + '" fill="' + kleurAssen + '" font-size="' + fontGrootteLabels + 'pt" text-anchor="end">' + yWaardeLabel + '</text>');
}

// Datapunten en X-as elementen berekenen
let aantalPunten = meetResultatenLijst.length;

// Horizontale afstand tussen twee opeenvolgende punten
let xStap = tekenBreedte / (aantalPunten > 1 ? aantalPunten - 1 : 1);

// Punten voor de lijn en voor de gevulde oppervlakte eronder
let grafiekPunten = [];
let oppervlaktePunten = [];

// Oppervlakte begint linksonder op de x-as
oppervlaktePunten.push(margeLinks + ',' + (margeBoven + tekenHoogte));

for (let puntIndex = 0; puntIndex < aantalPunten; puntIndex++) {
    // x-positie volgt uit de volgorde, y-positie uit de (afgevlakte) waarde
    let xPositie = margeLinks + (puntIndex * xStap);
    let yGenormaliseerd = yTotaalBereik !== 0 ? (meetResultatenLijst[puntIndex].v - yMin) / yTotaalBereik : 0.5;
    let yPositiePunt = margeBoven + (tekenHoogte * (1 - yGenormaliseerd));

    // Punt toevoegen aan zowel de lijn als de oppervlakte
    let puntString = xPositie.toFixed(2) + ',' + yPositiePunt.toFixed(2);
    grafiekPunten.push(puntString);
    oppervlaktePunten.push(puntString);

    // X-aslabel (uurnummer) ophalen, indien aanwezig voor dit punt
    let xAsLabel = meetResultatenLijst[puntIndex].l ? String(meetResultatenLijst[puntIndex].l).trim() : '';

    // Meest linker label op de x-as overslaan (puntIndex === 0)
    if (xAsLabel.length > 0 && puntIndex > 0) {
        let xLabelPositie = xPositie.toFixed(2);

        // Klein streepje onder de x-as
        svgOnderdelen.push(' <line x1="' + xLabelPositie + '" y1="' + (margeBoven + tekenHoogte) + '" x2="' + xLabelPositie + '" y2="' + (margeBoven + tekenHoogte + 5) + '" stroke="' + kleurAssen + '" stroke-width="1" />');

        // Uurlabel onder het streepje
        svgOnderdelen.push(' <text x="' + xLabelPositie + '" y="' + (margeBoven + tekenHoogte + 25) + '" fill="' + kleurAssen + '" font-size="' + fontGrootteLabels + 'pt" text-anchor="middle">' + xAsLabel + '</text>');
    }
}

// Oppervlakte sluit rechtsonder op de x-as
oppervlaktePunten.push((margeLinks + tekenBreedte) + ',' + (margeBoven + tekenHoogte));

// Vulling en grafieklijn tekenen
svgOnderdelen.push(' <polygon points="' + oppervlaktePunten.join(' ') + '" fill="' + kleurVulling + '" fill-opacity="' + transparantieVulling + '" />');
svgOnderdelen.push(' <polyline points="' + grafiekPunten.join(' ') + '" fill="none" stroke="' + kleurLijn + '" stroke-width="2.5" stroke-linejoin="round" stroke-linecap="round" />');

// Hoofdassen tekenen (y-as links, x-as onder)
svgOnderdelen.push(' <line x1="' + margeLinks + '" y1="' + margeBoven + '" x2="' + margeLinks + '" y2="' + (margeBoven + tekenHoogte) + '" stroke="' + kleurAssen + '" stroke-width="1" />');
svgOnderdelen.push(' <line x1="' + margeLinks + '" y1="' + (margeBoven + tekenHoogte) + '" x2="' + (canvasBreedte - margeRechts) + '" y2="' + (margeBoven + tekenHoogte) + '" stroke="' + kleurAssen + '" stroke-width="1" />');

// Titel van de x-as, onderaan gecentreerd
if (xAsTitel && xAsTitel.length > 0) {
    let xTitelPositie = margeLinks + (tekenBreedte / 2);
    let yTitelPositie = canvasHoogte - 8;
    svgOnderdelen.push(' <text x="' + xTitelPositie + '" y="' + yTitelPositie + '" fill="' + kleurAssen + '" font-size="' + fontGrootteTitelsAssen + 'pt" font-weight="400" text-anchor="middle">' + xAsTitel + '</text>');
}

// Titel van de y-as, links en 90 graden gedraaid
if (yAsTitel && yAsTitel.length > 0) {
    let xYTitelPositie = 18;
    let yYTitelPositie = margeBoven + (tekenHoogte / 2);
    svgOnderdelen.push(' <text x="' + xYTitelPositie + '" y="' + yYTitelPositie + '" fill="' + kleurAssen + '" font-size="' + fontGrootteTitelsAssen + 'pt" font-weight="400" text-anchor="middle" transform="rotate(-90 ' + xYTitelPositie + ' ' + yYTitelPositie + ')">' + yAsTitel + '</text>');
}

svgOnderdelen.push('</svg>');

// Alle regels samenvoegen tot een enkele SVG-tekst
let svgResultaat = svgOnderdelen.join('\n');

// ==========================================
// 6. EINDRESULTAAT & GEHEUGEN OPTIMALISATIE
// ==========================================

// Resultaat als object met titel en SVG, zoals de flow verwacht
let eindResultaat = {
    titel: grafiekTitel,
    svg: svgResultaat
};

let jsonString = JSON.stringify(eindResultaat);

// Expliciet geheugen vrijmaken voor de Garbage Collector
dataInput = null;
meetResultatenLijst = null;
yWaarden = null;
svgOnderdelen = null;
svgResultaat = null;
grafiekPunten = null;
oppervlaktePunten = null;
mooieVermenigvuldigers = null;
eindResultaat = null;

return jsonString;

// ==========================================
// HULPFUNCTIE VOOR SVG FOUTMELDING
// ==========================================
// Bouwt een SVG met een rode titel en de foutmelding, zodat de fout op het dashboard zichtbaar is.
function genereerSvgFoutmelding(foutmelding) {
    console.error(foutmelding);

    let foutSvgOnderdelen = [];
    foutSvgOnderdelen.push('<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 900 340" width="100%" height="100%" style="background: transparent;">');
    foutSvgOnderdelen.push(' <defs>');
    foutSvgOnderdelen.push(' <style>');
    foutSvgOnderdelen.push(' @import url(\'https://fonts.googleapis.com/css2?family=Exo+2:wght@400;600&amp;display=swap\');');
    foutSvgOnderdelen.push(' text { font-family: \'Exo 2\', sans-serif; }');
    foutSvgOnderdelen.push(' </style>');
    foutSvgOnderdelen.push(' </defs>');
    foutSvgOnderdelen.push(' <rect width="900" height="340" fill="#1E1E1E" rx="10" />');
    foutSvgOnderdelen.push(' <text x="450" y="140" fill="#FF5252" font-size="22pt" font-weight="400" text-anchor="middle">Configuratiefout</text>');
    foutSvgOnderdelen.push(' <text x="450" y="190" fill="#FFFFFF" font-size="16pt" font-weight="400" text-anchor="middle">' + foutmelding + '</text>');
    foutSvgOnderdelen.push('</svg>');

    let foutResultaat = {
        titel: 'Foutmelding',
        svg: foutSvgOnderdelen.join('\n')
    };

    // Verzamelarray vrijgeven voor de Garbage Collector
    foutSvgOnderdelen = null;

    return JSON.stringify(foutResultaat);
}

```

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 24, 2026, 12:42pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1564 "2026-10-24T12:42:10Z")

</div>

# NEW [Dasiboard Studio TEST Version V2.2.0](https://homey.app/a/com.satoer.dashboardstudio/test/)

2026-10-24

- New: Fetch RSS Feed to Markdown - Added a flow card to fetch and format single or multiple RSS feeds into clean Markdown for dashboards, and renamed the Calendar settings tab to Flow Cards.
- New: Standardized Homey Topics - Moods, flows, and variables now use clear homey/moods/, homey/flows/, and homey/variables/ topic prefixes with full backward compatibility for existing dashboards.
- New: Flow Card: Dashboard Opened Page - Added a trigger card that fires when a dashboard opens or navigates to a page.
- New: Flow Card: Dashboard Is Open - Added a condition card to check if a dashboard is currently open.
- New: Flow Card: Dashboard Is Open on Page - Added a condition card to check if a dashboard is open on a specific page.  
\*New: Capability & Topic Cleanup - Added an audit tool in the app settings Configuration tab that scans all saved dashboards to find enabled Homey device capabilities and MQTT topics no longer referenced in any widget, formula, or template, letting you review them in an interactive checklist and disable them with one click to reduce memory and network traffic.
- Improved: State Caching - Added cache mode options in Settings to optimize memory usage and stability on Homey.
- Fixed: All-day calendar events stay on the correct day when daylight saving time changes.

## Fetch RSS Feed to Markdown flow card

 ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/1/511c2516e8bab61446b9fd7d5f56ad9f39c979c9.jpeg)  
Fetch live news headlines and blog articles directly into Dashboard Studio without any homeyscripts. The **[Fetch RSS Feed to Markdown](https://satoer.com/dashboardstudio/?docs=Homey+Flow+Cards&widget=rss-feeds)** flow card downloads one or more RSS or Atom feeds, automatically sorts articles chronologically, and renders a clean Markdown table ready for your Text widgets.  
Also the flowcards to send insight data and calendar markdown, have now the option to set a custom topic name to send it directly.

## Other new flow cards

- Dashboard Opened Page - Added a trigger card that fires when a dashboard opens or navigates to a page.
- Dashboard Is Open AND card - Added a condition card to check if a dashboard is currently open.
- Dashboard Is Open on Page AND card - Added a condition card to check if a dashboard is open on a specific page.

## Memory Improvements

To the user who anonymously sent in the error reports and the other users that are sending huge amounts of data through topics, such as entire interactive SVG files or massive markdown tables: Homey allocates a strictly limited amount of memory to each app, and exceeding that limit causes the app to crash. One issue is that, by default, all this data is cached. Every topic value is kept in memory so that whenever you open or reload a dashboard, that data is sent automatically and every widget immediately displays the latest info. If caching is disabled, the widget simply waits until the sensor broadcasts new data. The problem arises when these very large topics also get cached.

In this new version, caching is handled more memory friendly, and I added an option in the Dashboard Studio Homey settings to actively prevent caching large topic values:

 ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/0/80e196826cac302b9a04df6330ebe1e3afa13728.png)  
My advice: if you are experiencing crashes, set this to “Optimized.” It will stop caching large topics, though the trade-off is that those widgets won’t automatically populate on reload. If everything runs smoothly, feel free to leave it on “Full.”

## Capability & Topic Cleanup:

 ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/7/47bf7459a190584e9bb6d95f1d222f6af4c27014.png)  
Added an audit tool in the app settings Configuration tab (all the way at the bottom) that scans every saved dashboard stored on your Homey to find enabled device capabilities and topics no longer referenced in any widget, formula, or template. You can review them in an interactive checklist and disable them with a single click to save memory and cut down on network traffic (though keep in mind this only scans device, flow, mood, and variable capabilities, which generally do not take up massive amounts of memory anyway).

## Fixed: All-day calendar events stay on the correct day when daylight saving time changes.

> [@nmeden](#):
>
> The all-day midnight seems to be calculated with the current offset (UTC+2) instead of the offset on the event’s own date. After the switch to UTC+1 on 25 Oct, `22:00Z` is 23:00 on the previous day, so the event lands one day early. I haven’t looked at the code, so this is only a guess from the data.

This has been fixed, though you will probably have to wait a 1/2 or full year to actually test it out 🤣

---

<div class="post-metadata">

**Author:** ![nmeden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nmeden/32/9579_2.png) [@nmeden](https://community.homey.app/u/nmeden)\
**Post date:** [October 24, 2026, 1:20pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1565 "2026-10-24T13:20:32Z")

</div>

> [@Satoer](#):
>
> > [@nmeden](#):
> >
> > The all-day midnight seems to be calculated with the current offset (UTC+2) instead of the offset on the event’s own date. After the switch to UTC+1 on 25 Oct, `22:00Z` is 23:00 on the previous day, so the event lands one day early. I haven’t looked at the code, so this is only a guess from the data.
> 
> This has been fixed, though you will probably have to wait a 1/2 or full year to actually test it out 🤣

Nope, still DST a couple of hours more.

Fix is confirmed! 👍

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [October 24, 2026, 4:12pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1566 "2026-10-24T16:12:03Z")

</div>

Nice new functions! First impressions:

- unused fields: 130. Most of them where from removed/reinstalled apps or using different apps.
- suggestion for RSS Markdown card: Allow the user to create a list of words; if any of these words appear in a title, exclude that post from the Markdown output. I personally use this to filter out the many football-related posts that appear over each weekend.
- Limiting internal memory usage sounds like a good solution. Since I’m curious about the outcome, I’ll keep an eye on memory (which one best?) usage over the next few weeks while using the ‘Optimized’ setting.
- Could you tell us a bit more about “Standardized Homey Topics”?

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 24, 2026, 4:24pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1567 "2026-10-24T16:24:28Z")

</div>

> [@Amersfoort](#):
>
> - suggestion for RSS Markdown card: Allow the user to create a list of words; if any of these words appear in a title, exclude that post from the Markdown output.

Good idea.

> [@Amersfoort](#):
>
> Could you tell us a bit more about “Standardized Homey Topics”?

The new ability to directly control variables, flows, and moods (which you can turn on by enabling their capabilities) originally just use only the name of the variable, flow, or mood. But with the auto widget creation option, I need to be able to guess what kind of device I am controlling based on the topic path (and value). So, just like with insight graphs, the topic now has homey/variables/variable\_name in front of it. It is still backwards compatible though, so if you use just variable\_name, it works just like it used to.

---

<div class="post-metadata">

**Author:** ![Marcel\_R](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_r/32/47933_2.png) [@Marcel\_R](https://community.homey.app/u/Marcel_R)\
**Post date:** [October 24, 2026, 7:33pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1568 "2026-10-24T19:33:44Z")

</div>

Hi,

First of all: thanks for this amazing app!

After a quite steep learning curve (which is absolutely worth it!), I could solve all issues/challenges till now, but one issue in Dashboard Studio 2.2.0 actually remains:

Using the graph widget for displaying my actual power consumption works fine. But when I want a graph showing the actual solar panel power, it only works as long as the values send subsequently are not identical. As I send new values every 10 seconds (Homey flow) and use overlays for power consumption and solar panel power, it’s quite annoying when the both graphs are not ‘in sync’ (a datapoint added every 10 seconds, like in evenings, when solar power is 0).  
So, how to get the graph widget appending a new datapoint when consecutive incoming values are identical?  
The Data Stream Explorer confirms an incoming value every 10 seconds (triggered by the flow), but nevertheless the solar power graph remains unchanged (when subsequent values are identical, like 0).  
Something I miss or something missing/wrong in app?

---

<div class="post-metadata">

**Author:** ![Rune\_DK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rune_dk/32/79404_2.png) [@Rune\_DK](https://community.homey.app/u/Rune_DK)\
**Post date:** [October 24, 2026, 7:56pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1569 "2026-10-24T19:56:13Z")

</div>

First of, love it! spend a hole day getting my dashboard up and running 🙂

Only thing i cant solve is a way to return to page 1 after xx minuts of inactivitet.

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 24, 2026, 9:11pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1570 "2026-10-24T21:11:46Z")

</div>

> [@Marcel\_R](#):
>
> Using the graph widget for displaying my actual power consumption works fine. But when I want a graph showing the actual solar panel power, it only works as long as the values send subsequently are not identical. As I send new values every 10 seconds (Homey flow) and use overlays for power consumption and solar panel power, it’s quite annoying when the both graphs are not ‘in sync’ (a datapoint added every 10 seconds, like in evenings, when solar power is 0).  
> So, how to get the graph widget appending a new datapoint when consecutive incoming values are identical?

Ah yes, I get the problem. It only adds a new value when the value actually changes. I will fix this in a future release so it appends a datapoint whenever it receives an update from the topic.

One question though, why are you approaching it like this? Homey already tracks all of your historical data natively. There is a Dashboard Studio Insight graph feature that allows you to send complete graphs directly to the widget.

 ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/3320b20da79429a213ee59e03cf6462a4c9e850d.png)

[See the documentation over here](https://satoer.com/dashboardstudio/?docs=Homey+Flow+Cards&widget=insights).

> [@Rune\_DK](#):
>
> Only thing i cant solve is a way to return to page 1 after xx minuts of inactivitet.

That is interesting! Another user asked for that exact feature just a couple of weeks ago. Lucky for you, I already built it in back then. The setting is called Landing Page, and you can configure it right in the Dashboard Environment:

 ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/3/03e1dee2def793cee49cf34547863f3999bf6e3b.png)  
(I’ll make it clearer that this controls page interactivity)

---

<div class="post-metadata">

**Author:** ![Marcel\_R](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_r/32/47933_2.png) [@Marcel\_R](https://community.homey.app/u/Marcel_R)\
**Post date:** [October 25, 2026, 8:33am UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1571 "2026-10-25T08:33:32Z")

</div>

> One question though, why are you approaching it like this? Homey already tracks all of your historical data natively.

For 2 reasons:

1. Because my focus is the actual consumption/production and of the last minute. As far as I know the Insight data are not recorded every 10 seconds
2. The Insight data do not always show the measured values. There is interpolation used by Athom. I reported a few weeks ago and they confirmed it’s how Insights work (unfortunately).  
For example: the daily power consumption should be 0 at 00.01 hrs. But, in fact it isn’t. If the consumption is 10 kWh the day before, the Insight value measured at, for example 00:05 hrs. is ‘somewhere between 10 and 0 kWh’ (near 10 kWh).

Maybe I misinterpreted your solution or the ‘Send Insight’ card works differently, but the only time I used interpolated data was shown in the graph, not the measured (‘real’) data. Please correct me if I’m wrong and have to use in a different way.

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 25, 2026, 11:18am UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1572 "2026-10-25T11:18:24Z")

</div>

I think the insight data is recorded whenever the data changes, and it gets pruned as it gets older (so it gets more compressed, with fewer data points per time interval). That is just an assumption, though. Anyway, in my experience, the data is added in real time.

Still, you do need to send the graph data at intervals, and I would not recommend an interval of 10 seconds. I personally do this every 10 minutes on a 24 hour graph, but every minute should be fine too. Another advantage is that the data updates immediately on a page reload, so it does not have to rebuild the entire graph from scratch.

---

<div class="post-metadata">

**Author:** ![Marcel\_R](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_r/32/47933_2.png) [@Marcel\_R](https://community.homey.app/u/Marcel_R)\
**Post date:** [October 25, 2026, 12:58pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1573 "2026-10-25T12:58:07Z")

</div>

> Still, you do need to send the graph data at intervals, and I would not recommend an interval of 10 seconds. I personally do this every 10 minutes on a 24 hour graph

This is perfect for historical data and I use this way as well. But, when I want to see how the actual consumption (from grid) and the solar panels power and the difference of these two for the last minute (updated every 10 seconds by adding the actual value) in one visualisation (= 3 graphs in layers), updating even every minute is not informative.  
Of course, instead, I can use a gauge widget to show the actual values, but that’s the actual value only, not the last minute(s) data.  
I realise it’s all nice to have and I just wondered if it’s missing functionality or a setting I missed. That’s clear now and I could consider to use a ‘quite dirty’ workaround: adding 0.01 to the measured value in the flow and distract 0.01 for the next measured value (and so on), so every value will be different and will be recognised as new value added as datapoint to the graph.

---

<div class="post-metadata">

**Author:** ![Bert\_Onraedt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert_onraedt/32/79096_2.png) [@Bert\_Onraedt](https://community.homey.app/u/Bert_Onraedt)\
**Post date:** [October 25, 2026, 4:26pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1574 "2026-10-25T16:26:34Z")

</div>

> [@nmeden](#):
>
> All full day events are also displayed on the day before it start

I don’t have this problem.  
I remember it has been an issue when Satoer was developping the Calendar-integration, but since then it runs pretty flawless.

edit: I see it has already been fixed, so maybe i just didn’t notice…

---

<div class="post-metadata">

**Author:** ![nmeden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nmeden/32/9579_2.png) [@nmeden](https://community.homey.app/u/nmeden)\
**Post date:** [October 25, 2026, 6:30pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1575 "2026-10-25T18:30:36Z")

</div>

I might have found an additional bug.

**Bug Report: Topic Binding to Page(s) under Widget does move element**

**Description:** When binding a topic to **Page(s)** under a Widget, I expect the widget to evaluate the expression in the **Binding Options** and move to the target page accordingly. However, it does not move when the topic triggers.

**Context / Additional Observations:**

- Moving a group using **Override Page(s)** works as expected, though notably **Binding Options** are not available on that control.

I was able to work around the issue locally by putting two containers inside a group and splitting the logic across two separate topics (one for moving the group, one for setting opacity).

---

<div class="post-metadata">

**Author:** ![Satoer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/satoer/32/38113_2.png) [@Satoer](https://community.homey.app/u/Satoer)\
**Post date:** [October 25, 2026, 7:55pm UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1576 "2026-10-25T19:55:34Z")

</div>

> [@Bert\_Onraedt](#):
>
> edit: I see it has already been fixed, so maybe i just didn’t notice…

The bug was particularly when changing from summertime to wintertime 😉

> [@nmeden](#):
>
> Bug Report: Topic Binding to Page(s) under Widget does move element

Ah, that’s indeed a bug. Thanks. shall fix this next version 👍

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [October 29, 2026, 7:16am UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1577 "2026-10-29T07:16:39Z")

</div>

> [@Satoer](#):
>
> - New: Flow Card: Dashboard Opened Page - Added a trigger card that fires when a dashboard opens or navigates to a page.

Would it be possible to let de Dashboard variable empty in this card?

When making major changes to the layout or implementing significant app updates, I first copy the dashboard under a different name (including a version number). Since the dashboard is mandatory and cannot be a variable, I have to manually update dozens of flows each time.

At least one value has to be filled in: dashboard or page.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/9/c95df6070976b4e9db4a21f421787fbb2418a19a.png)

---

<div class="post-metadata">

**Author:** ![Bjarte\_Heigre](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bjarte_heigre/32/69411_2.png) [@Bjarte\_Heigre](https://community.homey.app/u/Bjarte_Heigre)\
**Post date:** [October 29, 2026, 8:37am UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1578 "2026-10-29T08:37:52Z")

</div>

**Bug – Load & Filter iCal: events from [Outlook.com](http://Outlook.com) published calendars are dropped (non-standard TZID)**

Hi @Satoer, thanks for a great app! I found an issue with the iCal parser.

**What happens**  
When I load a published [Outlook.com](http://Outlook.com) calendar (ICS link from Outlook on the web), the Load & Filter iCal card runs without errors, but **no events** come through. “Convert iCal JSON to Markdown” renders the week view with day headers only, while the same file contains several events in that period.

**Likely cause**  
[Outlook.com](http://Outlook.com) exports the file as Exchange 2010 and uses non-standard time zone IDs, for example:

- `DTSTART;TZID=Customized Time Zone:20261030T111500`
- `TZID=W. Central Africa Standard Time`
- `TZID="tzone://Microsoft/Utc"`

Matching `VTIMEZONE` blocks for these IDs are included in the file, so the parser could resolve the offsets from VTIMEZONE instead of an IANA lookup. It looks like events with an unknown TZID are discarded.

**Steps to reproduce**

1. Publish an [Outlook.com](http://Outlook.com) calendar and copy the ICS link.
2. Advanced Flow: Load & Filter iCal (Today + 7 days) → Convert iCal JSON to Markdown (“Today + 7 days”) → topic.
3. Run it: the output has no events, even though the ICS contains events in the period.

**Cross-check**

- A Google Calendar ICS works fine in the same flow.
- If I subscribe to the same Outlook calendar in Google Calendar and use Google’s iCal address instead, the events show up with correct times. So the data itself is fine.
- Changing the time zone in Outlook settings does not help; new events still get `Customized Time Zone`.

**Environment**  
Homey Pro (2023), Dashboard Studio v2.2.0.

Workaround for others: subscribe to the Outlook calendar in a Google account and use Google’s secret iCal address.

Happy to test a fix!

---

<div class="post-metadata">

**Author:** ![Ton\_B](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ton_b/32/10723_2.png) [@Ton\_B](https://community.homey.app/u/Ton_B)\
**Post date:** [October 29, 2026, 11:48am UTC](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169/1579 "2026-10-29T11:48:32Z")

</div>

Hi, how can I use the value in minutes that I receive from my EV to calculate the charging end time?

[Previous page](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169.md?page=77)

[Next page](https://community.homey.app/t/app-pro-dashboard-studio-a-completely-free-form-dashboard-designer/151169.md?page=79)
