PiBox » Iron Man

Ordered 433Mhz xmit/receive units from Amazon, along with BN-Link RF outlets.
I already have Arduino's I can use, including ESP8266-01's.

• Debian pkg: 1.8.13 - apt get arduino
• Upstream: 2.3.2

• Official
  • Releases
  • 1.1
• Guide (3rd Party Article)
  • Official Getting Started
• Video

ESP8266 Guide (from Ironman lightsw project, only valid for 1.x releases).

This should be tested first with the Arduino boards, then ported to the esp8266 if possible. A bank of esp8266 boards for a collection of RF outlets would be preferrable to a bank of Arduino's, although some of them are pretty small too.

Step 1: Get the runtime protoboard back up and running. This is not the programmer, it's the other board.

It's got a ton of wires hanging on it and it doesn't quite look like the picture on the Wiki. I need to design it with an HLK-PM03 step down power supply (110v to 3.3v) to use mains power. And then mains have to pass through to the socket. I should update the Fritzing diagram for that.

The sensor attempts to pair correctly but to the wrong device. It's trying to connect to the Media System (on .60) instead of the Ironman Systsem (on .67).

.........imiot setup:
Connected to: MuseN
IP address  : 192.168.101.199
Password    : 6953af02c3
Resetting GPIO0.
HTTP server started
Device registration not found.
Scheduling timer events.
...............................Sent multicast announcement: 0
.........Registering with url = http://192.168.101.60:8165/pair/iot/1df53702-0f21-11f0-b4a6-b827eba2c19a
Return code from http.POST: -1

1. Media System should not have registration enabled.
2. Ironman may not have registration enabled and running in piboxd.
3. Media System doesn't have the web server running to respond to the POST from the sensor.

I'll shutdown Media System and retry just to see if Ironman responds at all. Then I need to check piboxd builds to make sure Ironman gets registration while Media System does not.
Once I get Ironman responding to the multicast request I can check on the web server that should be responding to the POST from the sensor.

Ironman is not responding to multicast.

.........imiot setup:
Connected to: MuseN
IP address  : 192.168.101.199
Password    : 6953af02c3
Resetting GPIO0.
HTTP server started
Device registration not found.
Scheduling timer events.
...............................Sent multicast announcement: 0
................................Sent multicast announcement: 1
................................Sent multicast announcement: 2
................................Sent multicast announcement: 3
................................Sent multicast announcement: 4

Verified that sensor and Ironman are attempting registration - ironman gets multicast request and sends back uuid. sensor attempts to connect to ironman with the POST to complete registration. But this fails because the imrest server isn't running because I can no longer compile nodejs with Buildroot.

I've already ported imrest to mongoose (see RM #1006). But I think I missed porting imrest to an initscript. The old startup script, runserver.sh, just starts nodejs, not the new imrest.

Also, when I run imrest manually, the registration fails with 401 on the sensor:

Connected to: MuseN
IP address  : 192.168.101.199
Password    : 6953af02c3
Resetting GPIO0.
HTTP server started
Device registration not found.
Scheduling timer events.
....................Sent multicast announcement: 0
................................Sent multicast announcement: 1
................................Sent multicast announcement: 2
................................Sent multicast announcement: 3
................................Sent multicast announcement: 4
................................Sent multicast announcement: 5
................................Sent multicast announcement: 6
.............Registering with url = http://192.168.101.67:8165/pair/iot/3b0577f2-0f40-11f0-a89a-b827eb3c7aaf
Return code from http.POST: 401

This is likely because imrest's API was updated so pwrctrl (re: imlightsw) must be updated to match.

The runserver.sh shouldn't be needed. It's actually quite messy. There should be an init script for the php server (imwww) and one for the IoT server (imrest). Both should start at boot time. Both should be running mongoose. And both should be able to test for state files within the C code wrapping mongoose. Doing this will simplify Ironman startup and reduce clutter in the /home/httpd/* directories by removing the useless nodejs stuff (which still needs to be removed) and extra php files (but might leave the templates).

1. imlightsw repo
   1. Port pwrctrl to use new API (RM #1195)
   2. Port pwremote to use new API (RM #1195)
2. imrest
   1. Remove src/old directory. (RM #1197)
   2. Add default runtime directory for imrest (re: make it start in /home/httpd/imrest) (RM #1198)
   3. Add init script for imrest (RM #1199)
   4. Have imrest check for gpio state to allow registrations. (RM #1200)
   5. After this is done, I can retest imrest with pwrctrl sensor.
3. metabuild
   1. Remove imgpio package from ironman since mongoose can check gpio itself (so shell scripts don't need to do it anymore). (RM #1203)
4. imwww
   1. Remove imrest directory from imwww repo (RM #1196)
   2. Port imwww to mongoose (RM #1204)
   3. Make init script run mongoose-ported imwww (RM #1205)

1203, 1204 and 1205 can be worked on after this issue is complete.

Registration appears to complete now.

frontEnd[imrest.c:266] INFO Inbound method: POST
handlePost[imrest.c:157] INFO uri: */pair/iot/547c1774-1236-11f0-84e6-b827eb3c7aaf*
handlePost[imrest.c:158] INFO PAIR_IOT: */pair/iot*
handlePost[imrest.c:162] INFO body: {"type":"light_switch","description":"Toggle_light_switch","state":0}
handlePost[imrest.c:180] INFO Match PAIR_IOT: /pair/iot
devicePairIot[pair.c:123] INFO Entered.
gpioRead[utils.c:583] INFO GPIO value for pin 4: 1
Ev/sys/class/gpio/gpio4/value
devicePairIot[pair.c:136] INFO Registration mode enabled.  Handing pair request from 192.168.101.199
handle_uuid[pair.c:55] INFO handle_uuid has been called: stampDir: /home/httpd/imrest/ironman/iot/, json = {"type":"light_swi
tch","description":"Toggle_light_switch","state":0}
handle_uuid[pair.c:66] INFO Registration file: /home/httpd/imrest/ironman/iot//192.168.101.199
handle_uuid[pair.c:89] INFO Wrote registration stamp file: /home/httpd/imrest/ironman/iot//192.168.101.199

But using that registration fails on imrest.

frontEnd[imrest.c:266] INFO Inbound method: GET
handleGet[imrest.c:122] INFO Requesting IP: 127.0.0.1
deviceGetDevices[device.c:307] INFO Entered.
deviceGetDevices[device.c:316] INFO GetDevices request from local system.
deviceGetDevices[device.c:328] INFO iotDir: /home/httpd/imrest/ironman/iot/
deviceGetDevices[device.c:340] INFO Requesting check of 192.168.101.199
utilsLoadUUID[utils.c:130] INFO iotDir: /home/httpd/imrest/ironman/iot/
utilsLoadUUID[utils.c:133] INFO iot file: /home/httpd/imrest/ironman/iot/192.168.101.199
utilsLoadUUID[utils.c:144] INFO File data: {"type":"light_switch","description":"Toggle_light_switch","state":0}
deviceGetDevices[device.c:344] ERROR Failed check of 192.168.101.199

pwrctrl is not adding the UUID to the registration JSON packet because it's in the URL. However, when imrest checks the packet later when pwrctrl tries to reconnect it doesn't find the uuid (in deviceGetDevices()) in the saved JSON data so it rejects the attempt to reconnect.

I can either remove the check imrest (because the filename IS the UUID) or I can add the UUID to the JSON packet during pwrctrl's registration.