not sure since when/which update, I am observing some strange behavior of my OpenHAB on Apple watches:
icons not displayed (yes, I saw this is already discussed in a parallel thread, and pending some action on Apple side)
some (but not all) switches are not showing the correct status. while for some items this works just fine as always, for others it doesn’t and the status is not displayed correctly. It seems (but not sure that is true) this defect is for all my hue bulbs only.
strange enough, when I switch to that “watch” sitemap on an iPhone in the OpenHAB app, the entire sitemap does just what it is supposed to do - including icons showing, and correct status of all switches.
See attached two screenshots for example: the first bulb labelled “Stehlampe” is turned on and at 100% in the iPhone app, but shows as turned off (but still at 100%) on the watch.
I am having the same issue here. Opening the watch sitemap in a browser works all file and perfekt. Opening the watch sitemap with the OpenHAB App on Apple Watch leads to strange behaviors… Icons not showing up, Buttons not working (Switches are working). Display/Sitemap is flickering (disappearing / showing up again). Seems to be reloading all the time. I don’t know.
Same to me. Does anybody have some news about this issues in the meantime?
I have created a comprehensive sitemap for the Apple Watch. When it works, the Watch app is a real added value. Unfortunately, the app rarely works for me.
The sitemap is displayed for a fraction of a second or maybe a second. Then the page disappears, meaning that only a black screen appears briefly on the Apple Watch. And so it continues, with the sitemap and black screen alternating approximately every second.
I have already tried to create a very simple sitemap with only one switch to rule out the possibility that it is due to the rather complex sitemap. However, I experienced exactly the same behavior, flashing every second.
I also uninstalled the Watch app and then reinstalled it, but that didn’t help either.
What is the reason for this? Is the app fundamentally faulty, or am I perhaps doing something wrong?
