First impressions and ideas

[adocampo]

Just installed the watchapp and started playing with it. So far, I'm in love with it!! Awesome work, @Willow-Systems !!

I have a PTS and my wife a PTR, so the watchapp crashes when exiting detail view... :'( hopefully it can be solved sometime in the future. But I'm so happy at the moment I don't even care.

I have a few suggestions for the app, perhaps some of them are easily doable.

• scroll long text: most of my entities name doesn't fit on the watch screen, so I cannot see what I'm interacting with, I think it would be helpful if those long names can scroll, and extra-useful for those who, like me, if enter into detailed view where we can see the complete name, if we fail the device and go back, the app crashes.
• sort items: there are devices/sensors/etc we interact the most and other almost we don't, but the app shows them in a given order. It would be very useful to let the user choose the order the items are shown, so they don't have to navigate 30 items to know the kitchen's temperature (for example)

Very good job! I'm very impressed!

[Willow-Systems]

Hey! Glad to hear you're finding it useful!

Yeah the crashes upon backing out of certain views is super annoying. It doesn't affect diorite (Pebble 2) which is odd. It's an underlying PebbleJS issue, but hopefully I'll find a fix.

Scroll long text - This should be pretty easy, I'll see what I can do soon

Sort items - Yeah this is the next feature I want to work on. I think having a special 'favourites' section on the home screen would be the best way. I'm conflicted as whether the content of that list should be filled by going into the entity on the watch and doing something to 'favourite' it (like long press etc), or whether you specify a home assistant group to be your favourites, then manage the content of the group through home assistant (i.e. you create a group called 'pebble' in your configuration.yaml and manage it there.

The latter option would be easier to manage if you have loads of entities as you can do it from a computer, plus it would mean the configuration will survive something like reinstallation of the Pebble app, and be synced to all users of your instance. Let me know if you have any thoughts on this.

[adocampo]

I like the idea of groups, but I never used one before and as I'm reading right now, they can become obsoleted at some point. (that "still" could mean they could be unsupported in the future)

New groups cannot support more than one type of entity, so we should have a group for switches, another for lights, another for sensors, and so on... depending on the number of the devices, it could be useful, but if we want to control just a bunch of devices, it would be an annoyance. Besides, new groups toggles all the devices at the same time.

What about accessing a card? I don't even know if it can be possible, but with an entity card it would be easily configurable (even with a GUI), and it can mix any entity just like old groups.

[Willow-Systems]

Hmm. I'll have a think as to what's best in terms of grouping.

Scrolling has been added to the detail view, but this won't help with super long entity names. I'll see what I can do about that. Maybe I'll add an option to overflow into the subtitle instead of showing the state

[jonaseymour]

Nice to see some more commits to this over the last few months. Are there any plans to add OG pebble/Pebble steel compatibility? Sadly they are the only devices I have so can't try this out...

[radudorurus]

Hello. I've tried the app. It is nice from you to put effort on a "defunct" device still very versatile.

Since the entities number may be overwhelming I suggest another approach. I do not know if it is possible.

Create a new user for the watch. Create token. Create a specific dashboard page only for the watch and restrict access to other dashboards/pages for the watch. Create a card or more with the wanted entities to be available on the watch app.

Why I suggest this? The most used entities for me are some lights and the openGate button. Gate button should be accessible very fast on the first page I mean as few clicks as possible