Added Multiple Structure and Device support

[fuelxc]

Added models Structure and Device.
Allows for multiples of each and setters can be called on nest/structure and will affect all the children
Do to the new models I added in a flag for initializing structures.

Refactored a bit of the initialization of Nest in order to help this refreshing.

Looking to go get a smoke alarm to so that we can subclass devices into thermostat and smoke alarm. Might consider changing the namespace at that time off of NestThermostat to Nest and changing Nest to Account

[fuelxc]

(tests are included)

[ericboehs]

@stevenpetryk I'd love to see this merged. It needs some love especially with the new changes you've intro'd.

[stevenpetryk]

TODO: make it work with smoke detectors

Is that outside the scope of this gem? I mean, this is the only gem I can find designed for interacting with Nest at all, and it WOULD be nice for it to work with Nest Protect, but the name of the gem is nest_thermostat. Maybe, in the grand scheme of things, it would be better to wrap the Nest API in a separate gem, and then have nest_thermostat and nest_protect be more like plugins for that gem? It would allow for modularity in the even that Nest releases more products.

[ericboehs]

I think we'll make separate gems for that. I plan on getting a nest protect in the next 2-3 months. A core api gem could be good too.

[fuelxc]

i can fix the merge if you guys like and remove the todo. I was planning on getting nest protect as well to implement

[stevenpetryk]

Just FYI, if you're registered as a Nest developer (it's free), you can add a fake device to your account using the Nest Developer Chrome plugin. That's what I've been doing, since I don't actually have a Nest thermostat.

[fuelxc]

Oh nice, cheers forthat

[stevenpetryk]

Also, @ericboehs, this was mentioned in passing by @fuelxc, but I'm a huge fan of changing the namespace to Nest and separating the current Nest class into Structure and Device classes. Perhaps Device could contain code relating to any device (ID, name, IP Address, location, etc.), and Thermostat could be a subclasse of it. This would help greatly with adding support for Nest Protect. Maybe a milestone would be a good idea?

[ericboehs]

That sounds like a great idea. Feel free to add off topic comments in gitter.