Well I found my old Philips hue board that I had soldered my Header pins onto in order to root this thing.
Wasn’t sure if it had a static or dynamic Ip but I just used Zen-map scan of my network to find it’s IP. I didn’t want to break out my UART for serial communication so this was faster in my mind.
I first ran a scan with the [Philips-Hue device] (running/on my WIFI network) and took a screenshot of all my devices.
Then I unplugged the [Philips-Hue device] and rescanned my network taking another screen shot and doing a visual diff on the images. forgot to run a faster scan so this took unnecessarily long time…
And I compared the two lists and I’m guessing even though I didn’t hit save and I closed out zenmap that it was cashed so as a backup I just logged into my router and found my IP-Address of the [Philips-Hue device].
I navigated to this device… I think this is my other Hue Controller thought that has not been rooted.
I unplugged that device and observed the results.
The webpage had been cashed so it persisted even after a refresh but closing the webpage and attempting to access it again produced.
So the search for my rooted Philips Hue continued…
Seriously contemplating breaking out the UART and just talking to it serial but I believe I’ll find it via my router…
Not certain that WIFI is running on this device anymore I plug in the ethernet cable and look in my router again.
Success! I’ve found the elusive [Philips-Hue device]
They appear to be identical screens if you navigate to their ip-addy’s but the logo on this device is broken I noticed… maybe coincidence there. Anyway, that leas me to believe I have to SSH onto this so I will use Putty on this one.
Tried Putty for just SSH setting that should work and no-joy. Figured I’m grasping at straws so I set Zenmap to do a full scan on just this device and see what ports it has open. Listed a bit of ports among which were 80 and 8080.
So pretty much knew I needed to just specify port on my URL with either appending :80 or :8080.
So at this point I’m starting to wonder if I shouldn’t have broken out the UART from the start… But I guess this is good info for collecting purposes.
I’ll try putty specifying port prior attempts via web-browser failed.
Shoot… forgot about 443… lets try it…
Okay so 443 is hosting the web page… I guess good to know. That explains that… I guess 80 and 8080 are Illusive but at this point I think the admin client Is only going to be accessed via Serial connection so I put off breaking out the UART long enough.
https://github.com/bahamas10/hueadm - just a side note lots of good information on controlling the P-Hue in this article.
Reading through this link I didn’t believe it was the resource I used to determine which Pins needed Vcc, Gnd, TX and RX. So, the search continues…
https://forum.archive.openwrt.org/viewtopic.php?id=66346 - Reading through this produced the following bit of information:
1. UART UART is located in J1 and J6 (standard 2,54 mm pitch header), J6 pinout: 1 - GND 4 - RX 5 - TX From <https://forum.archive.openwrt.org/viewtopic.php?id=66346>
I was hoping for a picture of the board because the PCB has small lettering and I wanted to be certain where I was attaching my cables to. So, I continued to look for a picture of the Pins labeled out on the board.
I’m fairly certain I had enabled Wifi on one of these devices but if memory served only certain models are capable or maybe my guides only worked with certain models. One or the other.
I created a schematic that was bad here that I’m leaving out as I didn’t use it for this and it would be misleading.
So, I’ve seen it in 2 places now. 1=GND, 4=RX, 5=TX. Looks like no VCC. Which is convenient because I only had (3)-wires handy without digging.
https://blog.andreibanaru.ro/2018/03/27/philips-hue-2-1-enabling-wifi/ MIght Need Later
When I inspect the board I’m working on and compare it to the above screenshot I notice my header pins are not as expected…
I’m not certain if that was a experiment but I don’t believe I should use the header pins that are soldered on. My solution is the following though.
RX-PURPLE/ORANGE Later becomes Yellow
On the UART we’ve got the following:
1-Green is ground. Easy
4-UART says its RX and on the Phue Board its expecting RX
5 - UART says its TX and on the Phue Board is expecting TX
I’m ready to plug it all up and see if I can talk to it.
So says, my UART is listed as COM6 in Device manager.
Fire up Putty here and take a look I suppose…
We’ll give defaults a try but highly unlikely…
No-joy but was expecting that. I’m just loose’y goosey with those pins so this might be right and I’ve got bad connections at the board. I’m going to check this setting to be certain what the speed should be set to.
Hooked things up got some junk when I hit the keyboard unplugged everything.
Powered on the PHUE device and the UART
Pressing the keyboard produces the above which is good I’m close either my TX/RX are reversed or my Baud Rate is wrong.
Gonna swap Pins
Power down everything…
Swap RX and TX
Well now I don’t get anything going to put them back
Power down everything…
Swap RX and TX
Thinking there’s a setting in addition to Baud going to check.
Or I should use a different UART… Lets try different UART. Cant’ find anything obvious other than Baud right now.
Turns out I fried that UART… So I’ve got a couple others that I’m less confident in…
I inspected the board but it didn’t label the header pins so I couldn’t remember the details on what went into getting this all to work but thankfully I recalled reaching out to Kyle a while back and found the following:
Is your feature request related to a problem? Please describe.**
Light automation support/Ideas with Philips Hue
Describe the solution you’d like
I would like to use mycodo for light schedules with the philips hue lights. Also, could it send an alert - set a light bulb a notification color. Example: temp high alarm - light turns red
I’m pretty excited about this one…
I found this URL https://github.com/bahamas10/hueadm
So I ran:
curl -sL https://deb.nodesource.com/setup_13.x | sudo -E bash -
sudo apt-get install -y nodejs
smguth@mycodo:~ $ sudo apt-get install -y nodejs Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: libfuse2 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libc-ares2 libjs-highlight.js libnode72 nodejs-doc Suggested packages: npm The following NEW packages will be installed: libc-ares2 libjs-highlight.js libnode72 nodejs nodejs-doc 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 10.4 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Get:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libc-ares2 armhf 1.17.1-1+deb11u2 [96.2 kB] Get:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libjs-highlight.js all 9.18.5+dfsg1-1 [397 kB] Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libnode72 armhf 12.22.12~dfsg-1~deb11u4 [7,261 kB] Get:4 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf nodejs armhf 12.22.12~dfsg-1~deb11u4 [148 kB] Get:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf nodejs-doc all 12.22.12~dfsg-1~deb11u4 [2,547 kB] Fetched 10.4 MB in 3s (3,750 kB/s) Selecting previously unselected package libc-ares2:armhf. (Reading database ... 107381 files and directories currently installed.) Preparing to unpack .../libc-ares2_1.17.1-1+deb11u2_armhf.deb ... Unpacking libc-ares2:armhf (1.17.1-1+deb11u2) ... Selecting previously unselected package libjs-highlight.js. Preparing to unpack .../libjs-highlight.js_9.18.5+dfsg1-1_all.deb ... Unpacking libjs-highlight.js (9.18.5+dfsg1-1) ... Selecting previously unselected package libnode72:armhf. Preparing to unpack .../libnode72_12.22.12~dfsg-1~deb11u4_armhf.deb ... Unpacking libnode72:armhf (12.22.12~dfsg-1~deb11u4) ... Selecting previously unselected package nodejs. Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_armhf.deb ... Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ... Selecting previously unselected package nodejs-doc. Preparing to unpack .../nodejs-doc_12.22.12~dfsg-1~deb11u4_all.deb ... Unpacking nodejs-doc (12.22.12~dfsg-1~deb11u4) ... Setting up libc-ares2:armhf (1.17.1-1+deb11u2) ... Setting up libnode72:armhf (12.22.12~dfsg-1~deb11u4) ... Setting up libjs-highlight.js (9.18.5+dfsg1-1) ... Setting up nodejs (12.22.12~dfsg-1~deb11u4) ... update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode Setting up nodejs-doc (12.22.12~dfsg-1~deb11u4) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ...
sudo npm install -g hueadm
sudo npm install -g hueadm
added 41 packages, and audited 243 packages in 20s 4 packages are looking for funding run `npm fund` for details 32 vulnerabilities (1 low, 13 moderate, 11 high, 7 critical) To address issues that do not require attention, run: npm audit fix Some issues need review, and may require choosing a different dependency. Run `npm audit` for details.
sudo apt-get install npm
sudo npm install -g hueadm