i did. 2.4 A 5.1 volt from my old samsung tablet and a newer one from samsung which i charge my galaxy 24 ultra with. both are good and working but no difference on the homey.
when I update firmware it get stuck on verify at the end of it.
edit: after a long time verify finished and found ok.
i just don’t want to factory reset and have to do everything again. 40+ devices and god know how many flows. i rather wait till new firmware or a way to put experimental firmware on it. backup has same firmware and stuff so that won’t help i guess.
nope. only if you make these in usb tool (which i forgot :-/, was running flawless since march ‘23) or have a backups subscription.
there are logs but not accessible when it crashed. logs only go so far. there is a app for more extended logs i thought. But yeah just the basics, not in dept.
Only when you root your Homey (which may or may not void your warranty). And apps that make extended logs (as @Da_JoJo suggests) only make logs from data available through the SDK/Web API, which is too high level and not helpful at all when trying to debug crashing issues.
I wrote a TelemetryCollectorApp that solves the log problem. The only downside is that the respective app developer also has to integrate it (the effort is about 10 minutes).
I think we’re talking about a completely different log problem here. Your app is unable to access the relevant information that might provide clues as to why a Homey is crashing.
I wrote an API for the app that runs in the Homey app process/container itself.
And there are already options for the process itself (such as uncaughtException), but I didn’t pursue this because I didn’t think Athom would be very happy about it and I wanted my app to be published.
Totally correct. Which sucks in my case (and probably some others). Already send numerous requests in the years since homey existed as beta.
But yeah i still need to know how i get experimental firmware on mine on usb mode. I do a simple guess that the problems is in the last firmware’s memory handling of apps which are loosened and altered in successive firmwares. Hence I thought it might be helpfull to try. As they should run in subcontainers it should not crash the homey itself and kill these automaticly or restart them. Either way it shouldn’t end up in crashing the core system. System is still accessible and working as i can make a full backup and upgrade firmware the same version. It boots a long time with white ring in the end resulting in a red breathing ring. Can only acces file system on usb and the ssh, running also in a container, is of no use. Getting root is another thing. Protection of the core system is pretty decent .
I decided to wait for next firmware and see how that fares. Last option a factory reset but I will not be happy with that. Although it might be a good idea to check if the homey still functions 100%.
Any ideas welcome (besides the obvious like powersupply etc
The most important requirement that you need is the ability to read/write ext4 filesystems. The post suggests that this is possible from Windows, perhaps the Windows Linux subsystem can do this without any external app requirements.
.
(besides the obvious like powersupply etc