So, today is Tuesday, 04.10.2016,
A little tired after sitting up to 4 AM coding last night, more about that later…
-Except the fact that it’s a regular working day, today Google going to announce some things.
And they’re telling us that it’s gonna be big…
Really dont care for several about the rumors out there, except for one thing:
I’ve been sitting on the fence for a long time regarding the amazon echo, due to both my wait for Google Home,
but also due to the incompatibility of geolocation of the echo outside supported countries.
To put it in another way, I’m in no way interested in the weather, traffic, and etc. in the US.
Among other things.
Other reasons are that i already have other things that speak well with each other, my Nest thermostats, Protect’s, and cameras working great with my smartthings.
As we’ve already know, Google owns Nest, so i would guess this will have good communication from the start.
Other reason to point out is that Google already seem to have decided for supporting SmartThings.
Have read several rumors about that, including THIS article from androidpolice.com
For those interested in more about this, you can read more several places, like ArsTechnica .
Some of the codewriting from tonight included a new device handler for my home,
This is a part of my renovation project of my living and dining room.
In which the question was that since I already have a Nest thermostat in my kitchen, it seems a bit overkill to have another one 1 meter from it in the dining room, so how do i control the underfloor heating I’ve mounted.
Which i tried to ask the community about what they thought, but nobody had any solution for it.
Even if i wanted to use the Nest thermostat i would have to make a custom setup, as the load is higher than what the Heat link can safely switch.
So the result was using a Fibaro relay, which can handle the load fine.
But as the dimmers, the original Fibaro device handler type is a generic multichannel z-wave device.
This wouldn’t work well with my rules, that are listening of the Nest thermostat and simply follow that.
So I’ve compiled a new device handler last night, wasn’t suppose to do it, but since i anyway was checking other things on the computer, why not?
-Anyways, the Device Handler can be found on my Git here: FGS-212 (clicky)
NB: As I’ve said, this is something i threw together really quickly, and therefore isn’t finished/polished in any ways yet.
Some things you’ll find if you look in the code is that i used the whole capability and parameter list/configure, as i didn’t bother go through it manually, just threw it in from my repo collection that i had from before.
The ones not supported by the other config codes just do a whole lot a nothing anyways 🙂
Seems to work in its rough shape now, however not sure about pwr monitoring though.
Maybe I’ll check later tonight.
Figured that would be the best way to do it as it is an open solution across almost my whole 1st floor, and kitchen and dining room are next to each other.
From my experience, the sunload and other factors in these two rooms are similar.
Therefore: Kitchen-Nest thermostat, Dining room-Fibaro relay that follows the Nest Thermostat.
And if i can kick myself to do it, i will mount the Nest Thermostat that i have laying in the living room.
In the living room my sunlight conditions are a little bit different (Whole lot a sun, all day), so the sunload sensor of the Nest will come in handy.
Now, lets see what Google have in store for us then 🙂
Okey then, the announcement are over,
Homerun for smartthings by the looks of it 😀
Also, if you watch the introduction video, there’s a sneak peak of the connection with Nest at the end of the video.
Promised integration with Hue, SmartThings, and Nest.
Introduction Video – Not new, but confirmed at this point 🙂