• 0 Posts
  • 54 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle
  • I tried a similar scenario: The phone has a nfc reader built in, so I put the tag on the charger and tried letting the phone read it, but quickly discovered that android can’t/wont read nfc tags unless the phone is unlocked, which defeated the elegance of the solution. I hadn’t considered buying a standalone reader and attaching the tag to the phones, that sounds a lot more complicated.


  • Using an Automation APP like Tasker to turn off a Home Assistant-controlled smart plug when the battery exceeds a reprogramming threshold, might be a more reliable method & works for any device.

    This is the method I have been using for years and it works great. I use Home Assistant to manage the automation, the Home Assistant client app for Android (you could use tasker for this) to collect the device telemetry to send to Home Assistant (how it knows when the battery hits 85% or drops below 70%).

    I do want to point out there is one small downside to this method: your device charger (and I’m using an Anker wireless phone charging stand as my charger) only works for one device. Example, say my personal phone is charged up to 85%, so I take it off the charger, but my work-issued phone needs to be charged, but when I put my work phone on the charger nothing happens and it doesn’t charge because the charger is connected to a smart plug that’s turned off because my personal phone is charged up.




  • Are you just talking about dynamic DNS services for one or a few home servers?

    There’s always DynDNS, but that’s a paid service. I actually discovered that dynamic IP address service was provided free by Google when using Google Domains as the registrar, so I moved a few of my private domains over to Google several years ago to save myself $55 a year.

    Unfortunately, Google Domains is shutting down and all registrar services and existing customer domains are getting moved to squarespace and I’ve not yet been able to determine if squarespace is going to be offering the free dynamic DNS service or not.









  • No, you’re not paranoid. I’d call it diligent.

    The premise of the statement you quoted is faulty to the core. A device internal to your home network knows a lot about the design of your home network and it knows a lot about the other devices on your network, and it can be used to facilitate/relay malicious access to your other devices if it becomes compromised.

    Wyze has always struggled with security problems…and I’ll admit that I do have several wyze cameras…but long ago decided their security was not trustworthy and created an entirely new virtual lan to run just my IOT stuff from. That, at least, reduces the exposure for some of their security issues. I certainly would never have interior cameras built by wyze - that’s too risky even with robust network security on my side of it.




  • The article says:

    The French agency that regulates radio frequencies, the ANFR, has notified Apple of its decision to ban iPhone 12 sales after tests showed the Specific Absorption Rate (SAR) was above the allowed limit.

    Followed by this quote:

    The ANFR said it would verify that the iPhone 12 models were no longer being offered for sale in France starting today.

    That sounds a lot like “banned” to me. Considering those two quotes, I don’t think the article title is misleading. It sounds like they are banning sales effective immediately, and will force apple to conduct a recall if they can’t retroactively fix the already sold units.


  • From the article:

    The agency noted that tests measuring radiation absorption rates at a distance of 5cms (1.98 inches) showed that the iPhone 12 was in compliance with the limit of 2.0 watts per kilogram.

    But it also says that:

    The ANFR said accredited labs had measured absorption of electromagnetic energy by the body at 5.74 watts per kilogram during tests simulating when the phone was being held in the hand or kept in a pocket, writes France 24. That’s higher than the European standard absorption rate of 4.0 watts per kilogram.

    That sounds like different test methodology was used for the test it is currently failing? There is a difference between “from 5 cm” vs “held in hand” or “kept in a pocket”.

    It makes it sound like the iPhone 12 was in compliance earlier, but is not in compliance now with different test methodology.


  • It’s not per kilogram of the device. It’s a measure of absorption per kilogram of body mass of the person using the device.

    A good way to think about it is: throw a small piece of meat into the microwave and let it absorb some microwaves. It gets warm. Now imagine a much larger piece of meat. It can absorb a lot more microwaves before it starts getting warm. The smaller the ‘body mass’, the less radiation it can absorb and dissipate before becoming damaged. So when it comes to mobile device radiation levels, they focus on the watts of radiation absorbed per kilogram of body mass.



  • Headline is a bit misleading. It’s not part of California state law yet. The bill needs to go back to the senate for a procedural vote, then needs to be signed into law by the Governor. It’s probably a foregone conclusion that both those things will happen given the unanimous support for the bill, but I just wanted to point out that it’s technically not a done-deal yet.

    iFixit obviously has some vested interest in seeing this pass, but at the end of the day they’ve accomplished something great for the country. I can’t wait to see how this actually impacts consumer products going forward.