151 lines
11 KiB
XML
151 lines
11 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<feed xmlns="http://www.w3.org/2005/Atom">
|
|
|
|
<title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title>
|
|
<link href="https://home-assistant.io/blog/categories/public-service-announcement/atom.xml" rel="self"/>
|
|
<link href="https://home-assistant.io/"/>
|
|
<updated>2018-03-05T20:44:53+00:00</updated>
|
|
<id>https://home-assistant.io/</id>
|
|
<author>
|
|
<name><![CDATA[Home Assistant]]></name>
|
|
|
|
</author>
|
|
<generator uri="http://octopress.org/">Octopress</generator>
|
|
|
|
|
|
<entry>
|
|
<title type="html"><![CDATA[Clarification about Emulated Hue]]></title>
|
|
<link href="https://home-assistant.io/blog/2018/01/21/clarification-emulated-hue/"/>
|
|
<updated>2018-01-21T01:00:00+00:00</updated>
|
|
<id>https://home-assistant.io/blog/2018/01/21/clarification-emulated-hue</id>
|
|
<content type="html"><![CDATA[There are some misconceptions floating around about the future of the Emulated Hue component and I would like to set the record straight. **The Emulated Hue component is not going to be removed nor will we ever remove any functionality from Home Assistant to push you to support the Home Assistant project by subscribing to the Community Support Package.**
|
|
|
|
The reason people are concerned about the future of the Emulated Hue component is because of a poor choice of words in a deprecation message. This message was [introduced a year ago][pr2] when we deprecated the config option `type: alexa` for the Emulated Hue component:
|
|
|
|
> Alexa type is deprecated and will be removed in a future version
|
|
|
|
That config option should never have been called `type: alexa` but instead have been called `mode: legacy`. If you think about it, why would emulating something even have different modes it emulates based on the consumer? That means that one of the two emulation modes is incorrect.
|
|
|
|
The old implementation was not 100% correct. It was correct enough to work with Alexa (the original target) but not with Google Home. When fixing Emulated Hue we added `type: alexa` to re-enable the old implementation so that people did not have to go through the trouble to re-add their Alexa devices. The option was deprecated to indicate that we would remove the incorrect emulation in the future. However, we forgot about actually following through with that.
|
|
|
|
The mistake we made was calling the correct mode `google_home` although it had nothing to do with Google Home. It confused people and they kept adding `type: alexa` to their configuration, triggering the deprecation warning.
|
|
|
|
The warning will be updated starting Home Assistant 0.62 and will also include a link to this blog post.
|
|
|
|
More info:
|
|
|
|
- To read about what was incorrect in the first version of Emulated Hue, take a look at the PR fixing it: [Re-org emulated_hue and fix google home][pr1].
|
|
- Read the [documentation on how to configure Emulated Hue][eh-conf]
|
|
|
|
[pr1]: https://github.com/home-assistant/home-assistant/pull/4708
|
|
[pr2]: https://github.com/home-assistant/home-assistant/pull/5549
|
|
[eh-conf]: https://home-assistant.io/components/emulated_hue/#configuration
|
|
]]></content>
|
|
</entry>
|
|
|
|
<entry>
|
|
<title type="html"><![CDATA[[Update: fixed] A frank and serious warning about X]]></title>
|
|
<link href="https://home-assistant.io/blog/2017/06/20/things-you-should-know-about-senic-covi/"/>
|
|
<updated>2017-06-20T01:04:05+00:00</updated>
|
|
<id>https://home-assistant.io/blog/2017/06/20/things-you-should-know-about-senic-covi</id>
|
|
<content type="html"><![CDATA[**Update June 21:** Senic has removed our name from their materials and have [issued an apology][apology]. We wish them best of luck with the launch of COVI.
|
|
|
|
**Update June 28:** Removed the brand name from the title to reduce the search ranking.
|
|
|
|
*Original post:*
|
|
|
|
<!--more-->
|
|
<p class='note'>
|
|
TL;DR: We are not affiliated with Senic or their COVI product. We will not support their users and you will get a subpar Home Assistant experience by using their product. **Furthermore, we cannot guarantee stability or security if you use Senic products.**
|
|
</p>
|
|
|
|
Recently Home Assistant has been made aware of a product by [Senic] that will be launching later today on [Kickstarter][kickstarter] ([screenshot][ks-backup]). Senic is not new in the IoT business, we have had support for their first product ([Nuimo]) since last September. Their new product, COVI, uses Home Assistant as its core home automation codebase. This is great, that is what open source is all about. However, they also use our name and logo in their Kickstarter, with the press and in their [developer documentation] ([screenshot][docs-backup]) to give the appearance of being affiliated with Home Assistant, against our wishes. Which is not great, at all.
|
|
|
|
Take some of the following quotes from their Kickstarter campaign:
|
|
|
|
> COVI is built on an open source platform. The Senic team, along with outside developers, contributes to this platform to create the integrations for COVI.
|
|
|
|
> With COVI, we have built upon an open platform called Home Assistant that anyone can contribute to alongside our engineers and the Home Assistant community.
|
|
|
|
Although those quotes are technically correct, they are very misleading. The Senic team contributes only to their own platform, they have not contributed to Home Assistant, its integrations or related projects. We did receive [1 contribution][netdisco-contrib] from them for [Netdisco], our network discovery package. It included a memory leak and required us to publish [a hotfix release][hotfix] for the 0.39 series. Their contribution has since been reverted. A third party contributor had contributed support for their Nuimo controller.
|
|
|
|
Here is a quote that their CEO Tobias Eichenwald gave [to Forbes]:
|
|
|
|
> Unlike many larger companies who build closed automation platforms, COVI is built on an open source platform called Home Assistant that includes 500+ contributors. This allows COVI to be integrated into any ecosystem or platform with an open API.
|
|
|
|
They reached out to us on April 7 ([screenshot][email-backup]). We replied on April 11 and told them they should not use our name as we do not want to be affiliated with them because we do not want to support their users. After that one e-mail we had never heard from them again until Forbes accidentally published an article about it before the Kickstarter launched. We did not get any chance to give feedback on their Kickstarter campaign content and they went ahead and used our name and logo without authorization or permission.
|
|
|
|
If you want an open source and constantly evolving product, get yourself a $35 Raspberry Pi, install our hub [Hass.io] for free and buy yourself some cheap and reliable [IKEA Trådfri lights][tradfri] to get yourself a basic home automation setup. If you want a $250 talking lamp, go buy the COVI. Just know that we are not affiliated with Senic, we will not support their users and you will get a subpar Home Assistant experience by using their product. **Furthermore, we cannot guarantee stability or security if you use Senic products.**
|
|
|
|
Senic, we know that this is probably not what you wanted to wake up to on the first day of your Kickstarter but you left us no choice. Please reach out to us to help make this right. **We will always do everything in our power to protect the best interests of the Home Assistant community, <span style='text-decoration: underline;'>our</span> 500+ contributors and 250,000+ users.** If we don't hear from you by Wednesday, June 21st, we will be forced to consider further actions.
|
|
|
|
Sincerely,
|
|
|
|
**Paulus Schoutsen**<br>
|
|
Founder, Home Assistant
|
|
|
|
**Robbie Trencheny**<br>
|
|
Core Developer, Home Assistant
|
|
|
|
[Senic]: https://www.senic.com/en/
|
|
[kickstarter]: https://www.kickstarter.com/projects/802159142/1793705123?token=03dc08b4#
|
|
[ks-backup]: /images/blog/2017-06-senic-covi/covi-kickstarter-screenshot.png
|
|
[email-backup]: /images/blog/2017-06-senic-covi/email-senic.png
|
|
[docs-backup]: /images/blog/2017-06-senic-covi/senic-docs-screenshot.png
|
|
[Netdisco]: https://github.com/home-assistant/netdisco
|
|
[netdisco-contrib]: https://github.com/home-assistant/netdisco/pull/94
|
|
[hotfix]: /blog/2017/02/25/config-panel-and-state-restoration/#release-0392---march-1
|
|
[Hass.io]: /hassio/
|
|
[to Forbes]: https://webcache.googleusercontent.com/search?q=cache:https://www.forbes.com/sites/paularmstrongtech/2017/06/19/covi-is-about-to-make-some-general-electric-execs-very-unhappy/
|
|
[tradfri]: /blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/
|
|
[Nuimo]: /components/nuimo_controller/
|
|
[developer documentation]: http://blog.senic.com/posts/the-senic-hub-a-brief-software-overview
|
|
[apology]: https://medium.com/@senic/an-open-letter-to-home-assistant-5ccb53ccf722
|
|
]]></content>
|
|
</entry>
|
|
|
|
<entry>
|
|
<title type="html"><![CDATA[[Update: decision reversed!] Philips Hue blocks 3rd party lights]]></title>
|
|
<link href="https://home-assistant.io/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/"/>
|
|
<updated>2015-12-12T18:44:00+00:00</updated>
|
|
<id>https://home-assistant.io/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs</id>
|
|
<content type="html"><![CDATA[**Update Dec 16**: Great news! Philips has decided to [reverse their decision][philips-reverse] and is working on a software update to allow 3rd party light bulbs again.
|
|
|
|
<p class='img'>
|
|
<img src='/images/blog/2015-12-philips-hue-3rd-party/philips-hue-reversed-faq.png'>
|
|
Philips Hue FAQ entries regarding reversing the decision.
|
|
</p>
|
|
|
|
*Original post:*
|
|
|
|
<!--more-->
|
|
Philips Hue was one of the first to get smart lights accepted by the mainstream. Their Zigbee-based hub is rock solid, never crashes, great API and worked with other Zigbee light bulbs too. They are a bit expensive but the platform was worth every penny, till now.
|
|
|
|
Yesterday a thread on [/r/homeautomation][reddit-hue] published that Philips Hue now blocks all but their own bulbs and those of "friends of Hue". I have been able to confirm this in the [Philips Hue FAQ][philips-hue-faq] (Update Dec 14: they have removed the entries - [mirror here][philips-hue-faq-mirror]):
|
|
|
|
<p class='img'>
|
|
<img src='/images/blog/2015-12-philips-hue-3rd-party/philips-hue-faq.png'>
|
|
Philips Hue FAQ entries regarding 3rd party light bulbs.
|
|
</p>
|
|
|
|
This means that after you update your Hue bridge to the latest version:
|
|
|
|
- As of now, you can still use your existing paired 3rd party light bulbs
|
|
- You cannot pair new 3rd party light bulbs
|
|
- You're out of luck if for some reason you have to pair existing 3rd party light bulbs again
|
|
- Resetting your hub will force pairing of all your bulbs again
|
|
|
|
If you own a Philips Hue hub and are using 3rd party light bulbs, make sure you do not upgrade your hub if you want to be able to pair new 3rd party lightbulbs. But do realize that you are sitting on a ticking time bomb.
|
|
|
|
I have read, but have been unable to confirm it, that resetting your hub will force a software upgrade. So beware of that too.
|
|
|
|
I will no longer suggest people to buy into the Philips Hue ecosystem.
|
|
|
|
[philips-reverse]: http://www.developers.meethue.com/documentation/friends-hue-update
|
|
[reddit-hue]: https://www.reddit.com/r/homeautomation/comments/3wet8h/fyi_the_hue_hub_is_now_blocking_third_party/
|
|
[philips-hue-faq]: http://www2.meethue.com/en-us/support/search/?q=Another+brand
|
|
[philips-hue-faq-mirror]: /images/blog/2015-12-philips-hue-3rd-party/mirror.png
|
|
]]></content>
|
|
</entry>
|
|
|
|
</feed>
|