I did read over that indeedDigit wrote:I advise you to read a little bit more about the Homey project before judging too quickly, cause some of your statements are incorrect.
For instance, Homey will be based on the Raspberry Pi Compute Module, not on a Raspberry Pi Model B as you might think.
It's even mentioned on their Kickstarter 'Home page', hard to miss I'd say. Compute Module means no SD, but eMMC.

Well that 170k is primarily for getting the device developed further and making it more stable; but indeed as they do have it in their plans it is likely they can resolve this, it can be a tricky thing though as sometimes you might want the redundancy. Eg does a signal received at two receivers mean it was sent twice (thus repeated, eg twice pressing the same button); or just a duplicate of the same transmission?Digit wrote:And what's the problem with receiving the same signals in multiple places? I don't see the problem.
I'm sure they'll fix this 'problem' with EUR 170000 in their pocket.
But for that they are using the Google Voice recognition stuff; I don't think they will develop anything of their own there. Doing their own voice solution would require them to hire quite a few more people who actually understand that stuff, and there are not many folks out there that do.Digit wrote:Personally, I'm more interested in a "private / local" speech recognition solution
The Jasper system already demonstrates that, and that where folks who spent a lot of time on it.
>, combined with the best TTS there is - no matter whether it falls under PA or not.
> Who cares about what I let my computer say to me (the News, weather forecast, yes master, 20 unread emails, ... ) ?[/quote]
For me it is not the fact that it is something that somebody will read along (that was just a side-note as they make a claim about it); it is more to the fact that I don't let any of my sensors talk to the Internet; they have no business doing so and the VLAN they live in does not have routing towards/from the Internet.
More importantly the depending on an external service is bad: Internet down, and you can't turn on your lights the comfy way you are used to.
I cannot disagree, that is absolutely awesomeDigit wrote:The reason I backed Homey is (for me, and I think for the majority) that voice is the ultimate way of interacting with a HA system.

Yep, I've read that, very good writeup, but there you also resorted to using the Google API in the end as the self-contained system is just not good enough (and unfortunately I don't know any alternatives to it either...)Digit wrote:"Jasper" is funny but not good enough for me - TTS is very bad. But Jasper was the trigger for me to revisit Voice Control once more:
http://blog.hekkers.net/2014/04/16/home ... e-control/
I understand that sentimentDigit wrote:And I've seen some "early work" on Homey (before it had that name) on Tweakers.net and was flabbergasted with how well it performed.
So when Homey appeared on Kickstarter the only thing I could do was to support their effort to make Homey work.
Nothing more, nothing less. I just hope they succeed in creating an awesome product, open enough to embed in our own systems.

I wish them good luck too; it does not seem to be the tool for my job though.
Btw, as you already have a RFXLAN and now that new RFXtrx thingy, what part of the 433mhz will you let handle by the Homey, or will you make the RFXLANs sent their output to the Homey so that it can do all the centralized things it needs?
The advantage of having multiple 433mhz receivers is ofcourse that one can spread them throughout a house and avoid distance/wall issues. for reception.