is anyone developing an OH/OH2 app for an an iWatch?
I see there are opensource MQTT bridges between Apple Homekit and OH2. I don’t feel creating a dependency with vendor provided middleware (Homekit) is the most robust and vendor agnostic approach to talking to OH2.
IOS on iWatch needs to talk directly with the server running OH2 over wifi, not via HomeKit. Do others agree with the approach?
Or perhaps you think I should “invest” in a HomeKit hub and bridge it to OH2 via MQTT?
I’m an ~<intermediate coder for main stream platforms, but never developed for an iOS platform. Is anyone interested in forming a group to discuss how OH2 sitemap could be rendered on a iWatch and how this technically could be achieved?
I also don’t know if the Apple iWatch/iOS developer guidelines will permit the iWatch to communicate with an external service on non standard TCP port. Maybe it’s deemed a security risk?
On first glance, it appears a wrapper or browser type app would be best approach (the same approach as currently implemented on iOS Phone and iPad. Basically an empty shell of an app that takes a couple of configuration parameters:
OH server IP or DNS address (not sure how to do this when there is no keyboard on an iWatch)
OH Port number
User id and Password (if required)
On first launch, choose default sitemap.
When the iOS iWatch app opens it renders the sitemap in a format suitable to the small screen format.
Maybe the configuration gets done on the iPhone and gets synced to the iWatch shell application. This would mitigate the need for data entry on the iWatch interface.
happy to discuss.