Closed wborn closed 3 years ago
I noticed that yesterday ;)
And found out this is one of the little flaws of wanting to build both openhab.org and next.openhab.org off the same main
branch... Currently the deploy previews are made only for openhab.org (for events, blog posts etc) but since it succeeded and simply ignores the add-ons it doesn't find I guess we're good!
Thanks!
Yes it seems to work well with both versions! 🙂
Feel free to suggest additional "featured" bindings, the list is a little outdated. I'd remove "nest" because of the API shutdown, and add maybe "http", perhaps others ("remoteopenhab", 'ipcamera"...? Too bad they don't have logos).
I merged https://github.com/openhab/openhab-docs/pull/1574 and cherry-picked it to stable so the next builds will have the logos.
I'd remove "nest" because of the API shutdown, and add maybe "http", perhaps others ("remoteopenhab", 'ipcamera"...? Too bad they don't have logos).
That's OK with me. I think the Nest Binding is feature-worthy again when my PR for adding support for the new API is merged. :wink:
so the next builds will have the logos.
It seems that all add-ons are considered to provide "supported things" on the main page. The sorting looks a bit odd now the automation add-on images show up first:
These types don't have an all button because there aren't many. If the missing add-ons are featured, they can be more easily discovered.
There's also https://github.com/openhab/openhab-docs/pull/1574 to add images for these add-ons.