Now it (image refresh) works like a charm !
Thank you, Michel, and congratulations again on your work, I really admire it ! Even though I don’t use all the features (calendar, graphs, etc.), I think you deserve credit for creating the most powerful and polished Homey app. Thank you also for your responsiveness and dedication to always delivering the most stable and high-performing product as quickly as possible. And all of this for €0!! Honestly, it’s very impressive !
NB : A small PayPal donation to thank you
Also: from previous posts I understood the underlying algorithm which data points to show is complex, resulting in a more or less ‘random’ outcome after the interval is set. In this graph, it means only some of the grid power values are shown and some of the returned power. That doesn’t make sense. It even happens when the interval value is set to 0,001 (as said: in viewer, in editor all values are shown). As suggested, the complexity might be less if only the x-axis and y-axis (and related gridlines) are calculated and set on multiple (stacked) graphs and settings like point values are set independently per graph (of course, if possible…)
Still figuring out a lot of things. Is there a way to dynamically change an image based on a state. Eg. i have two images of my card. One where he’s connected to load the battery and one where he’s not connected. So I would like to change the images based on the connected-state of the car.
But aren’t you comparing a peak value for a day to the average value of a whole day in the bar graph? There’s a good app called power by the hour if you want to collect day, month, and year energy statistics. You can use those values to create graphs as well.
Yeah, but I thought pushing it down to keep it in the graph would be better than cutting it off. You could also give the graph a bit of headroom, then it doesn’t need to push down:
Maybe a more convenient way is to use the icon widget. You can also use images in the icon settings instead of icons. Set the icon source to custom icon and add both images to the Icon and Active Icon:
(You can select the images by pressing the icon next to the URL box and pressing the “+” in the gallery)
Now you can flip between the two images just by making the “active state” dynamic and sending a true,1/false,0 value to it.
This way only one of the images is visible based on the incoming value.
Does your car app have some kind of “charging” boolean? If you enable that capability in the Homey Dashboard Studio settings, you don’t even have to use a flow to flip the images.
Just thought of another easy solution, although I consider the build in formula engine a bit of a more “advanced users” solution, I think this is easy to understand.
Add a single image widget and make the URL dynamic (chain icon). Select the “connected state” topic you have enabled. Click the “binding options” button. Here you can fill in a formula. Use this: if(value, "/images/image1.jpg", "/images/image2.jpg") :
In line charts, negative values are filled using the “Positive fill color” setting; this works correctly for bar charts.
Improve the logic of the chart definition order: define the “Visual type” first, and then specify the colors, as the latter depend on the chart type.
Make y-axis values more readable in graphs like example below: air pressure. For gauges, there is an “Abbreviate large values” (y/n) option; perhaps this could also be implemented for charts.
There is already a graph option with the same name, but that’s for “Point values” only.
Yeah, this is 2.3.5 with some extra options (like being able to change the line opacity). Thanks for the snippet. I see it now. It’s weird though, the negative fill color actually does change if you change the color. I’ll look into it.
Bars can be stacked on top of each other
Bars can be stacked on top of each other now instead of just side by side.
Invert Graph Point Values on Negative Numbers
Added an Invert Y on negative values setting so point value labels automatically display below negative bars and data points and above positive ones.
Graph Axis Titles
Name the category and value axes. The title is drawn outside the ticks when the field has text.
Graph Line and Bar Opacity
Set how solid the positive and negative lines or bars are, separately from the fill.
Abbreviate Graph Axis Numbers
Large value-axis numbers show as thousands and millions, such as 12.5k. Turn Abbreviate Large Values (k, M) off to print the full number.
Changed
Moved Rotate to the Typography Settings
Category and value rotation now sit with the other axis text settings, under X Axis (Datapoints) and Y Axis (Value). Users that used this setting might need to redo this setting.
Fixed
Smaller Graph Fixes
Time axes stay responsive, streaming holds the right edge, hover hits the bar under the pointer, and axis titles stay on their own side.
Negative Graph Fill Color
An unset negative fill now uses the negative line color shown in the picker.
This is now possible. You can stack bar graphs on top of each other and also change the opacity of the graphs. It is also possible to make every bar graph on top of the other a bit smaller:
You mean move the whole sections? Not going to do that. I like to keep the section order for each widget as consistent as possible. Besides, “Visual type” is already first if you use the built-in presets.
You’ve mentioned this before. Every time I looked at it I thought, “But the values are already abbreviated…” Since it was already implemented, I never gave it another thought. But now I get it. You want to be able to turn it OFF. Not on. This is implemented now.
Added.
I haven’t figured out why your graphs are still an hour off (this is still the case right?). Are you sure you have the UTC correction enabled right? It sounds like the Homey or the machine running it is in the wrong timezone or something. I’m not having this problem myself, and other users say the time is correct. Can you check your Homey time by running this HomeyScript?:
// HomeyScript: Complete Timezone & System Time Inspector
const now = new Date();
const epochMs = Date.now();
const tzOffsetMinutes = now.getTimezoneOffset();
const intlOptions = Intl.DateTimeFormat().resolvedOptions();
console.log('=== Sandboxed JS Runtime ===');
console.log(`Epoch Timestamp (ms) : ${epochMs} <-- Insights storage timestamp`);
console.log(`ISO 8601 (UTC) : ${now.toISOString()}`);
console.log(`Sandbox Local String : ${now.toString()}`);
console.log(`Sandbox Timezone : ${intlOptions.timeZone} (offset: ${tzOffsetMinutes} min)`);
// 1. Inspect System Information
let homeyTimezone = null;
let homeyDate = null;
try {
// Check available methods on Homey.system
if (typeof Homey.system?.getInfo === 'function') {
const info = await Homey.system.getInfo();
homeyTimezone = info.timezone || info.timeZone;
homeyDate = info.time || info.date;
console.log('\n=== Homey System Info (getInfo) ===');
console.log(`System Timezone : ${homeyTimezone}`);
console.log(`System Reported Time : ${homeyDate}`);
console.log(`Language / Units : ${info.language} / ${info.units}`);
} else if (typeof Homey.system?.getState === 'function') {
const state = await Homey.system.getState();
console.log('\n=== Homey System State ===', state);
} else {
console.log('\n=== Homey.system Methods ===');
console.log(Object.getOwnPropertyNames(Object.getPrototypeOf(Homey.system)));
}
} catch (err) {
console.log('\n[!] Error querying Homey.system:', err.message);
}
// 2. Inspect Clock Module (if present in API)
try {
if (Homey.clock) {
console.log('\n=== Homey Clock Module ===');
if (typeof Homey.clock.getTimezone === 'function') {
homeyTimezone = await Homey.clock.getTimezone();
console.log(`Clock Timezone : ${homeyTimezone}`);
} else {
console.log('Clock methods:', Object.getOwnPropertyNames(Object.getPrototypeOf(Homey.clock)));
}
}
} catch (err) {
console.log('\n[!] Error checking Homey.clock:', err.message);
}
// 3. Inspect Geolocation / Location
try {
let geo = null;
if (typeof Homey.geolocation?.getGeolocation === 'function') {
geo = await Homey.geolocation.getGeolocation();
} else if (typeof Homey.geolocation?.get === 'function') {
geo = await Homey.geolocation.get();
} else if (Homey.geolocation) {
console.log('\n=== Homey.geolocation Methods ===');
console.log(Object.getOwnPropertyNames(Object.getPrototypeOf(Homey.geolocation)));
}
if (geo) {
console.log('\n=== Geolocation Coordinates ===');
console.log(`Latitude, Longitude : ${geo.latitude}, ${geo.longitude}`);
if (geo.city || geo.timezone) {
console.log(`Location / Timezone : ${geo.city || ''} (${geo.timezone || ''})`);
if (!homeyTimezone && geo.timezone) homeyTimezone = geo.timezone;
}
}
} catch (err) {
console.log('\n[!] Error checking Homey.geolocation:', err.message);
}
// 4. Calculate Rendered Local Time for Graphs/UI
if (homeyTimezone) {
try {
const localFormatted = new Intl.DateTimeFormat('en-GB', {
timeZone: homeyTimezone,
dateStyle: 'full',
timeStyle: 'long',
}).format(now);
console.log('\n=== UI / Graph Graphing Representation ===');
console.log(`Resolved Timezone : ${homeyTimezone}`);
console.log(`Rendered Local Time : ${localFormatted}`);
} catch (err) {
console.log('[!] Error rendering localized time:', err.message);
}
}
return {
epochMs,
homeyTimezone: homeyTimezone || 'Pending detection',
};
This is also solved. But you have to load a pre 2.3.0 dashboard to get this data migrated again. I think you already solved this manually, so no need to do anything.
But this seems like something “basic” that should be possible. (Although you are the first to ask for this) I’ll think about how to integrate it. It probably needs some kind of new page rearrange dialog where pages have names, otherwise you wouldn’t know what you’re rearranging. I would also need to add options to relink all the widgets to the right page.
I’ve started using this incredible app to define some nice dashboards. One thing I haven’t found, and sorry if I haven’t searched enough, but is it possible to change Theme dynamically? E g one theme in daytime and another in nighttime, based on a value from a device.
You can make this one dynamic by clicking the chain icon. Sending theme names to it changes the theme. The dashboard software doesn’t have any built-in timers. You’ll need to use Homey to send the theme name to that topic and let it trigger using a time of day flowcard.
Presentation improvement suggestion for graphs:
When using ‘live stream’ data, the graph moves with the time, leaving a ‘empty space’ (in the picture, right from the values 345 and - 161) behind until the next data point has arrived (every x time). Maybe it’s a setting I missed(?), otherwise I think it’s nicer when the widget manages the value of the most recent datapoint is kept until a new datapoint arrives, so the graph no longer shows this empty spaces and look&feel becomes ‘smoother’ (this is the same behaviour I see in the Homey app when for example realtime P1 data are shown in a widget).
I understand the “problem”. I shall think about it. Maybe make this an optional setting, because I personally do not think the graph should just guess values. On the other hand, lots of sensors only update if something is changed, so in that case it is not guessed, it is still the same value but simply not changed yet.