Getting the following error on startup with the current git checkout.

alert: [steward] exception diagnostic=Cannot find module 'xmlhttprequest'
alert: [steward] exception stack=[{"fileName":"module.js","lineNumber":338,"functionName":"Function.Module._resolveFilename","typeName":"Function","methodName":"Module._resolveFilename","columnNumber":15,"native":false},{"fileName":"module.js","lineNumber":280,"functionName":"Function.Module._load","typeName":"Function","methodName":"Module._load","columnNumber":25,"native":false},{"fileName":"module.js","lineNumber":364,"functionName":"Module.require","typeName":"Module","methodName":"require","columnNumber":17,"native":false},{"fileName":"module.js","lineNumber":380,"functionName":"require","typeName":"Object","methodName":null,"columnNumber":17,"native":false},{"fileName":"/home/pi/steward/steward/node_modules/yoctolib/index.js","lineNumber":15,"functionName":"","typeName":"Object","methodName":null,"columnNumber":11,"native":false},{"fileName":"module.js","lineNumber":456,"functionName":"Module._compile","typeName":"Module","methodName":"_compile","columnNumber":26,"native":false},{"fileName":"module.js","lineNumber":474,"functionName":"Object.Module._extensions..js","typeName":"Object","methodName":"Module._extensions..js","columnNumber":10,"native":false},{"fileName":"module.js","lineNumber":356,"functionName":"Module.load","typeName":"Module","methodName":"load","columnNumber":32,"native":false},{"fileName":"module.js","lineNumber":312,"functionName":"Function.Module._load","typeName":"Function","methodName":"Module._load","columnNumber":12,"native":false},{"fileName":"module.js","lineNumber":364,"functionName":"Module.require","typeName":"Module","methodName":"require","columnNumber":17,"native":false}]
uncaught exception: Error: Cannot find module 'xmlhttprequest'

Presuming it needs to be added to package.json?

• adjust home page layout for more than three rows of devices vs. wide range of categories/groups (the "marshall's steward" problem)
• enhance update mechanism to take care of climate and media popovers
• make sure all deviceTypes have a popOver

1. tap on the steward's name
2. select mqtt as the cloud service
3. you will get URL and username to fill-in. there's a third, password.

thanks!

• marshall

…and not just the text field.

try this:

1. start the client and go to a drill down page
2. kill and restart the steward
3. now click the "(t)" to go back. nothing happens

my guess is that when the WSS closes, there should be an alert (not a javascript alert) and the (t) button should result in a reload..

I failed to compile e.g the Weatherstation example on my Debian Wheezy system using avr-gcc 4.7.2 and arduino 1.0.5, it complains about the loopPacket definitions having to be const, seems the notation has changed.

I changed the lines as follows, after which it compiled, now it runs fine and the steward running my white Debian BeagleBone sees it and gets temperature and humidity.

prog_char * const loopPacket1 PROGMEM = "{"path":"/api/v1/thing/reporting","requestID":"";
prog_char * const loopPacket2 PROGMEM = "","things":{"/device/climate/arduino/sensor":{"prototype":{"device":{"name":"Arduino with DHT-22","maker":"Arduino"},"name":true,"status":["present","absent","recent"],"properties":{"temperature":"celsius","humidity":"percentage"}},"instances":[{"name":"Weather Station","status":"present","unit":{"serial":"";
prog_char * const loopPacket3 PROGMEM = "","udn":"195a42b0-ef6b-11e2-99d0-";
prog_char * const loopPacket4 PROGMEM = "-dnt-22"},"info":{"temperature":";
prog_char * const loopPacket5 PROGMEM = ","humidity":";
prog_char * const loopPacket6 PROGMEM = "},"uptime":";
prog_char * const loopPacket7 PROGMEM = "}]}}}";

BTW. I didn't immediately find out which DHT library to use, as there are quite a few. Finally the one from adafruit worked, so maybe this could be noted in the source file?

The new login button and authorisation dialog appears okay when I'm running the steward on the Mac and accessing the D3 client from localhost. However I just updated my steward on the Raspberry Pi and ran it on the Pi in a headless state, accessing it over the network. The login button and auth dialog didn't appear?

There were a couple of—possibly irrelevant—messages on the JS error console.

Thoughts?

i need three days straight to complete updates to the backend; i won't have that for a week or so, so let's avoid confusion in the interim.

what we have so far looks pretty good, we're just waiting on me...

august smart lock - http://www.august.com
lockitron - http://lockitron.com
gohi smart lock - http://www.gojiaccess.com

when i click on a nest or ecobee thermostat, it says "show data for last week"

if i click on that, i get the correct popup. the text leading to the popup is wrong.

also: the text for /device/sensor/arduino/water says "send alert" ... for anything under /device/sensor, there shouldn't be any actions available.

finally, i suggest that the mappings from /device/... to a particular popover be placed in the entries variable in drilldown.js rather than in the carryonFunc() function in popover.js - we really ought to keep everything in one place.

in a subsequent enhancement, i'll request that we allow wildcarding in entries as well...

OWL energy monitor - http://www.theowl.com/index.php
parrot AR.Drone2.0 - http://ardrone2.parrot.com
ecobee smart plug - https://www.ecobee.com/buy/where/
MIO alpha - http://shop.alphaheartrate.com
yoctopuce - http://yoctopuce.com
data sensing lab - http://datasensinglab.com

While testing the support for a z-wave dimmer I noticed an issue with the UI in the d3 client. Whatever the level of the power is set on the device it is shown in the "arc" representation and the number next to it but when we try to make adjustments to the level the starting position of the slider does not reflect the device's current level but always starts at 41%:

The actual device level is properly recorded in the system and it is showing correctly in different sections of the UI as well as in the console itself.

res ipsa loquitur

we are now at the point where folks other than the curators are adding devices to their own copies of the steward. this is a great milestone. however, we need to make the HTML5/D3 client a little more friendly.

as a first step: if there isn't a match in the entries table for a device type, then see if

deviceType.split('/')[2]

is defined in the entries table, e.g., for "/device/climate/foo/bar", look for "climate"

delete: device (if it was created or is no longer discovered)
delete: thing to get rid of a prototype
delete: user

none of these are high priority. implementing the calls is a matter of completeness

As far as I understand it, Github doesn't allow pull requests to the wiki repo, so I thought this the best way to raise this.

The home page Home.md of the wiki references Bonjour, but Wikipedia's lovely URL includes parentheses so the link is broken. I'd replace the link as it is with a partially encoded form:

http://en.wikipedia.org/wiki/Bonjour_%28software%29

i guess i'm a neo-mac guy, because i think that the arrows are reversed on the more-than-five-devices-to-choose-from picker. specifically, when i click on the left arrow, i'd like the choices to scroll to the right; similarly, when i click on the right arrow, i'd like the choices to scroll to the left.

also, could we order the devices in the scroll list? primary sort key=deviceType (e.g., '/device/climate/netatmo/monitor'), and secondary sort key=name (e.g., 'Arden-Arcade')

thanks!

/mtr

If a device has a long name and we try to open the control to make adjustments (turn device on or off or set level) the text for the name of the device overlaps with the on/off button:

This has been bugging me.

• add entry for koubachi cloud
• sort cloud dropdown
• add option to disable LAN-requires-https

when adding an alert to the queue, if the same text is already being displayed or is already in the queue, then just drop it. the user should see it only once...

I never get a QR, only a broken image icon in HTTP. In HTTPS i usually get "unauthorized."

alert: [steward] exception diagnostic=Object # has no method 'url'
alert: [steward] exception stack=[{"fileName":"[as route] (/home/ethomasii/steward/steward/api/api-manage-user.js","lineNumber":106,"functionName":"Object.exports.create","typeName":"Object","methodName":"exports.create","columnNumber":90,"native":false},{"fileName":"/home/ethomasii/steward/steward/routes/route-manage.js","lineNumber":76,"functionName":"","typeName":"WebSocket","methodName":null,"columnNumber":22,"native":false},{"fileName":"events.js","lineNumber":98,"functionName":"WebSocket.EventEmitter.emit","typeName":"WebSocket","methodName":"EventEmitter.emit","columnNumber":17,"native":false},{"fileName":"/home/ethomasii/steward/steward/node_modules/ws/lib/WebSocket.js","lineNumber":647,"functionName":"Receiver.self._receiver.ontext","typeName":"Receiver","methodName":"self._receiver.ontext","columnNumber":10,"native":false},{"fileName":"/home/ethomasii/steward/steward/node_modules/ws/lib/Receiver.js","lineNumber":397,"functionName":"Receiver.opcodes.1.finish","typeName":"Receiver","methodName":"opcodes.1.finish","columnNumber":14,"native":false},{"fileName":"/home/ethomasii/steward/steward/node_modules/ws/lib/Receiver.js","lineNumber":378,"functionName":"Receiver.expectHandler","typeName":"Receiver","methodName":"expectHandler","columnNumber":33,"native":false},{"fileName":"/home/ethomasii/steward/steward/node_modules/ws/lib/Receiver.js","lineNumber":93,"functionName":"Receiver.add","typeName":"Receiver","methodName":"add","columnNumber":24,"native":false},{"fileName":"/home/ethomasii/steward/steward/node_modules/ws/lib/WebSocket.js","lineNumber":627,"functionName":"Socket.firstHandler","typeName":"Socket","methodName":"firstHandler","columnNumber":22,"native":false},{"fileName":"events.js","lineNumber":95,"functionName":"Socket.EventEmitter.emit","typeName":"Socket","methodName":"EventEmitter.emit","columnNumber":17,"native":false},{"fileName":"_stream_readable.js","lineNumber":746,"functionName":"","typeName":"Socket","methodName":null,"columnNumber":14,"native":false}]
uncaught exception: TypeError: Object # has no method 'url'

Investigate modbus and SCADA systems. Mapping TSRP and STP to modbus seems possible, this would give us access to existing SCADA system… it'd be interesting to add the Boeing 747 to the list of supported things.

Look at https://github.com/TooTallNate/node-modbus-stack as a first start.

it may be my imagination, but i think sometimes i see a javascript alert (which locks up the browser until you dismiss it).

if these are there, please remove them…

thanks!

res ipsa loquitur

two cases: different domains (parents, child) or misconfiguration.

also, what to do about unexpected traffic from unrecognized devices?

We seem to have have a broken link on the website,

http://thethingsystem.com/dev/Thing-Sensor-Report-Protocol.html

from

http://thethingsystem.com/dev/Developer.html

does anyone know if this is an isolated incident, or do we have a more general issue?

res ipsa loquitur

• do not require prototype (if it already exists)
• in prototype, do not require name or status, defaulting to true/["present","absent","recent"]
• in prototype, specify default heartbeat rate
• allow heartbeat-only packets

the default client should work through rendezvous and over the LAN. "not hard to do" (-;

notes below --

Design semi-alpha interstitial explaining to people the things they should click on

the steward name - to configure the steward
an icon to drill down to that thing or group of things

i.e. -

"click here to configure the steward"

or

"click here to go back"

after 8 seconds, or there's a click, it should go away.

at that point, we no longer need "TOUCH A THING FOR MORE INFO.", but keep it if you like.

res ipsa loquitur

• make overall design more elastic/responsive (web/mobile/screen)
• indicate scrolling when more than three rows of things are present
• center categories and tags

on a network with more than one AppleTV, the steward detects only one!

Got the api key for the koubachi, entered the user_credentials in the "name" field, app_key in the "appkey" field, and got an alert that the sensor was detected - but that's all. Nothing new appearing in the web interface.

and whenever a device re-joins on startup, scan the tasks to see if there is something to run.

when the console service pushes something that has a level of "alert", the message should be placed in a a 'marquee'

The UI has no notifications if a user tried to make changes but is not authenticated. I think that this should be explained in some sort of a message that would instruct the user to logon first.

I am trying to run it on my home theater pc, which runs Ubuntu on a first generation Intel Atom (x86). I just upgraded to the latest Ubuntu and following the steps for the Raspberry Pi, I tried running the Steward.

However, I get "uncaught exception: Error: dns service error: unknown". Output of the error is below. Full output is at http://pastebin.com/js7ztZyn .

res ipsa loquitur.

• add support for motive, presence, and wearable
• add historical data for climate

When I assign a color using the color picker it only works on the first click - If I want to change the color I have to relaunch the popover

can we change the name field (currently read-only) to an editable field, that does a "perform set { name: '...' }' when it loses focus (unless the field is blank)?

how hard would it be to add a button that forced a login for the client. i believe that unauthenticated access is always read-only...

the /device/media/chromecast/video is very powerful.

the current popup let's you enter a URL to play. i would like to have an option of searching for a youtube video and then clicking on the thumbnail to issue a play command to the chromecast.

danny - could you figure out what's possible in terms of a simple mechanism and then have a conversation with becky as to what the right paradigm is for the popup?

if the current state of a light is OFF and the rgb is [0,0,0] and the user selects ON, then instead of sending ON [0,0,0] send ON [255,255,255]

thanks!

We have a problem when initially logging into the d3 client for steward on the Raspberry Pi. If you go to http://steward.local:8887/client.html to create a user so that you can use https for read/write and the d3 client, it redirects to port 8888 and you get the following error when trying to create a user,

warning: [manage] wss 192.168.1.92 51035 /manage permanent=false, diagnostic=unknown api: /api/v1/user/create/admin, requestID=3, event=route

this procedure works for localhost (aka 127.0.0.1) but not if you're running the steward on a Pi and logging in from the LAN.

• on drilldown
• on index page

res ipsa loquitur

if the API gets an error (or is disconnected, etc.) can we use the alerting mechanism to report this?