-
-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for more customization for device controls entries #3140
Comments
You can control the subtitle and the grouping of these tiles by a setting. It uses data of the semantic model (https://www.openhab.org/docs/tutorial/model.html#semantic-model). IMO this metadata should be enough to configure the tiles you'd like.
Edit: These groups are only visible when adding new tiles, not afterwards. Therefore I'm not sure if a second setting is useful. |
Can you post a screenshot of that? |
Sure, sorry for having you wait. The former is my Google Home device controls dashboard; the middle one is the "add controls" screen for openHAB beta (from F-Droid); the latter is what I get if I long-press the TV item in the Google Home controls (which is currently the most complex openHAB equipment I configured for Google Home). I must say that the Google-based solution is still far from what I'd consider to be ideal, but it's fully functional. I can swipe on any dimmable device to change the brightness/volume/speed, tap to toggle the power, long press to open a view with more controls for that device. The openHAB controls are all over the place, the items with an okay name you see are groups with a type. But for instance if I add the light to the controls I can only toggle it, not change the brightness. I would at the very least like to be able to pair a Switch and a Dimmer into a single tile, then ideally also a sitemap that is displayed on long press. |
Maybe my model isn't configured properly though, here's a screenshot to give you an idea of how I structured it: I then have some additional non-semantic items for things that need extra hacks, such as this one that bundles the air purifier switch and fan speed dimmer into a single item that accepts on/off/speed setting. |
That does work currently. Which item type has the item you add as tile?
It has to be discussed how the sitemap should be linked to that widget.
Can you click on "Scooter smart plug" and make a screenshot of the right side of the screen? |
I'm currently using the setup required for SpecialColorLight for Google Assistant, therefore
I could change it to a different setup if needed, the current one is as it is because of the GA binding requirements, but it would be nice to have common conventions whenever possible. EDIT: I actually double checked and the groups don't show up to be added as tiles. So I had actually added the switch.
Here you go. No group type is set. |
Ok, now I got your feature request. This seems like a bigger task as it requires some kind of Sitemap rendering based on Items in a group (compared to Widgets like in normal Sitemaps). |
We already have links to Sitemap subpages (NFC tags), so re-use them for the device control. Closes openhab#3140 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
We already have links to Sitemap subpages (NFC tags), so re-use them for the device control. Closes openhab#3140 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
The UI command item in Main UI uses the same URL for `navigate:` than Main UI itself. Therefore use the same URLs as the browser uses. When a Basic UI URL is detected, open it in Sitemap, otherwise in Main UI Webview. Closes openhab#3140 Closes openhab#3529 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
The UI command item in Main UI uses the same URL for `navigate:` than Main UI itself. Therefore use the same URLs as the browser uses. When a Basic UI URL is detected, open it in Sitemap, otherwise in Main UI Webview. Closes openhab#3140 Closes openhab#3529 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
The UI command item in Main UI uses the same URL for `navigate:` than Main UI itself. Therefore use the same URLs as the browser uses. When a Basic UI URL is detected, open it in Sitemap, otherwise in Main UI Webview. Closes openhab#3140 Closes openhab#3529 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
The UI command item in Main UI uses the same URL for `navigate:` than Main UI itself. Therefore use the same URLs as the browser uses. When a Basic UI URL is detected, open it in Sitemap, otherwise in Main UI Webview. If no `link_to_more` is set, default to a list of members for groups. Closes openhab#3140 Closes openhab#3529 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
The UI command item in Main UI uses the same URL for `navigate:` than Main UI itself. Therefore use the same URLs as the browser uses. When a Basic UI URL is detected, open it in Sitemap, otherwise in Main UI Webview. If no `link_to_more` is set, default to a list of members for groups. Closes #3140 Closes #3529 Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
Closes #2382. Refs openhab/openhab-android#3140. Adds Android app's link_to_more metadata to the well-known namespaces, therefore also adds an editing page for it. --------- Also-by: mueller-ma <mueller-ma@users.noreply.github.com> Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
Is your feature request related to a problem? Please describe.
I find the device controls quite inflexible and inconvenient for most use cases.
A custom name can't be applied; my items are configured in groups such as:
So I can't simply add the "Power" item cause I'd have no idea of what's being toggled
Things can't be grouped; I'd like the control for lights to be swipable (to control the brightness) and tappable (to toggle it); at the current stage I can only add two controls, and tapping the brightness one would turn it off by setting it to zero (losing memory of the previous brightness setting)
Describe the solution you'd like
I think it'd be really useful to have a new metadata type similar to that for Google Assistant that allows to:
I'm okay with having creating a few proxy items if necessary to match the controls behavior, and/or with adding additional groups to match the semantics of the controls.
Describe alternatives you've considered
The alternative I considered is going through Google Home, and that's what I'm currently doing, though that's not ideal since I'd rather talk to openHAB directly, for performance and privacy reasons.
The text was updated successfully, but these errors were encountered: