Web Things about architecture

[fabaff]

First step for an integration is done: https://github.com/fabaff/webthing-ws

[dgomes]

I'm interested in following this topic

[zabuldon]

I'm in :)

[arbreng]

This looks very interesting!

Another potential benefit I see, especially with something like Hass.IO, is the ability to pull out the proprietary IoT stacks from the homeassistant core and make them addons. The addons host up a WebThings server on top of ZWave, Zigbee, etc and talk to hass over websockets.

This lets us:

• As @balloob says, Standardize and stabilize these APIs, to focus on a better user experience instead of IoT details
• Version and distribute these components independent of the main homeassistant release
• Slim down the Hass.IO builds and image size by quite a bit

[balloob]

Just an update on this, we have introduced a device registry that holds entities. This will better map to the data model as set forth by Web Things.

[joshgc]

Has there been any progress on this? I have some custom sensors being served via an RPi and the WebThings works great, but there appears to be no way to connect it to HomeAssistant. Still

[rzr]

Thanks I see it has moved upstream to:

https://github.com/home-assistant-ecosystem/webthing-ws

What's missing now ?

[frenck]

This architecture issue is old, stale, and possibly obsolete. Things changed a lot over the years. Additionally, we have been moving to discussions for these architectural discussions.

For that reason, I'm going to close this issue.

../Frenck