Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
IT Technology

Logitech Will Brick Its $100 Pop Smart Home Buttons on October 15 (arstechnica.com) 92

An anonymous reader shares a report: In another loss for early smart home adopters, Logitech has announced that it will brick all Pop switches on October 15.

In August of 2016, Logitech launched Pop switches, which provide quick access to a range of smart home actions, including third-party gadgets. For example, people could set their Pop buttons to launch Philips Hue or Insteon lighting presets, play a playlist from their Sonos speaker, or control Lutron smart blinds. Each button could store three actions, worked by identifying smart home devices on a shared Wi-Fi network, and was controllable via a dedicated Android or iOS app. The Pop Home Switch Starter Pack launched at $100, and individual Pop Add-on Home Switches debuted at $40 each.

A company spokesperson told Ars Technica that Logitech informed customers on September 29 that their Pop switches would soon become e-waste.

This discussion has been archived. No new comments can be posted.

Logitech Will Brick Its $100 Pop Smart Home Buttons on October 15

Comments Filter:
  • Makes sense (Score:5, Insightful)

    by i_ate_god ( 899684 ) on Wednesday October 08, 2025 @01:52PM (#65712564)

    The economy doesn't work if you buy things that last.

    • CONSUME (Score:5, Funny)

      by OrangeTide ( 124937 ) on Wednesday October 08, 2025 @02:07PM (#65712610) Homepage Journal

      And if you don't consume, then you're communist scum!

      • Re:CONSUME (Score:5, Insightful)

        by saloomy ( 2817221 ) on Wednesday October 08, 2025 @02:36PM (#65712720)
        We need legislation that all equipment that is no longer supported be open sourced, and one last firmware update gives a vector to load your own firmware (or community) firmware you download. I get they have no economic interest in these buttons, but for fucks sake, if you aren't paying for it continuously, "the cloud" will stop working with it eventually. We need a way to make the device receive / send API calls locally. This should be legislated. "We no longer support your device. Here is the most recent firmware's source code, the certificates used to validate the update server, and a quick read me on how to get it to fetch a firmware from your local computer (web server with said certificate). Thanks for using our product!"
        • Re:CONSUME (Score:5, Insightful)

          by dgatwood ( 11270 ) on Wednesday October 08, 2025 @04:22PM (#65713018) Homepage Journal

          We need legislation that all equipment that is no longer supported be open sourced, and one last firmware update gives a vector to load your own firmware (or community) firmware you download.

          Yes, and it needs to apply to absolutely everything, including computers, cell phones, etc. Having hardware locked to a single software vendor is barely tolerable while the manufacturer is supporting it, but absolutely should not be allowed once the manufacturer drops support.

          But that's not really enough. Reverse engineering the hardware for nontrivial stuff is usually not worth the effort. The companies should be required to also do one of two things:

          • Release their internal documentation telling address space layout, programming info for any custom ASICs, etc.
          • Provide complete source code for their firmware, along with the toolchain required to build it.

          This serves two purposes. First, it makes it much easier for a third party to bring up a usable firmware build without having to figure out how to unsolder the CPU and install a jumper harness under it to expose the JTAG pins. Second, it greatly increases the amount of effort required to drop support for a device, which may be enough to make companies think twice about doing it, and also may make companies think twice about releasing a product without a reasonable long-term plan for how to support it indefinitely.

          I get they have no economic interest in these buttons, but for fucks sake, if you aren't paying for it continuously, "the cloud" will stop working with it eventually. We need a way to make the device receive / send API calls locally. This should be legislated.

          Devices that require the cloud should be banned, period. Any device sold should be required to provide a non-cloud-based alternative control path that never leaves your network. This falls under "minimum security requirements" even if you ignore the whole "the cloud server could go away" problem and the "I can't turn my lights on because the Internet is down, and I can't see to reboot my router because I can't turn the lights on" problem.

          But that's a separate law.

          "We no longer support your device. Here is the most recent firmware's source code, the certificates used to validate the update server, and a quick read me on how to get it to fetch a firmware from your local computer (web server with said certificate). Thanks for using our product!"

          That only helps if it is actually possible to build the firmware, which isn't a given. Also, that's opening all users up to a lot of risk if it gets installed automatically, because if there are any security holes in the device, someone would then have the global signing key and could upload new firmware that permanently compromises every unpatched instance of that device all across the planet in a matter of days.

          IMO, a much better process is something like this:

          • Devices must be able to have properly signed firmware side-loaded, either by shoving the data on a USB stick and plugging it into the device (strongly preferred) or by making the device look like a USB mass storage device when you connect it to a computer and the user dragging and dropping the firmware bundle onto it.
          • The manufacturer stops shipping automatic firmware updates.
          • The manufacturer releases a manually downloadable firmware update that allows the user to provide a replacement signing key by attaching a mass storage device or uploading it to the mass storage endpoint.

          The use of an external mass storage device (rather than the device looking like a mass storage device) is strongly preferable for security reasons, because it would be much harder (and, if done correctly, impossible) to exploit remotely and install a malicious party's key onto the device, then trick it into downloading a new firmware bundle from some other server, etc.

          At that point, the user would provide a new user signi

          • Provide complete source code for their firmware, along with the toolchain required to build it.

            You are asking too much. If a company ceases to operate and lays off the engineers, they won't be able to do this, which is no simple task.

            I would start with a requirement that such hardware be sold with a warning, similar to the health warnings on cigarettes, or California prop65 warning, informing consumers that this product may stop working at any time. The consumer should be aware of this risk before buying the product.

            • A part of bankruptcy should give the code to the public for any devices that were sold. Problem solved.
        • For all software, including embedded, the full source code shall be but into the national library of the country it is sold in - and it must be shown that it actually compile to the sold software.
          • For all software, including embedded, the full source code shall be but into the national library of the country it is sold in - and it must be shown that it actually compile to the sold software.

            Time to take your Meds.

          • This is pretty easy. You build the software with a prescribed build environment and compare hashes. It is done in high security industries to validate the code you use compiled came from the source code you audited.
      • And Consumist scum have landed us in this mess.
    • It doesn't have cancerous growth curves demanded by those trying to hit an exponential jackpot every quarter, but the economy will function just fine.

    • You're not actually "doing" anything with the button other than reinforcing trust that a company's cloud server will exist in a few years to carry out what you perceived as a linked actual, lol. Foolish to think that.

  • by gweihir ( 88907 )

    These are toys and were never designed as professional equipment. At the same time, my light-switches just keep working ...

    • Funny you should say that. I had a ceiling fan that stopped working. Various YouTube videos suggested it could be a failed capacitor in the fan. I took it apart, and everything measured correctly on my meter. The fan was fine. The problem was the switch on the wall had broken. I've had to replace four failed light switches in our house.

      They don't make them like they used to.

      • When I was finishing my basement by retired EE dad strongly suggested getting switches and outlets made in Mexico if USA wasn't available at the big box.
      • That's why the first thing I do with anything electrical is check for power.

        Disclaimer: I spent 3 years as a hardware tech. The first things checked are power and clocks.
      • by gweihir ( 88907 )

        Sounds like cheap switch quality. I am still at a lifetime failed light switches of one, and that one was about 50 years old.

        • by crow ( 16139 )

          They were all in the same house, but they were installed at three different times (2 original, 1 extension, 1 later retrofit), so they wouldn't have been from the same batch. I'm thinking they were all in places where you would often be standing to the side, so there could be side-to-side stress, which is what caused them to fail. They were all from the 90s or later; older switches might have been stronger.

          • by gweihir ( 88907 )

            Possibly. There is also the occasional bad batch where some economics graduate moron caused things to be made cheaper than possible.

  • ...I believe there should be disclosure on the packaging or product page. Otherwise they are selling an internet service, not just a physical product.

    Blue states are usually okay with such laws, the red states like to waste all their time working around laissez-faire's gotcha so that the Holy Rich can have their Holy Taxcuts. ProveMeWrong!

    • In my mind these intentionally brick-able devices violates " implied warranty of fitness [for purpose]".

      Getting an attorney and actually winning a case though. Good luck, these guys got way more lawyers than any of us consumers have.

  • by thegarbz ( 1787294 ) on Wednesday October 08, 2025 @02:08PM (#65712616)

    stands for "support".

    • What does the "H" stand for?

    • The I stands for Intranet. Don't buy crap that relies on the cloud.
      • IoT doesn't necessarily mean cloud. Plenty of IoT devices work without them.

        • by flink ( 18449 )

          IoT doesn't necessarily mean cloud. Plenty of IoT devices work without them.

          I would say most IoT devices are cloud connected. You can't have an Internet of things if the thing is not on the internet.

          Not all smart devices are IoT devices though. You have protocols like Z-Wave, Zigbee, and Matter that allow completely local control, but those devices aren't necessarily internet addressable without jumping through some hoops.

          • There's a difference between cloud connected and cloud dependent. To be clear all the IoT devices in my house are cloud connected. But 100% of them work when there's no internet connection at home as well.

    • by Falos ( 2905315 )

      (the first 'S' stands for Security)

  • by medoc ( 90780 ) on Wednesday October 08, 2025 @02:13PM (#65712638) Homepage

    Another illustration of why you donÂt want to depend on the cloud for local functions.

    • Unless they commit to open sourcing the cloud server aspect upon EOL so that the users, if they choose, can run it on their own cloud server.

  • Solve it with open source.

    • This is literally why I am investing into a purely Matter-over-thread ecosystem. While I am currently sinking it to homekit, it is not reliant on hk, and i could swap hk out with any solution under the sun, or write my own.
  • by whoever57 ( 658626 ) on Wednesday October 08, 2025 @02:17PM (#65712656) Journal

    Bosch is going to take down the servers that some of their smart thermostats use.

    The thermostats will continue to work, they just won't be Internet-accessible.

    They are sending out newer models that will be fully supported at no cost to the owner.

    • by flink ( 18449 )

      When I moved into my new house, I bought a bunch of fairly bare-bones Honeywell switches that supported Z-Wave. All the smarts are on a server I control. Short of a physical defect I never have to worry about them going out of support.

  • More like Poop switches.

  • by PPH ( 736903 ) on Wednesday October 08, 2025 @02:33PM (#65712706)

    Postage paid by recipient.

    Use the address of the Logitech CEO as the return address so they can get caught in the infinite loop.

  • by ebunga ( 95613 ) on Wednesday October 08, 2025 @02:45PM (#65712744)

    You merely paid $100 for the privilege of throwing it away before it wears out.

  • by MpVpRb ( 1423381 ) on Wednesday October 08, 2025 @02:49PM (#65712768)

    ... that requires cloud access
    The cloud is a trap
    Run away

  • People just accept this kind of thing as totally normal. As we move closer and closer to the WEFs "Own nothing:be happy", it's becoming more and more absurd that people are just OK with this.

    Watch them turn around and sell an identical product with a different color button or rounded corners or something.

    • They're frogs being boiled in slowly heated water. Thanks, I'll stick with my ancient manual light switches et al.
  • Arent there open source projects like home assistant that can do the same thing?
  • Specifically cross-platform, not vendor-app or vendor-cloud dependent.

    I still have some Hue bulbs, and a few WiFi bulbs that are dependent on vendor lock-in that I'll be replacing when they go out.

    Any newer devices are Matter/Thread compatible. Local control, no vendor lock-in.

  • Thank goodness it wasn't open source...can you imagine? People might still be able to use a thing they bought, err, I mean "inadvertently rented without realizing it".

    And we can't have that, now can we?

  • So Logitech are pulling another Squeezebox? I'll buy their mice, but anything else - no thanks Logitech.
  • And you can make a useless machine out of them.
  • Wonder if someone can do a software fix ? But I never bought any.
  • I will probably never "adopt smart homes." Good old metal key to unlock my door, ancient Honeywell dial to control the temperature, refrigerator with no screen or wifi, optical peephole in the door, and TOGGLE SWITCHES FOR LIGHTS.
  • They bricked all of my Squeezeboxes.
    And then they stopped making the Trackman Marble.

    I'm done with Logitech.

Contemptuous lights flashed flashed across the computer's console. -- Hitchhiker's Guide to the Galaxy

Working...