Can’t relate, it closes right away / doesn’t open twice
Which app version do you run?
Which Homey model & firmware?
It doesn’t happen to me either. I assume that you have not yet installed the latest version 0.2.7. Please check it out once. Thank you
I think I’ve found a possible cause. But now I have to find out how I can fix this 
Everything is up to date; the app version is 0.2.7, and the Homey is also running the latest update, 13.4.1.
Thanks, and hopefully you can resolve this.
By the way, I have one other issue. The luminance sensor only updates the LUX value when I close and reopen the Homey app. The floor plan has to be reloaded for me to see the latest LUX value.
Sorry, but I can’t do anything about it, apparently that’s only the case with you. Neither at SingKT nor at Peter_Kawa or with me this problem occurs.
I will test the problem with LUX value and look for a solution, but will probably not be the case until next week. I’ll get back to you as soon as I find out.
Thanks for your feedback 
Hi @SingKT,
Thanks for the detailed Firefox vs iPad comparison screenshots — that made the actual cause much easier to pin down than I expected.
What’s happening: the widget calculates where to draw a device by re-deriving the visible image size from the container size and the image’s aspect ratio, instead of just reading the actual rendered image box from the browser. That math should match what gets drawn, but mobile WebViews (iOS/Android, like Homey’s app uses) can size an intrinsically-scaled image slightly differently than desktop browsers — which is exactly why it looked fine in Firefox but drifted on iPad/Android.
Fixed now: the widget measures the actual rendered image directly, the same way the edit page already does — so it can’t diverge from what’s really on screen, on any platform.
Thanks again for taking the time to test this so thoroughly — that side-by-side comparison was exactly what made this fixable.
Hi @Rembo038,
I’ve already come to that, the mistake was obvious 
Thanks for reporting this — found it. The widget fetches the value correctly on load, but live updates from Homey were silently getting dropped: the backend was sending the raw number straight through, while the widget’s realtime handler only accepts a small wrapped object (the same shape a fresh load already gets). A bare number failed that check and got ignored — which is exactly why it only ever updated after a full reload.
Fixed now — live LUX updates should come straight through without needing to reopen the app. This also affects any other standalone measure sensor (power, CO2, a temperature/humidity sensor not paired into a combined device, etc.), so it should help beyond just luminance too.
Thanks again for the clear report!
Okay, that is indeed a bit strange, but if nothing can be done about it, then so be it. I’ll just have to click twice; it’s not that much trouble, haha.
No problem, thanks for looking into it! Once I’m home, I’ll test whether the LUX value updates in real time.
Hi @Asterix
I just got home and immediately tested the real-time LUX update.
However, it isn’t updating in real time; I still have to refresh the homey app. I can see the LUX value changing in Homey, but on the Spacey floorplan, it only updates after I close and restart the mobile app. I restarted both the app and the Homey Pro, but that didn’t help either.
Perhaps it would be a good idea to add a button to the floorplan to refresh the floorplan? That is, if it’s possible; the idea just occurred to me as an alternative to having to restart the entire mobile app just to refresh the Spacey floorplan.
Thanks for the help!
Hi Rembo,
You’re just a bit too quick.
The proposed code by Asterix is not added to the app yet, or isn’t published as app update @ app store yet.
Only when a new version is announced here /or under “View Change log” on the app page in the app store, you can install the update & run your tests.
Hi Peter,
Oh, that explains a lot; I was a bit too quick to judge 
.
Then I’ll wait for the next update of the app.
Keep up the good work, it is an amazing app!
Hi Rembo038
Ludvig has just released version 0.2.8, please test it, I would like to hear your feedback.
Hi @Rembo038,
Thanks again for confirming — really appreciate you testing it directly. For anyone else following along: this was a deeper bug than my first attempt caught (the backend was sending the wrong device identifier to the widget, so the update never reached the display at all, regardless of the value format). Fixed now and submitted to Ludvig: Fix realtime device id mismatch preventing live measure_* updates by Asterix-m91 · Pull Request #7 · ludvigaldrin/com.svipler.app.spaceyplan · GitHub
But you have to wait with testing, only when Ludvig has uploaded the new version 
pushed
is there a trick to see the temperatuur with decimal’s? if you use a device that wil show the temperatuur?
Confirmed, also with Watts and temperatures.
Very nice request & implementation!
Good idea!
@Asterix is it possible to add the decimals to temperature sensors?
