FreeCAD is fairly good. Some of the controls are a bit wonky, but that is just a minor gripe. If you are starting on FreeCAD, that doesn’t matter so much. FreeCAD is good to know if you design components for KiCAD as well.
Parametric modeling is fucking awesome, btw. I am not quite sure how old that concept is though.
I just dug a little into the Flutter API and saw what might be going on. Scaling is done properly on a regular browser, but there might be a built-in function for it somewhere. It may take a few more steps with Flutter.
(Just rambling a bit for those who care about details and theory crafting.)
Calling BoxFit in Flutter is significantly less expensive for thumbnails, I would speculate. It appears that it would take a few operations to scale an image properly and could impact slower devices.
An option to enable or disable image scaling would be nice. It’s just annoying that its probably not a one line code change. (Unless it is. That would be great.)
Connect instance switching will be buggy sometimes, especially when there is a Lemmy update that modifies auth tokens in some way.
The only way I know how to resolve account list bugs like that is to purge your app cache and app data. It’s not ideal, but it has worked for me in the past.
This is fairly common with remote sensors. Some are perfect and exist in a perfect system, some do not. I am going to rattle off some of the first things that pop into my head…
Honestly, there are a thousand reasons that you could miss a data point every once in a while. Just looking at the chart, it is still sending a data block but the humidity just reported low for a second. Maybe the thermostat is not getting a data block and filling in the data based on its own clock.
Compare it to other data and see if the system turned on or off. Electronics can be sensitive to power drops and it wasn’t able to feed power to the part of the board that manages the sensor for a second. Maybe there is a condition where a capacitor gets fully discharged for a second and is pulling all current away from the sensor. (It’s usually an analog signal from sensors and maybe a measurement of resistance that translates to temperature or humidity. A voltage drop would significantly impact a reading.)
It could be a timing glitch with the code where it can’t read the sensor but builds the data block anyway. Depending on how the sensor works, it could be trying to compute the data the second it gets polled for data and it has nothing to give.
It could even be the wiring to the rest of the system. HVAC systems vibrate and a screw might be getting loose. It could be a cold solder joint, even. What is to commonality between the two thermostats that you had?
The list goes on. I have always treated sensor data as unreliable. Heck, I have a couple of CO2 sensors that do the same this as what you are seeing here. Every so often, the just report zero for a second.
Mesh protocols like zwave and zigbee aren’t 100% reliable. It could be local interference with the signal.
Without some extensive debugging and the willingness to disassemble your thermostat, just treat it as an annoyance.