Resetting and using Philips Hue bulbs with the Amazon Echo or hub

The Amazon Alex app is a unifying console for IOT and other experiences.   I recently struggled trying to reset some legacy Zigbee devices that were paired with controllers I no longer had. It turns out I can use that app to reset my bulbs even though:

  1. It isn't obvious how you reset devices.
  2. The failure connect screen doesn't offer reset as an option.
  3. The program doesn't list my Amazon Echo as being able to do that on the screen where it describes resetting the devices.

Backstory

I received a pair of white Philips Hue A19 bulbs as part of an Amazon promotion.  Later I sold my Echo and got a new Amazon Echo with the built-in hub.  Newer Hue lighting supports both Zigbee and Bluetooth while older devices are controllable over Zigbee networks. 

Never have I ever owned a Philips Hue hub.

The bulbs must be reset to factory settings to onboard them to a new hub. In my case, my 4th gen Amazon Echo. The older bulbs can't be reset over Bluetooth. I couldn't get the rapid on/off power reset sequence to work.  Frustrated, I put the bulbs into the closet for a couple years until Amazon added a serial number-based reset hook in the Echo app.

Launch the Echo app and start adding a device

This is the standard new device startup screen


You are adding a device

There is a lot of stuff in this application.  I just want to add my bulbs.



It is a light bulb

Yup just a bulb here.  



Scroll down until we find the Philips devices

They are Philips Hue devices.

There it is

Phillips Hue is one of dozens of vendor options.

This would work for a new un-initialized device

There is no obvious way to reset the devices so we can just try auto-connect.

I'm a guy so it wouldn't occur to me to click on the question mark help icon in the upper right corner.

Hope springs eternal

It won't work because the bulb is still bound to the Amazon Echo or hub that we got rid of or we bought these bulbs used.

Find the serial number on the bulbs

The Amazon app can signal a hard reset to Philips Hue bulbs if we know their serial numbers. We are going to need the serial number of the bulb.  The bulbs can be reset or controlled if we have physical access to the serial numbers written on the sides.

Try again with the serial number

The Alexa app can reset a bulb if it has the serial number.  Lets try and find the device again.

Find Philips in the device list again

Here we're searching instead of scrolling.  We end up in the same place.

Click on the help question mark

This time we're going to ask for help.

This totally isn't obvious.  The help screen is a mash-up of functionality and some incomplete text and comments.

Scroll until you get to the Philips section

You can't see what you need at first so scroll.  You may be able to see the start of your section.  

Connect smart home devices to Echo Show Plus or Echo Show.  

The Amazon Echo isn't mentioned even though it can act as a Zigbee hub.  I stared at that a while because I don't understand why the Echo isn't mentioned.








Click on Reset Phillips Light

The page only mentions the Echo Plus and the Echo Show but it works for the ball-shaped (spherical) Amazon Echo!

Click on the Reset Philips Light in blue at the bottom.

Reset by serial number

Enter the serial number and click on the button that you can just see partially off the bottom of the screen.  You may need to scroll to see the button after entering the serial number.

Follow the normal device naming and onboarding.

The bulb will reset and appear as a new device.  From here on you just follow the normal new device procedure.

My bulbs

Philips Hue White A19 2-Pack 60W Dimmable LED Smart Bulbs Works with Alexa, HomeKit & Google Assistant
  • 929001136979
  • 840 lumens
  • 2700K
  • 9.5 watts used


Revision History

Created 2024 03


 

Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS access id and secret key.
Read more