This all seems a bit strange. No press releases or mention of this. On Khimo's site, there's only one mention of this as being a successor to the BLGW. There are no explanations in the FAQ as to how to migrate from the BLGW to this new product. Khimo refers to NL devices but never mentions ML devices. The screen shots of the web interface for configuring the product look identical to that of the BLGW. The "upgrade" to allow 3rd party integration requires a direct payment to Khimo. The BeoLiving app looks identical to the BeoLink 2 app. However, the BeoLink 2 app says that it's copyrighted by Bang & Olufsen -- yet the BeoLiving app says that it's owned by Khimo. It looks like an odd breakdown in partnership between B&O and Khimo. Don't get me started on all of the typos in the documentation on the Khimo site!

Khimo are the developers behind the BeoLink Gateway and have written the user guides etc for programming it. BeoLiving looks like the next iteration of the BeoLink Gateway however hasn't been formally announced / released by B&O.

Perhaps in the past the arrangement was for B&O to have exclusivity over the product but they have now moved the operations and support for home automation over to Khimo and given them branding rights in the new arrangement?

There's also a new app 'BeoLiving' by the looks of it on the app store under Khimo's developer account; https://itunes.apple.com/US/app/id1417970502#?platform=ipad

It looks much the same as the BeoLink app

An alexa skill has also been produced by Khimo; https://www.amazon.co.uk/BeoLiving-Intelligence-skill-by-Khimo/dp/B079VQB18J

Confusing there's no announcement from B&O

My dealer stated that the Khimo-hub wasn't released by B&O yet. So that's an explanation for lack of announcement from B&O. Maybe they wait for the BLGW stock to be depleted?

By the looks of it it features more or less the same software as the BLGW.

Since the NL/ML-converter has been phased out as well, and the BLGW shares its hardware, they needed new hardware to keep offering their integration line.

I now notice a document on Khimo's site that explains the differences between BLGW and BLI. It seems that the big difference is that BLI does not support ML. There is no ML socket. If you have ML products, you must use a Beolink Converter. Also, Beo4 and BeoRemote One commands are not supported. You can migrate your BLGW configuration file over to the BLI, but you will orphan any macro commands pertaining to ML devices. A new feature is the ability to create Groups for the purpose of multiroom sound distribution.

I don't see the BLI to be for everyone -- particularly anyone with ML devices. I certainly hope that the BLGW will still be supported with updates and new features alongside the BLI.

Any news here - new user experiences?

Anyone using the Beoliving Intelligence with a NL/ML Converter?

MM

chucky wrote:

Hello future update.....

Seriously if you do not own a gateway yet, people will buy it, otherwise I would not even consider before they have updated it. How can it be so difficult to get some camera”s in an app? There are a million other systems that do not have problems with these basic things. I even bought a doorbird, and yes I get a picture, if I am lucky, and yes all is fully wired with cat 7. An Echo Show at 20% cost can even do that.

No zwave suppport, reallly? Let us live the Hue dream. Z wave is more stable and switches are. wired. I have both and Zwave is much better. Lutron also works really nice, but needs a lot of wiring, still working on rs232.

Hello chucky, I'm Ivan of the Khimo team, this is our new BeoWorld forum account where we will be available for support issues, requests, etc.

Just wanted to let you know that the latest update for the BeoLiving Intelligence adds support for all ONVIF protocol cameras, it is now really easy to add them and you can do it directly through the app or on the web setup page. We are also working on improving remote access to cameras, this feature will be available soon.

What specific zwave system do you wish we supported? We take our customers demands into account when defining which systems to develop drivers for!