domi04151309 / homeapp Goto Github PK

Describe the solution you'd like

It would be nice if the (SimpleHomeApi)[https://github.com/Domi04151309/HomeApp/wiki/SimpleHome-API] wiki page would contain instructions about mDNS discovery, and how to configure avahi-daemon. (Mentioned in commit 6d492b8).

It'd be also nice there was an explanation how to setup UPnP announcements for own SimpleHomeApi services yourself.

The Shelly page should mention the devices known to work (and that others should work, too):

• Shelly 1 with temperature+humidity sensor
• Shelly Plug S
• Shelly Plus 1

The page should also mention that autodiscovery works with shelly devices.

In the screenshot of Hue bridge sliders for various variable inputs are shown.
In the wiki there seems to be only the possibility to toggle a command for the SimpleHome API.

I think it would be great if a slider input could be used in this case too. For instance by adding a range attribute in the list of commands.

Description

I started the app, added my Hue bridge, tap the button to associate. It has correctly synced all the rooms and lights, but there are none of the scenes that are registered. I know the scenes are correctly registered in the bridge because I use the Hue app on Android and hueadm on Linux.

• Android version: LineageOS 16.1, microg
• Home App version: 1.7.2
• Installation source: F-Droid

Thank you for the software, thus said :)

Describe the solution you'd like

When using Shelly devices, each power socket and light switch has its own device. When you have more than 5 of them, the list in HomeApp gets pretty crowded and it's not easy to see if switch A belongs to the same room as socket B.

It would be nice if I could group devices into "rooms", and have all of them visible on the main screen without having to open them.

Living room
- Stair light
- TV light
- DVD player socket
Kitchen
- Radio
- Main light

Maybe opening/closing (expanding) would be nice, too.

Describe the solution you'd like

Google Play store still has version 1.7.2: https://play.google.com/store/apps/details?id=io.github.domi04151309.home

It would be nice if version 1.9.0 was published there.

(1.9.0 is on f-droid already: https://f-droid.org/en/packages/io.github.domi04151309.home/)

Description
The socket device icon in blue looks ugly on a white background.
The original one from #58 looked better in my eyes.

I presume you did that change because of white/dark themes.
Could there be an inverted one for the dark theme instead of using the blue one?

I use several Yeelight devices, they are widely used devices. The proprietary application does not seem very privacy-friendly... It would be really great if they were supported by this application!

There are several repos available on github, maybe some can be useful
https://github.com/topics/yeelight

Description

1. open GitHub page.
2. Look for About (desktop, top right hand side)
3. click link https://domi04151309.github.io/Android/HomeApp - get error

Controll shelly plus also over bluetooth. E.g. switch on/off

Just wanted to start by saying this app works really well!
Would it be possible to be able to allow for edit the widget icons? Something like the ability to select from a preset amount of colors (to keep things minimal) would be great. This would be nice to help me differentiate between different light colors/scenes on the Hue lights.

Thank you!

Offer adding a widget for an available scene.

Of course, this issue has to solved first #20

Shelly relay devices (Shelly Plus 1, Shelly 1, see https://shelly.cloud/ ) are installed in power sockets and light switches and can be used without any cloud services.
They have a publicly documented API at https://shelly-api-docs.shelly.cloud/gen1/ (Shelly 1) and https://shelly-api-docs.shelly.cloud/gen2/ (Shelly Plus 1).

It would be nice if HomeApp would support their API.

I would like to support that by buying you some test devices. Please contact [email protected] if you are interested and let me know your postal address.

Service Discovery

Shelly devices announce themselves via MDNS (Bonjour/Zeroconf) and not SSDP. One can use the linux tool "avahi-browse" to find them.

• v1 devices "announce a HTTP service on port 80 via mDNS. Hostname is always in the form of shelly<model>-XXXXXXXXXXXX": https://shelly-api-docs.shelly.cloud/gen1/#mdns-discovery
• v2 devices: https://shelly-api-docs.shelly.cloud/gen2/Overview/CommonDeviceTraits#mdns

Gen2 shellies advertise themselves the Multicast Domain Name System (mDNS), also known as Bonjour. Devices advertise two types of services:

• _http._tcp - a web server serving on port 80. This service is also advertised for Gen1 shellies
• _shelly._tcp - service instance specific to Gen2 Shelly devices."

$ avahi-browse --cache --no-db-lookup --parsable --all
+;wlp1s0;IPv4;ShellyPlus1-A8032ABD2342;_http._tcp;local
+;wlp1s0;IPv4;ShellyPlus1-A8032ABD2343;_http._tcp;local
+;wlp1s0;IPv4;ShellyPlus1-A8032ABE2344;_http._tcp;local
+;wlp1s0;IPv4;shellyplus1-a8032abd2342;_shelly._tcp;local
+;wlp1s0;IPv4;shellyplus1-a8032abd2343;_shelly._tcp;local
+;wlp1s0;IPv4;shellyplus1-a8032abe2344;_shelly._tcp;local

Android natively supports mDNS discovery also with Kotlin: https://developer.android.com/training/connect-devices-wirelessly/nsd#discover

Device information

All devices (v1 and v2) have a public (unprotected) JSON information file at /shelly:

v1

{
    "type": "SHSW-1",
    "mac": "483FDA82687A",
    "auth": false,
    "fw": "20211109-124958/v1.11.7-g682a0db",
    "longid": 1,
    "num_outputs": 1
}

https://shelly-api-docs.shelly.cloud/gen1/#shelly

v2

$ curl -s shelly1.home.cweiske.de/shelly|jq .
{
  "id": "shellyplus1-a8032abd1bcc",
  "mac": "A8032ABD2342",
  "model": "SNSW-001X16EU",
  "gen": 2,
  "fw_id": "20210921-202758/0.8.1-g52de872",
  "ver": "0.8.1",
  "app": "Plus1",
  "auth_en": false,
  "auth_domain": null
}

The "gen" key is only available on v2 devices.

https://shelly-api-docs.shelly.cloud/gen2/Overview/CommonServices/Shelly#http-endpoint-shelly

Number of switches

v1

The JSON object in GET /status has a "relays" array property: https://shelly-api-docs.shelly.cloud/gen1/#shelly1-1pm-status

{
    "relays": [
        {
            "ison": false,
            "has_timer": false,
            "timer_started": 0,
            "timer_duration": 0,
            "timer_remaining": 0,
            "overpower": false,
            "source": "http"
        }
    ],
    ...
}

v2

We have to look for "switch:*" keys in the device configuration object for v2-devices:
https://shelly-api-docs.shelly.cloud/gen2/Overview/CommonServices/Shelly#shellygetconfig

$ curl -s shelly1.home.cweiske.de/rpc/Shelly.GetConfig | jq .
{
  ...
  "switch:0": {
    "id": 0,
    "name": "wohnzimmer_1",
    "in_mode": "follow",
    "initial_state": "restore_last",
    "auto_on": false,
    "auto_on_delay": 60,
    "auto_off": false,
    "auto_off_delay": 60
  },
  ...
}

Detecting on/off device state

v1 returns the ison state in the /status route as well.

Both v1 and v2 devices have the /relay/0 URL, which tells us if it is switched on or off via ison:

$ curl -s shelly1.home.cweiske.de/relay/0|jq .
{
  "ison": true,
  "has_timer": false,
  "timer_started_at": 0,
  "timer_duration": 0,
  "timer_remaining": 0,
  "source": "http"
}

v2 also returns all states in /rpc/Shelly.GetStatus:

$ http -p b shelly1.home.cweiske.de/rpc/Shelly.GetStatus
{
   ...
    "switch:0": {
        "id": 0,
        "output": true,
        "source": "http",
        "temperature": {
            "tC": 58.8,
            "tF": 137.8
        }
    },
    ...
}

Switching on/off

Both v1 and v2 devices have the /relay/0 URL, which allows turning the device on, off or toggling the device state with a GET parameter:

$ curl http://shelly1.home.cweiske.de/relay/0?turn=on
$ curl http://shelly1.home.cweiske.de/relay/0?turn=off
$ curl http://shelly1.home.cweiske.de/relay/0?turn=toggle

• v1: https://shelly-api-docs.shelly.cloud/gen1/#shelly1-1pm-relay-0
• v2: https://shelly-api-docs.shelly.cloud/gen2/Components/FunctionalComponents/Switch#http-endpoint-relayid

Note: Some devices have more that one relay. See above for detecting the number and names of switches.

Temperature sensors

v1

It's possible to attach a temperature sensor to a Shelly 1 device. /status gives us the values:

{
    ...
    "ext_sensors": {
        "temperature_unit": "C"
    },
    "ext_temperature": {
        "0": {
            "hwID": "0300",
            "tC": 23,
            "tF": 73.4
        }
    },
    "ext_humidity": {
        "0": {
            "hwID": "0300",
            "hum": 52.3
        }
    },
    ...
}

Authentication

v1

https://shelly-api-docs.shelly.cloud/gen1/#common-http-api

All resources except for /shelly will require Basic HTTP authentication when it is enabled

v2

https://shelly-api-docs.shelly.cloud/gen2/Overview/CommonDeviceTraits#authentication

Communication through HTTP and Websocket channels is secured by a digest authentication mechanism using the SHA256 hmac algorithm as defined in RFC7616.
When enabled, all communication is protected except:

• the RPC method Shelly.GetDeviceInfo
• the HTTP endpoint /shelly

Description

Dear developer! In the process of using, I found a bug in layout / display. As shown in the figure, in the first page, the lower part of the text in the red box is blocked, so you can only see “Your Dxxxx”. It may be an adaptation problem.
App version is 1.7.2, my mobile phone is Google nexus 6, screen resolution setting is 1920*1080, font size and display size are the largest! ! !, Android system is 8.0.
The above is a description of the problem. The overall experience of the software is good. You can see that the design is very attentive. Thank you very much for the efforts of the developers all the time. I hope to receive a reply.
Thank you!

Additional information

• Android version: _System Settings > About > Android 8.0
• Home App version: _Settings > About > 1.7.2
• Installation source: F-Droid

Describe the solution you'd like

Support for TP-link devices

Description

Recommend
https://github.com/Domi04151309/HomeApp/wiki/Hue-API-%28v1%29 be updated to note that HomeApp needs groups and will control groups of lights.

There is no edit option so I can't do this myself :-(

I'd like to be able to fire (execute) a command from my android home screen.

Typically I'm looking for a way to toggle a switch without having to:

• open Home app
• select the corresponding device in the devices list
• click on the "switch" action

If I could see the response as in Home app it would be perfect !

context

• plug with switch flashed with Tasmota

It would be nice if there was an official release on f-droid with shelly support.

Is something missing for a release in your eyes?

• #31
• #27
• #64

Open Hab integration

It woud be great to be able to usw this beautiful app as a Frontend for OpenHab. I am not shure if there is already a workaround for this.

Currently, if there are no registered devices, a single button is shown with the text "No devices found". In think this button could be used to help a user to add a first device.

I'm having this problem the 10th time now after resetting my git checkout --hard for #64 , so I post this as a bug.

When trying to build HomeApp with Android Studio 2020.3.1 I get an error:

Build file '/home/cweiske/dev/tools/HomeApp/app/build.gradle' line: 1

A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.android.internal.application'.
   > Android Gradle plugin requires Java 11 to run. You are currently using Java 1.8.
     You can try some of the following options:
       - changing the IDE settings.
       - changing the JAVA_HOME environment variable.
       - changing `org.gradle.java.home` in `gradle.properties`.

The solution is to open File > Settings → Build, Execution, Deployment → Build Tools → Gradle and change "Gradle JDK".

This should be set automatically.

Description

See title

Dear @Domi04151309,
Thanks a for this great looking App. 🙏🏼
Would it be possible to integrate the IKEA Tradfri protocol as well, as it its kind of Philippe Hue or ZigBee compatible?

In a first try I was not able to 'find' LEDs of my smart home system.

Best regards
Matl

Description

The experimental device discovery in HomeApp 1.7.2 crashes here in my home network.

I'm pretty sure it has to do with one of the devices here in the network, but I don't know which.

I WifiService: acquireMulticastLock uid=10088
I mi04151309.hom: Background concurrent copying GC freed 28261(3249KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 5807KB/11MB, paused 2.376ms total 284.427ms
D Volley  : [1663] e.c: /data/user/0/io.github.domi04151309.home/cache/volley/1061423297142620875: java.io.FileNotFoundException: /data/user/0/io.github.domi04151309.home/cache/volley/1061423297142620875: open failed: ENOENT (No such file or directory)
D Volley  : [1663] e.o: Could not delete cache entry for key=http://192.168.3.3:49152/description.xml, filename=1061423297142620875
D Volley  : [1658] e.c: /data/user/0/io.github.domi04151309.home/cache/volley/1061423297142620875: java.io.FileNotFoundException: /data/user/0/io.github.domi04151309.home/cache/volley/1061423297142620875: open failed: ENOENT (No such file or directory)
D Volley  : [1658] e.o: Could not delete cache entry for key=http://192.168.3.3:49152/description.xml, filename=1061423297142620875
I mi04151309.hom: Background young concurrent copying GC freed 80112(8928KB) AllocSpace objects, 12(240KB) LOS objects, 50% free, 5748KB/11MB, paused 680us total 106.160ms
I WifiService: releaseMulticastLock uid=10088
D AndroidRuntime: Shutting down VM
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: io.github.domi04151309.home, PID: 1093
E AndroidRuntime: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:501)
E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
E AndroidRuntime: 	... 1 more
E AndroidRuntime: Caused by: org.xmlpull.v1.XmlPullParserException: expected: /link read: head (position:END_TAG </head>@18:9 in java.io.InputStreamReader@2c10d77) 
E AndroidRuntime: 	at com.android.org.kxml2.io.KXmlParser.readEndTag(KXmlParser.java:984)
E AndroidRuntime: 	at com.android.org.kxml2.io.KXmlParser.next(KXmlParser.java:375)
E AndroidRuntime: 	at com.android.org.kxml2.io.KXmlParser.next(KXmlParser.java:313)
E AndroidRuntime: 	at b.a.a.a.h(Unknown Source:244)
E AndroidRuntime: 	at b.a.a.a.g(Unknown Source:5)
E AndroidRuntime: 	at b.a.a.b$c.b(Unknown Source:7)
E AndroidRuntime: 	at b.a.a.b$c.a(Unknown Source:2)
E AndroidRuntime: 	at b.b.a.w.n.O(Unknown Source:8)
E AndroidRuntime: 	at b.b.a.w.n.e(Unknown Source:2)
E AndroidRuntime: 	at b.b.a.f$b.run(Unknown Source:30)
E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:883)
E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:100)
E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:214)
E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7356)
E AndroidRuntime: 	... 3 more
W ActivityTaskManager:   Force finishing activity io.github.domi04151309.home/.activities.SearchDevicesActivity
I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
I Process : Sending signal. PID: 1093 SIG: 9
I WindowManager: WIN DEATH: Window{6ced571 u0 io.github.domi04151309.home/io.github.domi04151309.home.activities.SearchDevicesActivity}
I ActivityManager: Process io.github.domi04151309.home (pid 1093) has died: fore TOP 
I WindowManager: WIN DEATH: Window{ec0885f u0 io.github.domi04151309.home/io.github.domi04151309.home.activities.DevicesActivity}
I Zygote  : Process 1093 exited due to signal 9 (Killed)

Additional information

• Android version: 10
• Home App version: 1.7.2
• Installation source: F-Droid

Description

If you press the back button while polling commands, the application crashes when using the SimpleHome APi protocol. This present if device use "switch" mode. Some times android show message that app was stopped, usually it closed without messages.

• Android version: System Settings > About > Android version 10
• Home App version: Settings > About > Version 1.9.0(190)
• Installation source: F-Droid

Describe the solution you'd like

Basic Support:

• Show the Dashboard {Server}:1880/ui/

Enhanced Support

• Add a possibility to edit nodes {Server}:1880/
• Add possibility to send notification to HomeApp

Support for Tasmota, an alternative firmware for ESP8266, would be nice. I use multiple devices with Tasmota installed (self-flashed), but there is no easy-to-use open source app to control them. I'm currently using a browser with saved links to change the state of the ESPs. I also installed and configured an MQTT broker and everything is going well, but there is no useful open source app for that either. A home automation system would surely be an exaggeration to control a handful of devices.

Your app looks promising, so it would be great if you could add Tasmota support. Here is a link to commands that can be issued: https://tasmota.github.io/docs/Commands/

Command examples for web requests:
http://<ip>/cm?cmnd=Power%20Toggle
http://<ip>/cm?cmnd=Power%20On
http://<ip>/cm?cmnd=Power%20Off
http://<ip>/cm?user=admin&password=joker&cmnd=Power%20Toggle

Description
Adding a new device with latest git version f95d6a3 is broken.

1. Settings
2. New device
3. Add device with address
4. Name: Test
5. Address: homeapp-simpleapi.boo/
6. Click create
7. No device is added, device list is empty

11-28 22:25:33.952  7892  7892 D AndroidRuntime: Shutting down VM
11-28 22:25:33.969  7892  7892 E AndroidRuntime: FATAL EXCEPTION: main
11-28 22:25:33.969  7892  7892 E AndroidRuntime: Process: io.github.domi04151309.home, PID: 7892
11-28 22:25:33.969  7892  7892 E AndroidRuntime: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:501)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	... 1 more
11-28 22:25:33.969  7892  7892 E AndroidRuntime: Caused by: org.json.JSONException: No value for order
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at org.json.JSONObject.get(JSONObject.java:399)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at org.json.JSONObject.getJSONArray(JSONObject.java:594)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at s2.d.j(:42)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at s2.d.b(:87)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at io.github.domi04151309.home.activities.EditDeviceActivity.a0(:169)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at io.github.domi04151309.home.activities.EditDeviceActivity.V(Unknown Source:0)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at n2.f.onClick(Unknown Source:19)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.view.View.performClick(View.java:7259)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.view.View.performClickInternal(View.java:7236)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.view.View.access$3600(View.java:801)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.view.View$PerformClick.run(View.java:27892)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:883)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:100)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:214)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7356)
11-28 22:25:33.969  7892  7892 E AndroidRuntime: 	... 3 more

Additional information

• Android version: 10
• Home App version: f95d6a3
• Installation source: Own Build

Add text box in SimpeHomeAPI, for send to device. For example setting up time for alarm.

Implement a submenu in the SimpleHome API, this will allow to implement several features, for example: make a separate item for setting up a device from the application or group devices by type or by room.
For example, add a "submenu" mode to the list of modes. In which the application will wait for a response an object such as "commands".

Is it possible to make a connection to Bosch SHC like as https://github.com/tschamm/boschshc-hass ?

Add support for TP-Link Tapo devices like P100, P110...

Someone reverse engineered the API: https://k4czp3r.xyz/reverse-engineering/tp-link/tapo/2020/10/15/reverse-engineering-tp-link-tapo.html
There are libraries for Node.js and Python: https://github.com/dickydoouk/tp-link-tapo-connect and https://github.com/fishbigger/TapoP100

As the actual tasmota implementation just works for me if I'm at home because I don't have all my smart devices in the www by them self but via mqtt.

Further more the avtual use off my password feels unsecure.

Describe the solution you'd like
A previously connected device might not change available commands often. Reloading a potentially large list of command at each connect could be avoided.

A clear and concise description of what you want to happen.
I think a separate "heartbeat" message could be used instead of loading the full command list if an device is opened. This message would only need to contain some basic information over the available command, to make sure there are no changes. If there is a change, the full command list has to be called, resulting in a performance penalty. However, this probably happens way less frequently so often only a short message is needed to check if a device is available.

Add more device icons like security cameras, smart outlets... or maybe option to upload png/svg icon from storage.

Version 1.7.3 brings many new features, but the version number indicates that it's a bugfix release.

It would be nice if HomeApp would follow the "semantic versioning" rules: https://semver.org/

• Bugfix-only releases: Increase the 3rd number in the version: x.y.z+1
• Feature releases (even when they contain bugfixes): Increase the 2nd number, reset the 3rd to 0: x.y+1.0
• Breaking changes (removed features): Increase the major version, reset the others to 0: x+1.0.0.

Auto send "/commands" request ( for SimpleHomeAPI) devices, for refresh actual status, after receiving "toast" message.

Description

After last update app don't work through cellular network. Through wifi work ok.

Additional information

• Android version: _System Settings > About > Android version 10
• Home App version: _Settings > About > Version 1.7.3
• Installation source: F-Drod

Hi! I was wondering if it is possible to implement the app with some type of macro, in particular with alarms.

When the alarm first rings in the morning you can configure the app to turn on a light in your bedroom automatically.

Description
After moving a device in the device list in settings, tapping the device to edit it opens edit screen for the wrong device.

1. Open device settings
2. Move device 2 up to before device, so that it's the new number 1
3. Tap on device 1 to edit it
4. Device 2's edit screen is shown

Workaround: After re-ordering devices, leave the device settings with the back button. Then go back to device settings list and tap the device to edit it.

Additional information

• Android version: 10
• Home App version: Commit aa67490 (shelly branch)
• Installation source: own build

When automatically discovering devices via mDNS (since #27), HomeApp resolves the IP address and stores that in its configuration: url=http://192.168.3.71/.
This works fine for IoT devices with static IP addresses, but not for those that get a new one everytime from the DHCP server (dynamic IP).

The solution to this problem would be to not resolve the IP address during discovery, but to store the discovered name and then resolve it via mDNS when accessing the device.

This could be integrated into the current structure by saving "http://mdnsname.local/" as path (url=http://shellyplus1-a8032abd1bcc.local/). When trying to access that path, HomeApp would need to check if the domain ends with .local and resolve the domain via mDNS. Then the local domain would need to be replaced in that path, and then the actual HTTP request could be made.

I personally use static IPs for my IoT devices, so I don't have this problem. Others could, though.

Allow to set a default device. If a default is set, the app opens with default device. I only use one "bridge " and 2 vendors.

Detect the current preferred color theme (dark or light) and use it (extra setting like other apps - Nextcloud has 'Follow System' in OSS app).

I was worried because you only added light theme screenshots in fdroid.

Maybe also add Auto (day/night) - no value to me.

My router requires HTTP authentication to access the system, but the app doesn't seem to support this. It shouldn't be too hard to implement and it would be really nice. This app seems very cool so far, setting up an ESP8266 went perfectly and the app looks nice.

You can add Screenshots for F-Droid, too, if you want.
https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/
https://gitlab.com/snippets/1895688
That was simply information about what is still possible. You would then only have to enter the screenshots in fastlane. This is just one way that you can also add screenshots to the app view if you can. If you added screenshots (then F-Droid is happy) and if you can't add any -> then you can close the issue because it was only an info. Thank you that your app is available in
fdroid. Very much for your attention.

it is only information.

Hello, while I am still not an actual user of this app (that may happen once I set up Home Assistant at our house), I have tried to evaluate Home App multiple times in the past with simple HTML-based devices, namely routers, without any success, and I had just tried it again, without any new results.

I have tried accessing the settings of:

Xiaomi Mi3 (Rev.1), running PandoraBox and X-Wrt (Chinese OpenWrt distro that is actually vanilla OpenWrt Nightly, down to the package sources)

Xiaomi Mi3G, PandoraBox (will flash vanilla OpenWrt when I have the time)

Netgear DM200, running vanilla OpenWrt (I need to update it, it's from last year)

Linksys WRT32X, running vanilla OpenWrt (I need to update it, it's from last year)

TP-Link W8970 V2, running latest stock firmware

OEM D-Link DSL-2740U, running latest OEM firmware

TP-Link RE200 V1, running latest stock firmware

Other than that, I am pretty excited about Home App (It would be nice to be able to control our air conditioners, however the manufacturer (Tadiran) was lazy with those and outsourced the wireless tech to some random company, and we're not going to install the malware that is recommended for them (I have run a few tests on the APK) (especially since we are used to using the bundled remotes (I am more interested in connecting them to an isolated network to prevent unwanted connections to them)), so figuring out how they even they even work will take time (the recommended malware requires an account with some random Chinese company)).

Aside from the Hue/Saturation/Brightness sliders, there should be a setting (or button) for a "visual" color picker, where someone can pick colors by dragging or tapping into a gradient of colors.

Describe the solution you'd like

Link to GitHub and open a normal browser. Don't use no WebView. It is really annoying to login (2FA annoying) or share something with desktop.

Add a way to refresh the states. I tried to double tab the IP/Header and swipe down.

Use case
Second phone/tablet, some remote in room or in my case a desktop app, Also a timer or routine is used.

Okay so I set up a diyHue Bridge on my Pi and if I try to connect to it over the Hue Essentials App with the Hue API it's working just fine, but if I try to connect over the HomeApp and the Hue API I can't connect to the Bridge. I mean for sure I could also just use the website but I would really like to use the HomeApp since it is a good looking and also good working with other devices, like using and controlling the lamps on there own over the App