Dear @DaneedeKruyff you are absolutely right. A bit wired translation of the Flow names (arming and inserting into Italian are almost the same) made me making the mistake.
Now that I changed the flow card everything seem working smoothly.
Thanks again.
Could be your homey is to busy during restart, result of the under clocking by a lack of power, but this shouldnât happen and I havenât seen this before. (But there a still a lot of random errors thrown due to underpowered Homeys)
When this happens next time, please send me a diagnostics report before you restart Heimdall.
i tried to reboot several times with 5.3V stable power supply and seems to be ok.
the strange thing is that i have a lot of devices (shellys, zigbee, zwave, HA integrations, netatmo⌠) then a lot of apps and only heimdall suffered for this. iâll let you know if it happens again. thanks.
Well, thatâs not so strange, specific brand apps only rely on themselves to be stable and the technologie they use e.g Zigbee or Z-Wave etc. Heimdall relies on all others apps and Homey itself to be fully started and stable. Heimdall takes this into account when starting but sometimes strange things still happen, also not forget the firmware is still not released as stable.
Thanks, for the log, unfortunately it shows no error for Heimdall just the starting sequence. Did you send this after restarting Heimdall?
I do notice 63 reports of devices not ready when Heimdall starts, Heimdall will continue and they will be added letter when (if) they become available so that shouldnât be a problem.
The strange thing is, when you manually reboot there doesnât seem to be a problem but after a firmware upgrade there is a problem. Could you please report that to Athom specifically mentioning that.
Ok if itâs from before restarting then the app did not recieve any warnings from homey.
Regarding the voltage, while you supply 5.3volt is doesnât prove the cpu wonât register a voltage drop under load, please do check those values at the developers pages.
Thanks, this is usefull information for Athom to improve the firmware and firmware update process.
Thanks, That report also shows no indication what is going on, no error in it. The log looks normal, no app crash or warning from Homey itself towards the app so I have no idea where I should start to âfixâ this as nothing wrong is reported.
Even though I have no insight in the exact number of users using Heimdall on the Homey Pro Early 2023 there are quite some judging by error reports I receive on other quirks in the firmware, as far as I know this problem is limited to your Homey/situation so I have not much to go on.
What I did notice; youâre running version 10.0.0-rc.69 which is an experimental version of the Release Candidates. My first advice is to disable the Experimental Updates in the Developer Tools if you rely on this Homey for your home automation
Second advice is to disable automatic updates (for now) so you are in control when your Homey reboots after an update and can immediately take corrective action if Heimdall shows problems after a reboot/firmware install.
To keep up with the changes made by Athom to the homey-api Iâve updated the used version in Heimdall to the latest Release Candidate.
Iâve also made some improvements in the way the zone name of a device is read while it is no longer available as a property on a device and needs to be retrieved separately. Somehow the function to retrieve zone information is an expensive one on old Homeys, I received many errors from them. This change will hopefully solve that error.
After the previous test version I still received some automatic error reports, but luckily a lot less. Iâve made another minor changes which I hope will improve retrieving the zone names even more.