Enable some debug output when a custom tweet is sent

Version 2.6.0.249

JSON support.

To request the current Stoker status in JSON format, "GET" the page at "http://stoker_ip/stoker.json". The format is:

        { "stoker" : {
            "sensors" :
                [
                    { "id" : id, "name" : name, "al" : al, "ta" : ta, "th" : th, "tl" : tl, "tc" : tc, "blower" : blower_id },
                    ...
                ],

            "blowers" :
                [
                    { "id" : id, "name" : name, "on": on },
                    ...
                ]
            }
        }

The idea is this:

• 1 global Stoker object
• Stoker object contains two other objects
• First object is called "sensors"
  • "sensors" object is an array of sensor entries
  • Each sensor entry has:
    • id - 16 character serial number
    • name - User defined name
    • al - alarm, which can be 0, 1, 2
      • 0 - no alarms
      • 1 - Target
      • 2 - Fire hi/low
    • ta - Target temperature
    • th - Fire high
    • tl - Fire low
    • tc - Current temp
    • blower - 16 character serial number of the blower, if any. If no blower, then the value is null
• The second object is called "blowers"
  • "blowers" is an array of blower entries
  • Each blower entry has:
    • id - 16 character name
    • name - User defined name
    • on - 0 for blower off, 1 for blower on

To "POST" data, the JSON body should look exactly like the Stoker object above. The only difference is that the "POST" handler will ignore the read-only attributes.

For the sensor entries, the POST handler will ignore the tc field. For blower entries, the POST handler will ignore the on field.

If the POST succeeds, then the HTTP status code of 200 will be returned with nothing in the HTTP body. If the POST fails, status code of 400 will be returned and the body wil contain this JSON message:

        { "stoker_response" : "Failed" }

Version 2.6.0.226

When POSTing, use http://stoker_ip_address/stoker.Json_Handler

There's one more small development project I'm working on and that's to bring JSON support for web access.

After that, I think it's best to stop adding new stuff and fix the broken stuff. There are two major concerns I would like to address.

• StokerLog losing connection
• Bug where the fan remains on right after the unit is started.

Create a read-only page. The settings are at ro.html. This new web page will allow Stoker to serve up a non-modifiable web page. When you enable the "read-only" mode, the regular web page will have all of its input boxes disabled. When you enable read-only mode, you will need to supply a password. To disable read-only mode, uncheck the read-only box and input the proper password. If you forget the password, then you will have to clear out the database; this will mean you will lose all of your custom settings.

Enable DNS and gateway fields for static IP addresses. To use these settings properly, you must first modify the DNS, gateway, and mask settings, and then at the end set the static IP address.

Fix alarm strings on Twitter.

Clean up output on telnet so that StokerLog will not lose connection.

Version 2.6.0.221

More info for Twitter support on the Stoker.
Tweets will only work if you are using DHCP on the Stoker. The reason is there are bugs in using static IP addresses where the user cannot specify the gateway IP or the DNS IP addresses. Until this is fixed, the only way to set these values is to use DHCP.

Minor updates.
Add a new field for one-time custom tweets at twitter.html
No need reboot after twitter settings changes.
Fix serial number display on web page.
2.6.0.200

For those of you who have enabled Twitter on the Stoker, please note that:

Enable FTP server with static IP
2.6.0.194

More fixes for StokerLog
2.6.0.193

Revert web page to maintain compatibility with StokerLog. Twitter settings have now been moved to twitter.html.

So, let's say your Stoker IP address is 192.168.1.10. And usually, you access the web page with "http://192.168.1.10". Now, the Twitter settings are located at "http://192.168.1.10/twitter.html"
2.6.0.191

Minor Twitter changes
2.6.0.188

Enable Twitter support.

This will allow the Stoker to send tweets to any specified Twitter account. There will be a tweet generated every time an alarm condition is set/cleared and there will be a tweet at regular intervals. The frequency of these periodic updates is user defined.

Warning: Please be extremely careful using this. There are several security pitfalls that the user needs to be aware of. Basically, the entire process is vulnerable. Yikes! I'm no security expert, but these are some thoughts the user should be aware of.

1. The user will need to enter the Twitter account name and password into the Stoker webpage. The connection between the web browser and the Stoker during the operation is NOT secure. This means the account name and password can be sniffed out while submitting the info to the Stoker.
   
   If this is of concern, make sure there is a direct wired Ethernet connection between the Stoker and the computer - no wireless, no switches, no hubs, no routers.
   
   
2. The Stoker stores this information in non-volatile memory. The Stoker software will never publish this information. But Mr. Evil Hacker-man could potentially break into your house, steal your Stoker, unsolder the non-volatile memory, disassemble the executable, and then extract the info from the chip. But man, that's a lot of work.
   
   
3. The Stoker uses Basic Authentication to send the tweet. This effectively means the Stoker sends the account name and password in raw text direct to Twitter.com. Please see the Twitter API docs regarding basic authentication.
   
   Since this request uses the Internet, this means the account name and password are vulnerable to anyone sniffing the traffic.

Not exactly a happy set of thoughts. Kinda sucks to be the party-pooper, but there are some things you can do to minimize the risk.

1. Create a new Twitter account just for the Stoker.
2. Try to limit any type of personal info on the Stoker profile.
3. Create a totally new password for the account. Use any strong password generator site to create the password. Here's a Google search.

Usage: After upgrading, with your new Twitter account strong password in hand, open up the Stoker webpage, and click on the check box labeled "Show Twitter options".

• Updates - this enables/disables the Twitter support.
• Username/password - info for the new Twitter account.
• Update interval in minutes - number of minutes inbetween periodic tweets
• Message header - a few words at the beginning of each tweet
• Click save changes
• On the "Update successful" page, click on the "Back" link and wait for the new page.
• Once the new page is served up, reboot the Stoker.

Update for new commands.
2.6.0.99
Socket Test

Updates to the socket command set. Added CMD_ID_HTTP_PORT, CMD_ID_DUTY_CYCLE_MIN_MAX, and CMD_ID_DUTY_CYCLE_TIME_SLICE.

Fix output to be backwards compatible with StokerLog. 2.6.0.67

The previous example had some problems on certain computers and so I have reverted from Winsock2 back to Winsock 1.1 and that seems to work. Here is the new example: socket_test_wsock1.1.zip

Found a divide-by-zero problem. This problem causes abrupt termination on the socket whenever the CMD_ID_DUMP_ALL command is issued while a switch is plugged in.

Here's the fix: 2.6.0.63

Updates to socket control syntax.

WARNING: Still in alpha.

Here is the initial alpha release: 2.6.0.57

Here is some code written to test it: Example

Here's a preliminary look at the socket control syntax.

I'm rewriting all the socket control stuff. It was originally kinda hokey.