HSZigbee Now In Beta

[MrMxyzptlk]

Yes, you are correct, Phillips only pulled the support for 1 version...everyone screamed and they immediately reverted in the next build.

[w.vuyk]

I would rather say that the Osram bulbs did NOT*work at some point (since Philips pulled the support).
Osram Lightify*have been working again since Philips realized the mistake and reversed the decision. That was one year ago: Dec 9th 2015.

The hue API documentation provides the full documentation of the API for the hue system.
The API is versatile enough to have more than 450 third party apps available for the Hue.

Aeklo,

There needs to be a clarification added to this

Connecting Osram to Philips Hue is only working for the EU version of Osram Lightify, not for the US version. This is caused by Osram as they are implementing a newer version of the Zigbee (ZLL) protocol (v3)
And rumours are that Osram might also pull the connection to Philips Hue for EU versions for this version as well sometime soon.
No word yet from Philips on this newer version of the protocol, so I do not know if/when Philips is planning to change. They were part of the development of this newer version.

Thanks,

Wim

[aeklo]

The Hue hub is expensive and its a closed system. Currently, the Osram bulbs do not work with it (they did at one point). Osram is dedicated to support anything that supports the LightLink Zigbee spec so its very open. Many more devices are coming for it. That is why we choose it. Low cost and open, its a good place to start. If we can find a good direct solution, we will offer that. There really isn't anything viable out there yet that works under .Net. Of course, if there is, please let us know!

I would rather say that the Osram bulbs did NOT*work at some point (since Philips pulled the support).
Osram Lightify*have been working again since Philips realized the mistake and reversed the decision. That was one year ago: Dec 9th 2015.

The hue API documentation provides the full documentation of the API for the hue system.
The API is versatile enough to have more than 450 third party apps available for the Hue.

Edit:*Seems that the Lightify/Osram support is only valid for*EU versions.

[w.vuyk]

The Hue hub is expensive and its a closed system. Currently, the Osram bulbs do not work with it (they did at one point). Osram is dedicated to support anything that supports the LightLink Zigbee spec so its very open. Many more devices are coming for it. That is why we choose it. Low cost and open, its a good place to start. If we can find a good direct solution, we will offer that. There really isn't anything viable out there yet that works under .Net. Of course, if there is, please let us know!

Rich,

Like jlrichard was saying, it should not be named as HSZigbee. The plugin is not connecting with the zigbee protocol, but to IP and as such not able to 'talk' Zigbee. The Zwave plugin is actually performing the Zwave protocol, so there the name is not confusing users.

This plugin is depending on a branded hub (Osram) and not on protocol. For clarity I would expect the name to point to the brand.

Once you get to be able to address the protocol directly through USB etc, you would need to replace/rewrite the plugin anyway, so why not use a clear name now?

Wim

[jlrichar]

The Hue hub is expensive and its a closed system. Currently, the Osram bulbs do not work with it (they did at one point). Osram is dedicated to support anything that supports the LightLink Zigbee spec so its very open. Many more devices are coming for it. That is why we choose it. Low cost and open, its a good place to start. If we can find a good direct solution, we will offer that. There really isn't anything viable out there yet that works under .Net. Of course, if there is, please let us know!

Hue hub is $60, Osram is $30. Not a huge difference. The GE link bulbs definitely work with the hue hub. I use them all the time. Those are an extremely good value because of their build quality/price. Not sure I'll try the osram bulbs as they seem rather expensive comparatively.

At any rate, glad you made this plugin.

[blake]

The Lightify PRO gateway appears to have a direct API that does not rely on the cloud; https://eu.lightify-api.org/home-ui/...T)_EN_2016.pdf

Just need to import some gateways for us to purchase from you in the US

[rjh]

The Hue hub is expensive and its a closed system. Currently, the Osram bulbs do not work with it (they did at one point). Osram is dedicated to support anything that supports the LightLink Zigbee spec so its very open. Many more devices are coming for it. That is why we choose it. Low cost and open, its a good place to start. If we can find a good direct solution, we will offer that. There really isn't anything viable out there yet that works under .Net. Of course, if there is, please let us know!

I sorta like that you guys made this plugin. Initially I was disappointed you spent valuable time and resources replicating something that is already done. Then I thought more about what you did.

I am not sure you are aware that the Hue bridge works with the bulbs you list, and so does the Jowihue plugin? They do. So its been possible to do anything you mention here, and a lot more, using Zigbee, for a long time. I, and others, have mentioned this a few times in these Zigbee threads.

So why then, as a Hue/JowiHue user do I like that homeseer made this Zigbee plugin?

Because you added support for another companies' hub to Homeseer. In an HST plugin.

I do think plugin is not named correctly though. This plugin should be called the Osram Lightify plugin. I think it is a little confusing to call it a Zigbee plugin, unless you plan on supporting other hubs/dongles that use Zigbee with this plugin. Really this would be confusing for end users that don't even realize when Zigbee is actually being used--Hue for example. It makes sense for Z-wave since people set out to buy Zwave stuff since it mostly all works together. And z-wave stuff is not only labeled on the box as such, it is marked as such. That same scenario will definitely not be the case with this plugin and Zigbee. Whereas calling it the Osram Lightify plugin makes perfect sense. You have the Osram app, it tells you what works and doesn't. At no point is Zigbee mentioned, on the box, in the app, or in the marketing material.

Homeseer actually already works with a lot of cloud hardware. Here are some hub like things I can think of and their current HS interface status:

• Wink--Only via IFTTT
• Smartthings--Only via IFTTT
• Hue--JowiHue--Excellent support
• Harmony Hub--Rien Plugin--Recent access to official API
• Alexa--Excellent HST integration
• Nest--Spud plugin
• Google Home--Only via IFTTT
• MS surface Home--None
• HomeKit--Recently pulled
• Sonos--Not cloud, but interfaces to cloud music--well supported by Sonos plugin
• Neatatmo--Supported by two (Ultra) plugins, one for weather, the other for Camera/presence
• Chaimberlain Garage Door gateway--Supported by King Fetty Plugin

Notice that the plugins are named after the HW device they support, not the transport technology.

It would be nice if Homeseer worked directly with all of these hubs, or next best thing, directly with the corresponding cloud API, rather than through IFTTT.

Please consider changing the name of this plugin to Osram Lightify. In this one case it might be good you had your head in the clouds.

[rmiles7721]

I agree about the name as well. I use several zigbee devices with HS but no Lightify hardware. Got all excited about the plugin until I realized this.

[TechFan]

I haven't seen the list of supported devices yet, but it seems a more specific name would be more accurate.

[jgwinner]

This plugin should be called the Osram Lightify plugin.

That makes a lot of sense to me. (Good post, just wanted to quote the relevant part).

== John ==

[jlrichar]

Wrong name?

We did; See my post above. Unfortunately, the company we were working with could not provide a .dll or sample .NET code to use with this project. Many many engineering hours went into this with unreliable results.

I sorta like that you guys made this plugin. Initially I was disappointed you spent valuable time and resources replicating something that is already done. Then I thought more about what you did.

I am not sure you are aware that the Hue bridge works with the bulbs you list, and so does the Jowihue plugin? They do. So its been possible to do anything you mention here, and a lot more, using Zigbee, for a long time. I, and others, have mentioned this a few times in these Zigbee threads.

So why then, as a Hue/JowiHue user do I like that homeseer made this Zigbee plugin?

Because you added support for another companies' hub to Homeseer. In an HST plugin.

I do think plugin is not named correctly though. This plugin should be called the Osram Lightify plugin. I think it is a little confusing to call it a Zigbee plugin, unless you plan on supporting other hubs/dongles that use Zigbee with this plugin. Really this would be confusing for end users that don't even realize when Zigbee is actually being used--Hue for example. It makes sense for Z-wave since people set out to buy Zwave stuff since it mostly all works together. And z-wave stuff is not only labeled on the box as such, it is marked as such. That same scenario will definitely not be the case with this plugin and Zigbee. Whereas calling it the Osram Lightify plugin makes perfect sense. You have the Osram app, it tells you what works and doesn't. At no point is Zigbee mentioned, on the box, in the app, or in the marketing material.

Homeseer actually already works with a lot of cloud hardware. Here are some hub like things I can think of and their current HS interface status:

• Wink--Only via IFTTT
• Smartthings--Only via IFTTT
• Hue--JowiHue--Excellent support
• Harmony Hub--Rien Plugin--Recent access to official API
• Alexa--Excellent HST integration
• Nest--Spud plugin
• Google Home--Only via IFTTT
• MS surface Home--None
• HomeKit--Recently pulled
• Sonos--Not cloud, but interfaces to cloud music--well supported by Sonos plugin
• Neatatmo--Supported by two (Ultra) plugins, one for weather, the other for Camera/presence
• Chaimberlain Garage Door gateway--Supported by King Fetty Plugin

Notice that the plugins are named after the HW device they support, not the transport technology.

It would be nice if Homeseer worked directly with all of these hubs, or next best thing, directly with the corresponding cloud API, rather than through IFTTT.

Please consider changing the name of this plugin to Osram Lightify. In this one case it might be good you had your head in the clouds.

[sirmeili]

Yes. . .too bad it is cloud dependant. . .seems like this could lend itself to some of the same lag issues discovered when trying to tie together with Wink hub via IFTTT.

Let us know what you find best for the gateway.

If this is cloud dependent, it's a non starter for me

Sent from my XT1585 using Tapatalk

[TechFan]

Ordering a gateway. . .will look forward to the list.

[macromark]

So, does using the Lightify gateway/cloud limit Zigbee support to only lighting devices then?

We have more products to test. Once that's done, we'll put up a list.

[TechFan]

So, does using the Lightify gateway/cloud limit Zigbee support to only lighting devices then?