I have openhab running as my home automation system, which allows me to control my lights and in-house ventilation system. And I have setup some nice rules to automate as much as possible, now I want to update my WLC-1000 cameras settings through openhab.
I'm using my hue sensor in openhab and really like them, I was looking for some nice teardown pictures of the hue motion sensor, but could only find the Hue dimmer switcch dissection & Hue tap Dissection Since I'm pretty curious what's inside, and how they get this good batterylife I will dissassemble one of my hue motion sensors in the name of science to see what's in there, I hope I can help someone else out with these. I'll try to compile a list of the items I find on the board, if you have any additions please let me know :) - Atmega M2564RFR2-ZU - 4mb serial flash 25fu406c - Some type of Pir motionsensor -
For my project where I control my remote via pnps I want to create a low power sensor which will be able to send humidity & temperature data to my openhab server which is running mosquitto Since I have some esp8266 chips laying around, this would be great to setup as a wifi mqtt sensor with the dht22, which will periodically (every 10 minutes) send new sensor data to my mqtt broker. A quick video how to get a basic breadboard setup: I will need it to be pretty energy efficient, so whenever the esp is done sending data, it will go into deepsleep for 10 minutes, and then wakeup and send again...
When creating a webapplication or API it's important to test how well your site will work under heavy load, it's easier to prevent any problems beforehand, compared to doing it when you find out your server is getting swamped with requests.
Update, I have a new philips babycam, and rooted it again, so I added some more info. This is an older post, and after having contacted philips, they told me they had received a report of this issue months prior to my report. In the new firmware these problems don't exist anymore, this doesn't mean that the b120n is flaweless, because when you reset the babycam it reverts back to the old firmware, and you can root it. I wanted to try rooting my B120N cam, and tried to follow Paul Prices Owning Philips In.Sight IP Cameras But unfortunately Philips decided to close all interesting ports in the firmware version my cam was running. I did find a way to gain root access, and I wanted to add a recording of the process so you can try it yourself.. I setup my linux box as 'router' with mitmproxy and a hotspot, connecting my ethernet port and directing traffic trough hotspot -> mitmproxy -> internet In short the steps you need to do:
- Install mitmproxy on your pc / notebook (plenty of good tutorials available online), to be able to capture traffic and alter responses
- Setup a hotspot, where you will connect your phone and camera
- connect your phone, run the insight app, and configure your cam / scan the qrcode
- Now your camera will connect to the wifi, once the insight app asks you if you want to ipgrade press i in mitmproxy and set the filter to .* to capture all traffic and halt on every request
- click yes on the upgrade prompt in the insight app
- press 'a' key to allow the requests per line, untill you reach the upgrade_fw.sh line (don't press a on that line, we want to modify this request)
- hit enter on the upgrade_fw.sh and press 'e' to edit the request
- there will be an option to edit the url (I think it's 'u') then point the request url to 'http://yoururl.com/upgrade_fw.sh) where you set your own shellscript and ssh_config gile) and press enter, and hit 'a' to allow the request to complete.
- Your now have rootaccess to your camera. below you can find a sample upgrade_fw.sh and sshd_config you can use to complete the rooting.
I recently found this tutorial to convert the HC-SR501 PIR Motion sensor, to allow it to run on 3.3V, so I thought I would give it a try, to use it with my whisper node, and make it count the amount of people passing the sensor, trying to make it run on a coincell battery.
I was looking for a good way to group logs from different webapplications into one managable place, without too much configuration work on the different webservers, since some run on shared hosting, and some have different setups. I came across Paper Trail App A hosted log management tool, which gives you the ability to aggegrate logs from different places into one location, and here you can filter and group different webservers together, and search the log history.