Hi! Thanks for testing and sending through the stack trace.
I think that error is from homey itself before my code gets a chance to run. Is there anything weird/nonstandard about your SHS install?
Hi! Thanks for testing and sending through the stack trace.
I think that error is from homey itself before my code gets a chance to run. Is there anything weird/nonstandard about your SHS install?
Nope its just a standard install.
Homey [log][ManagerAppsLocal][AppLocal:dev.5to.wiser] Automatically restarting…
Homey [log][ManagerAppsLocal][AppLocal:dev.5to.wiser] Starting…
Homey [log][ManagerAppsLocal][AppLocal:dev.5to.wiser] Session ID: dev.5to.wiser-1.0.4-e43b50ab
Homey [err][ManagerAppsLocal][AppLocal:dev.5to.wiser] Error Starting: Could not mount /dev/random : 32
Homey [log][ManagerAppsLocal][AppLocal:dev.5to.wiser] Last 10 lines Stderr:
Error: Could not mount /dev/random : 32
at file:///app/packages/homey-local/lib/AppLocal.mts:1112:25
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async AppLocal.executeStart (file:///app/packages/homey-local/lib/AppLocal.mts:1295:7)
at async AppLocal.start (file:///app/packages/homey-local/lib/AppLocal.mts:979:7)
at async ManagerAppsLocal.restartApp (file:///app/packages/homey-local/lib/ManagerAppsLocal.mts:617:5)
Is it trying to generate a random key?
ls -la /dev/random
crw-rw-rw- 1 nobody nogroup 1, 8 May 8 12:18 /dev/random
Maybe it would be best to use
openssl rand -hex 32
Hi - sorry I didn’t get a notification you’d replied. Thanks for the extra logs! It’s odd because I’ve been testing using my own SHS install - very standard through Docker.
Nope, I’m not doing anything with /dev/random. I’m still fairly certain this is before my app launches as one of the first things it does is add a log entry to say it’s up and running - and we’re not getting that far.
I noticed that there’s another app on the forum where a user has mentioned a similar error. I’m keeping an eye on it, but I don’t see a fix as yet. [APP][Pro] Skoda - #95 by Steggi
Just another quick data point:
I reproduced a very similar failure by removing privileged: true from my Homey SHS Docker compose. The app then fails before startup with a mount error for /python. I know yours is /dev/random, but the failure is in the same stage of startup, where AppLocal seems to be mounting resources before the Python app starts
Could you just check, if you’re running via docker, to see if you’re running with privileged: true as shown in Homey’s documentation?
Are you using Proxmox?
I’ve just run the Homey install script and installed the app. Exact same error as you get. I think it’s because it’s an unprivileged LXC running Docker. I’ve switched it to privileged (by backing up the LXC and restoring it as privileged), and the app runs normally again. But as that install was fresh I had no other installed apps so I don’t know if that would play havoc with other app installs.
I don’t know why it would particularly need to be privileged if everything else is working well. I can only think it’s something to do with the introduction of Python Apps SDK which seems to have only been a couple of months back.
Edit: Yeah, I’m fairly certain that’s where the issue is. I’ve added a post to the SHS Proxmox thread to see if anyone can confirm.
That was it! I forgot that I had restored the LXC container to a new host and didn’t set the new restored container to privileged
Ace. Glad you’re sorted!
Let me know if you run into any other issues!
Do you intend to expand the app? For example existing away mode and/or individual radiator TRV?
Yeah, I do have some plans for extending it, but my main push was just to see if it’d be accepted properly first!
If you have any further ideas, do let me know- I’m open to trying to making this better than it is!