pageflight

joined 1 year ago
[โ€“] [email protected] 11 points 2 months ago

Yeah, if you don't want the next dev (or your future self) to accidentally undo that corner case you fixed, better put a unit test on it.

[โ€“] [email protected] 4 points 3 months ago

Just being forced to talk about how it's going and what's blocking can be helpful, so I'm glad you're questioning for to be more useful, not doing a little rubber-ducking isn't all bad.

 

I put three DS18B20s on a wire along with three SHT30s on D1 mini shields, all in a cardboard box indoors, for a day.

My conclusion is that the DS18B20s are actually more accurate. My Fluke's thermocouple also agreed with them.

The SHT30s all read several degrees higher, with the one that was at an angle reading a little lower than the others which were flat. When I turned them all on edge their temperatures converged a bit lower but still a bit high. I wonder if some of the spikes from their readings are just microcontroller activity.

I'm hoping to use the Tasmota TempOffset command to adjust.

 

The DS18B20 (on a Feather Huzzah) seems to miss some rapid changes that the SHT30 (on a D1 mini shield) reports, even though TelePeriod=60 for both. The DS18B20 does seem to report changes within 60s of each other sometimes so I think we're just seeing duplicate values elided, which I do expect.

The thermostat on the wall near them (which they'll be replacing) reports 70F, closer to the DS18B20. I have a thermocouple for my Fluke multimeter which I may try to calibrate in ice water and then use to calibrate the temp sensors, though I'm curious if there's an easier way; or I might not bother since I care more about just setting the climate for room comfort than specific numeric temperatures.

The data path is: Tasmota -> MQTT (Mosquitto) -> HomeAssistant -> InfluxDb. In this case the chart's just in InfluxDb's data explorer, though I have some dashboards in Grafana too (which was the motivation for having Influxdb).

[โ€“] [email protected] 1 points 11 months ago

Where does the NYPD keep getting these expensive but apparently useless robots?

[โ€“] [email protected] 1 points 11 months ago

Right. I care less about 60% less power, and more about will it randomly connect my phone to my car as my partner drives away instead to the speakers I was already using on the desk next to me.

[โ€“] [email protected] 2 points 1 year ago

There's still a huge racial disparity in tech work forces. For one example, at Google according to their diversity report (page 66), their tech workforce is 4% Black versus 43% White and 50% Asian. Over the past 9 years (since 2014), that's an increase from 1.5% to 4% for Black tech workers at Google.

There's also plenty of news and research illuminating bias in trained models, from commercial facial recognition sets trained with >80% White faces to Timnit Gebru being fired from Google's AI Ethics group for insisting on admitting bias and many more.

I also think it overlooks serious aspects of racial bias to say it's hard. Certainly, photographic representation of a Black face is going to provide less contrast within the face than for lighter skin. But that's also ingrained bias. The thing is people (including software engineers) solve tough problems constantly, have to choose which details to focus on, rely on our experiences, and our experience is centered around outselves. Of course racist outcomes and stereotypes are natural, but we can identify the likely harmful outcomes and work to counter them.

[โ€“] [email protected] 0 points 1 year ago

Yeah, I just got a few of the CloudFree Motion Light Switches and am quite happy with them. I had some trouble initially but then figured out I needed my 2.4GHz network to have a fixed channel, apparently that's a common thing with Tasmota on some chips. Now I have one pair acting as main/remote for my basement lights, and some others just acting as motion sensing switches but with the benefit of being able to monitor motion remotely.