rtl_433 mhz

One of the most difficult problems I’ve attempted to resolve in the last few years, is how to capture and record (into mysql database) data received from 433mhz sensors..

rtl_433 -M utc -F json -G

{“time” : “2019-09-25 19:11:54”, “model” : “Acurite tower sensor”, “id” : 2766, “sensor_id” : 2766, “channel” : “A”, “temperature_C” : 22.700, “humidity” : 44, “battery_low” : 0}

{“time” : “2019-09-25 19:12:01”, “model” : “Acurite Lightning 6045M”, “id” : 253, “channel” : “A”, “temperature_F” : 72.100, “humidity” : 41, “strike_count” : 26, “storm_dist” : 27, “active” : 1, “rfi” : 0, “ussb1” : 0, “battery” : “OK”, “exception” : 0, “raw_msg” : “c0fd6fa9d12d9a1b88”}

{“time” : “2019-09-25 19:12:04”, “model” : “Smoke detector GS 558”, “id” : 8078, “unit” : 14, “learn” : 0, “code” : “63f1ce”}

Trying to parse and collect the data using LiveCode has proven to be difficult. First problem with rtl receiver, is it isn’t seen as a com port, or other readable device. It is seen as its own terminal device. I’ve tried piping, didn’t work. Basically everything I’ve tried, hasn’t worked.

The best advice I have received to is send data out to flat file, then read the file. Which basically mean lots of file activity and parsing. Unsure if I am willing to do that for what should be a simple task. That would cause a great deal of read/write activity on the SD drives and possibly wear out the drive faster.

Heard of a new program that outputs the data to files specific to the device id, trying to find it. Will keep everyone informed.

LiveCode Project

Got a job writing a program to track a client’s, client’s. Can’t go into do much detail. But it is reawakened the joy of Programming in LiveCode again. LiveCode is up to version 9 now, haven’t done any major projects in it since version 6. SO, lots of new features and changes. Having to relearn a few things. This project will be using SQLite, which I haven’t used in a LONG time, but so far going fairly well.

UPDATE: You can see what the finish project looks like on LittleSoftwareBarn.com, Projects >> Boat tracker. Project took under two weeks to complete.

IP Power 9258

Have a need, fill a need.

After losing contact with one of our remote servers, we decided we needed a way to do a hard reboot. We call it ‘cycle the power’. Turn the power off, wait 30 seconds and then power the unit back on. We have had great luck with servers running months even years without issue. Unless they are overloaded or overheated.

Checking eBay for over the counter power controllers, we found the IP Power 9258. Got our first one for less than $70, but most cost between $80 to $120. After looking at programming options and being a MAC Shop we figured it was doable. In less the a week we completed IPPOWER.app. Very small, very simple controller for the IP Power.

First you’ll need the IP Power’s IP number. Using an old PC we first configured ours DHCP, using the included IPEdit. (Read their instructions, which aren’t very well translated to english). We then used LanScan to find the device by its Mac Address.

After you have the IP Power’s IP number, just startup IPPower app, it will ask for the IP Number, administration name and password. The defaults are admin, 12345678.

You can now control the IP Power using keys 1 – 4, clicking on button 1 – 4 or sending “/Applications/IPPower.app/Contents/MacOS/IPPower 4” (4 being the outlet to cycle the power on).

We have also setup iChat to support cycling the power. See the attached AppleScript. Configure iChat to execute the script on message received. The script will look for “outlet1” – “outlet4” as a message. And cycle the power with prompting.

For Apple Mac: ippowerminicontroller

Keyboard Tester

Nice perk of my current job is that we are allowed to spend time creating time saving programs. Within reason!

After getting an unusual number of reports of broken keyboards we decided we needed a quick easy way to test keyboards. Using mostly Apple iMacs, that is what we wrote the program for. BUT it works pretty good on windows as well (numerical keypad has issues though, but useable).

Spent less than a day creating the DIY Keyboard Tester using LiveCode.

Keyboard Tester Mac: diykeyboardtestermac

Keyboard Tester Windows: diykeyboardtesterwin-exe