I tried an incognito browser, same result. I have no idea.
But I am experiencing more issues since a few days. My first dashboard refuses to update most of the time. I can see the variables in Homey being correct, but in the dashboard nothing is changed. When I push the variable again it sometimes takes several tries before the dashboard updates it.. At least on my side things are not going well these last days.
I assume you have already performed a Homey device reboot, which can help quite a bit with vague automation issues.
How is the memory usage on Homey (storage and internal memory); is there still plenty of free space?
Yeah. Restarted a few times yesterday. Storage and memory are both around 50%, so no issues there.
Between 1.4.2 and 1.6.0, the logic that turns Logic variable updates on Homey into updates for the dashboard did not change. Those updates still go out over the same live connection to the app (a WebSocket-style link using Socket.IO), so there is nothing new in that path between those versions that would explain the dashboard falling behind what you see in Homey. 
Yea, I understand. Could it be connected to a second dashboard? Signals crossing (both are busy dashboards with data).
Donât think it should make a noticeable difference. Every connected dashboard gets the same live updates from the app, each screen only shows the ones its widgets are bound to.
One more thing I can think of is that Wifi and Ethernet are enabled. So, maybe Homey communicates on WiFi sometimes, which doesnât reach the dashboard since itâs on the ethernet IP. But I guess Iâm not the only one with WiFi and ethernet?
Perhaps your IP changed? Think it is anyway a good practice with Homey to give your Homey a static IP in your router
IP is static, but WiFi and ethernet never have the same IP. and both er enabled within Homey.
I donât think Homey jumps between networks like a telephone does. (I would also disable the wifi, why would you ever want to use that if you have ethernet connected)
Lets do a test. Reset the canvas and put just a graph on it:
Then go inside Homey create a flow with a Homeyscript (run [code] and return text-tag).
Put this in the script:
// ==========================================
// CONFIGURATION PARAMETERS
// ==========================================
// Timing & Resolution
const NUM_POINTS = 20000; // Resolution: Number of data points in the array
const DURATION_HOURS = 24; // Total time span of the graph
const START_TIME = new Date("2026-03-31T00:00:00.000Z");
// Nudge Settings (Animation speed)
// How fast the wave shifts sideways per second in real-time
const SHIFT_SPEED_MULTIPLIER = 1000;
const currentTimeOffset = Date.now() * SHIFT_SPEED_MULTIPLIER;
// Base value to ensure the graph stays primarily above 0
const BASE_OFFSET = 800;
// Wave 1: Sine Wave (Smooth, rolling hills)
const SINE_AMP = 400; // Height of the wave
const SINE_FREQ = 2; // Number of complete cycles per 24 hours
// Wave 2: Block/Square Wave (Sharp steps up and down)
const BLOCK_AMP = 200;
const BLOCK_FREQ = 4;
// Wave 3: Sawtooth Wave (Ramps up, drops sharply)
const SAW_AMP = 300;
const SAW_FREQ = 1.5;
// ==========================================
// WAVEFORM GENERATOR FUNCTIONS
// ==========================================
function getSine(t, freq, amp) {
return amp * Math.sin(2 * Math.PI * freq * t);
}
function getBlock(t, freq, amp) {
return amp * Math.sign(Math.sin(2 * Math.PI * freq * t));
}
function getSawtooth(t, freq, amp) {
return amp * (2 * ((t * freq) - Math.floor(0.5 + t * freq)));
}
// ==========================================
// MAIN SCRIPT LOGIC
// ==========================================
const result = [];
const durationMs = DURATION_HOURS * 60 * 60 * 1000;
const stepMs = Math.floor(durationMs / (NUM_POINTS - 1));
for (let i = 0; i < NUM_POINTS; i++) {
const pointTimeMs = START_TIME.getTime() + (i * stepMs);
const dateObj = new Date(pointTimeMs);
const waveTimeMs = pointTimeMs + currentTimeOffset;
const tDays = waveTimeMs / (24 * 60 * 60 * 1000);
let v = BASE_OFFSET
+ getSine(tDays, SINE_FREQ, SINE_AMP)
+ getBlock(tDays, BLOCK_FREQ, BLOCK_AMP)
+ getSawtooth(tDays, SAW_FREQ, SAW_AMP);
v = Math.max(0, v);
result.push({
t: dateObj.toISOString(),
v: Number(v.toFixed(3))
});
}
// Return as a strict JSON string to satisfy Homey's token expectations
return JSON.stringify(result);
Let it execute every second and send it to âGraphTestâ
Add the âGraphTestâ to the graph and watch it.
I enabled both since my last Homey ethernet adapter broke. 
So, as a fallback. But I disabled it now. Thanks, Iâll try this and report back.
I did test the script myself, and eventually it crashed homeyscript and dashboard studio haha. But when it was running it was pretty stable over here updating the graph every second.
Wow, what a lot of nice new options in the Menu widget! And what a lot of work and time you must have put into it. Thank you!
Questions arising from the first use:
The new image selector is also a major improvement!
First menu prototype using one horizontal menu and multiple vertical menus:
Sharp, ill add it on the bug list.
Ah, ill add a âstateâ setting for every menu item just like the button.
I donât understand this one, please elaborate.
You want an textual svg field inside the icons? Why? I understand the usefulness in the image widget, but why in the icon of a menu?
I do not understand this one either. You want to give each item a name? Offset values on what? Are you referring to the container label?
I have made a practical example in the demo
Read the appearing text in the demo. When the menu collapses because an item was chosen, the button that activated the menu needs to know that the collapse happened. Otherwise, the button would stay enabled. The âOutput status topicâ from the menu outputs âfalseâ when it is collapsed. If you bind this to the âstateâ setting of the button (which should be in toggle switch mode), it turns off automatically.
As of now, I donât have a solid idea for something like this, but maybe I should introduce a âdynamicâ widget. It would be similar to the container widget, but with a text field in its settings that can be made dynamic. In this field, the user could paste regular Dashboard Studio snippets, which would then materialize into the widget at runtime. This way, you could easily broadcast the same widget over multiple dashboards.
I donât know, itâs just an idea that popped up while I was writing this! It might be a nice topic to discuss with the community here. It sounds a bit niche, but perhaps it could bring other interesting use cases to Dashboard Studio?
I did not even think of that hahaha. Now every menu item needs a âstateâ setting to turn it off also.
The orange button in the main menu and selected submenu shows the currently activated menu.
I would like to use small svg images/icons that are not available in default icon library but are available as an svg (no url).
Could the following do the job: define an image with a svg and do not use an icon in front of a specific menu option. Hide and show the image (with a size and location of an icon) with the menu status?
Defining a horizontal menu, by default the menu names are visible and use space (see âNieuwsberichtenâ). In my example I only use icons without text and I want the icons to be equally spaced.
Several workarounds: define font size 1, or shorten the icon names and set the font opacity of the menu item to 0. What is the best solution for only showing Icons in a horizontal menu?
Which comes to another question: can I center the menu names under the icon, which is not uncommon.
Would you define buttons as a main menu and use the menu widget for submenus? Thatâs why I struggle with these menu item texts I thinkâŚ
I can think of even more options, but it has to remain workable. I admit: there are already a lot of options, and it takes quite a bit of time to figure out how it works (already). 
Have you had time to think about the above?
If the screen position is 0.4, then the icon must get the status off (=screen is open) and position 0 is closed (icon on). Or do I need to define a Homey flow for this?
Ah, yes. This will be solved if every menu item has a state option which you can turn of with the menu. Seeing this, every menu item should also have a âSend Off When Turned Off by Groupâ Otherwise the dropdown menu would not collapse.
But why arenât you uploading these svg images in the gallery to use them?
Ill add it to the list 
Thatâs an option that would work right now. Like I said, I did not even think of using a menu to show sub-menus. I just had a menu that can be made in to a dropdown menu in mind. If you make the âmain menuâ buttons a member of the same âSelection Group IDâ and turn âSend Off When Turned Off by Groupâ also on, only one sub menu will be visible at the time.
âŚ. ahh shoot. I just fixed a âbugâ that one item from the selection group should be enabled. I knew this would bite me in the ass some time. I shall look if I can make this optional.
Oh, no sorry. Did not have the time to debug that one. Should be possible, donât know what the problem is (but have not tested it). Have not dived in the code. It is on the list.
Just tried it:
I donât know what the problem is, but it works like a charm over here? I suspected the 0 might be interpreted as a boolean âfalseâ or something, but that does not seem to be the case. The values converted fine and my blinds are moving as expected.
Thanks for testing, I will reverse the settings and colors.
Changing a color in the Switch wizard happens digit by digit when you enter the RGB code. After typing one digit the color setup popup closes.
@Satoer wat is supergave en handige app heb je gemaakt. Een kleine donatie gedaan aan je harde werk. Het is voor een leek makkelijk te gebruiken. Maar vaak wel voldoende om ook moeilijke dingen te doen.
Nu zou ik graag een overzicht hebben van de stroomprijzen in Tibber. Ik krijg alleen niet bedacht hoe ik dat moet gaan doen. Zou je me daarmee willen helpen?
