My new Accessible Sensor Readout app for Windows@FreakyFwoof Grabbing now. Gimme a minute; I uninstalled the framework tool because it wasn't accessible, so I've gotta install that first.
My new Accessible Sensor Readout app for Windows@fastfinge OO, try turning off the checkbox in CTRL+L, it may have done that to hide what it thought were stopped or 0 RPM fans. Sometimes it exposes more things.
My new Accessible Sensor Readout app for Windows@FreakyFwoof No, no luck. I did check that the command line tool is available, and the HTTP API is running on 127.0.0.1 and can see fan temps.
My new Accessible Sensor Readout app for Windows@FreakyFwoof Still not working, but I see the problem. From the debug log: 2026-05-08 12:23:41 [Debug] Framework Control API probe failed for 127.0.0.1/api/thermal/history: The operation has timed out
My new Accessible Sensor Readout app for Windows@fastfinge I think that still won't work because the way your client pasted it was without port, and therefore TC copied it without port, so it's looking on 80. I've opened it on the web, now I see it truly.
My new Accessible Sensor Readout app for Windows@fastfinge Fixing now. It's something to do with I guess your instance being slightly non-Mastodon or someting. Not sure.
My new Accessible Sensor Readout app for Windows@FreakyFwoof Or tweesecake being weird about http links with ports in them. We're so close. I can see it in the log trying to call all the right things, so it looks good once it gets the right port.
My new Accessible Sensor Readout app for Windows@FreakyFwoof You'll also want to update the documentation to have a section for framework owners. Before running your program, they need to:
My new Accessible Sensor Readout app for Windows@FreakyFwoof All framework laptops (12, 13, 16, etc) are supported. The desktop is not, but the desktop just uses the standard way of reading fans so it should already just work.
