This thread details an ongoing community effort (with Honeywell) to hack EvoHome using the official API. This only refers to communicating with the Evohome server so like a home-brew replacement for the smartphone apps (right?) http://www.wordpress-1219309-4387497...ntrol-remotely
I've also seen people discussing directly talking to the EvoHome devices using stuff like WireShark, RF units. I'm not sure if there is an active community here, or whether they are trying to replace the EvoHome controller or just talk to it?
Maybe there is a 3rd option - a thread grouping the various homebrew efforts would be amazing so people can decide what route to go.
====
My position is that I love the idea of EvoHome but would like more precise control over each room in a non-traditional "turn on at 7, off at 9" way. We have a large house with only two people, and not particularly predictable schedules who will be in the house in which room at which time - other than when we get up in the morning.
It's daft that our bathroom is being heated just because the living room is, when I only want it warm to take a bath at some point in the evening. I work from home so typically my office needs heating 9-5 but sometimes in the evening too.
I love the idea of "scenarios" so I can tell my heating system "I'm going to take a bath". Or "We're going to bed soon". This seems contrary to the normal usage of the controller and app but possible through the API with custom code on top.
BUT - is that needed when the app will(?) let me just override any zone at any time?
My big dilemma is that I am strongly opposed to be locked into the EvoHome server. If internet is down, or your server is, or you decide my product is obsolete or even that the API should be retired or replaced with something totally different. I don't want to be beholden to someone else making decisions - anyone who plays multiplayer games knows the frustration that eventually they'll pull the plug on the server.
Plus, there are privacy issues. It seems an unneeded attack surface I have to send my heating requests to the internet when I'm sitting on the sofa
If EvoHome would just let me talk to the controller from my private WiFi as well as through the web this would be a non-issue. But since they don't/won't... what are the workable options, and how much DIY is involved in each?
I've also seen people discussing directly talking to the EvoHome devices using stuff like WireShark, RF units. I'm not sure if there is an active community here, or whether they are trying to replace the EvoHome controller or just talk to it?
Maybe there is a 3rd option - a thread grouping the various homebrew efforts would be amazing so people can decide what route to go.
====
My position is that I love the idea of EvoHome but would like more precise control over each room in a non-traditional "turn on at 7, off at 9" way. We have a large house with only two people, and not particularly predictable schedules who will be in the house in which room at which time - other than when we get up in the morning.
It's daft that our bathroom is being heated just because the living room is, when I only want it warm to take a bath at some point in the evening. I work from home so typically my office needs heating 9-5 but sometimes in the evening too.
I love the idea of "scenarios" so I can tell my heating system "I'm going to take a bath". Or "We're going to bed soon". This seems contrary to the normal usage of the controller and app but possible through the API with custom code on top.
BUT - is that needed when the app will(?) let me just override any zone at any time?
My big dilemma is that I am strongly opposed to be locked into the EvoHome server. If internet is down, or your server is, or you decide my product is obsolete or even that the API should be retired or replaced with something totally different. I don't want to be beholden to someone else making decisions - anyone who plays multiplayer games knows the frustration that eventually they'll pull the plug on the server.
Plus, there are privacy issues. It seems an unneeded attack surface I have to send my heating requests to the internet when I'm sitting on the sofa
If EvoHome would just let me talk to the controller from my private WiFi as well as through the web this would be a non-issue. But since they don't/won't... what are the workable options, and how much DIY is involved in each?
Comment