nixes / iothublib Goto Github PK

Currently thinking that callbacks aka function pointers might be the best way to go about this.

Good stuff here: http://arduino.stackexchange.com/questions/23063/user-callback-functions

This would be important for any real world deployment, where bugs will be found in this library and people will want to update their devices.

So I'm having trouble defining the class constructor in the way that I would in normal c++ when it requires parameters.

Some clues: http://forum.arduino.cc/index.php?topic=45931.0

Not a bad start: https://github.com/joemcmanus/ESP8266-Firewall

Practical function would be to prevent internet access from ip's that are not on the local subnet.

Read from eeprom into sensor_ids: 57b6ee6696069f5c1384272957b6ee6696069f5c1384272a
Read from eeprom into sensor_ids: 57b6ee6696069f5c1384272a

could probably fix by just reading as one big block into multidimensional array

Seems to only happen when something is routed.

Reset codes provide no help.
Maybe I'm not yielding enough?

Some ideas so far:

• Have a separate array for each type of actor struct and have an actor struct for each type,
• Have the state actually be a json object and the callback function decides what to do with it.
• Do some crazy templating so we can determine type at compile time (but this would allow only actors of the same type)

Specific circumstances:

• If server 404's and only one nodes registration fails continuously. Then the working nodes id will constantly get overridden.
• Clearing of first boot bit when node is not recognised by server and registration succeeded anyway.

if they are not valid, then attempt to obtain new ids

Based on api described here: Nixes/iotHub#24

Fix this by checking if an actor is still valid before committing to a complete boot.
Just do a get to /api/actors/invalid_id if anything but a 200 response unset first boot bit.

If a sleep interval is over 30 seconds, use deep sleep instead.

Use this:
https://github.com/esp8266/Arduino/blob/master/doc/filesystem.md

Currently trying to use aWOT for a nice api router interface but bumping into problems using class state from within callbacks.

Solutions I can think of include, overloads for non-static class methods. Or the addition of an option to pass pointers to internal objects through the route interface. The final option I can think of is the use of global variables to store sensor and actor objects, and the reading of state from within the router callbacks.