[Android] Habitat - Open Beta test

Discussions about Z-Way software and Z-Wave technology in general
Provo
Posts: 100
Joined: 19 Oct 2016 19:54

Re: [Android] Habitat - Open Alpha test

Post by Provo » 02 Jan 2018 08:37

Aegis wrote:
27 Dec 2017 17:58
Finally, regards to your hidden/deactivated devices cluttering up everything, notice that you have an option in settings to hide everything that's not associated with a room. Does this help?
No, not really. Whenever I add a new device to my network, I associate all the virtual devices created by that device to the room in which it's located with the "Move all elements to room" feature. This is simpler than associating each of the virtual devices. From the same page, I mark the ones I am not interested in as deactivated. With Fibaro dimmer modules, the number of uninteresting virtual devices is pretty high.

But I note that the Rooms overview in the app shows "N devices" for each room, and this number is the correct one – meaning, it excludes hidden and deactivated devices. But when I enter the room, the deactivated/hidden devices are listed. And what's strange, is that it seems to show most elements that are deactivated or hidden, but not all. For example, it lists all the deactivated Fibaro alarms and power measurements associated with these dimmers, but does not show the same dimmer modules' deactivated togglebutton elements associated with button press for those who have this feature configured. In other words, it doesn't seem perfectly consistent. Could there perhaps be something fishy with the logic checking for "permanently_hidden" and "visibility", and possibly some other parameter like "deviceType"?

By the way, do you also have plans to do remote support, and implement functionality for the mobile presence device? :)

Aegis
Posts: 30
Joined: 04 Jan 2017 22:26

Re: [Android] Habitat - Open Beta test

Post by Aegis » 02 Jan 2018 14:40

Thanks for the detailed description. the ZWay API has numerous quirks and I believe the issue of hidden devices showing up should be fairly easy to fix. I'll look into it right away :)

I am also looking into adding support for remote access. I don't use it myself as I don't really trust it but perhaps I'll change my mind once I learn more about how it actually works and how credentials are handled.

When you say "mobile presence device", what do you mean exactly?

Thanks again!

Aegis
Posts: 30
Joined: 04 Jan 2017 22:26

Re: [Android] Habitat - Open Alpha test

Post by Aegis » 02 Jan 2018 15:06

Provo wrote:
02 Jan 2018 08:37
Could there perhaps be something fishy with the logic checking for "permanently_hidden" and "visibility", and possibly some other parameter like "deviceType"?
I ignore devices where visibility is set to false now. New update being published as I'm typing this ;)

Provo
Posts: 100
Joined: 19 Oct 2016 19:54

Re: [Android] Habitat - Open Beta test

Post by Provo » 02 Jan 2018 16:47

Aegis wrote:
02 Jan 2018 14:40
When you say "mobile presence device", what do you mean exactly?
By the looks of it, the Z-Way module part of your solution is forked from the official mobile app support module. The official one makes a test device for notifications and a presence device for each associated mobile phone. The latter doesn't seem to be functional, as it always has the status of "LOCAL". My guess is that it is intended to shift between "LOCAL" and e.g. "REMOTE" depending on whether the phone is on the same local network as Z-Way, but from skimming the module code, this part looks like it's not yet implemented – unless the phone app is supposed to "force update" the status of this vdev through the API and it just doesn't work for me.

As your code is a fork of this, your module also instantiates these two virtual devices, and the presence one seems equally non-functional. As this would be a nice feature, I was curious as to whether you had any plans to implement this in the foreseeable future. :)

As for the handling of credentials on remote access, I don't know which details you're thinking about, but at least it's encrypted through SSL, so that part is safe.

Aegis
Posts: 30
Joined: 04 Jan 2017 22:26

Re: [Android] Habitat - Open Beta test

Post by Aegis » 02 Jan 2018 17:13

Ah, gotcha. Your assumptions are correct. Since Habitat doesnt yet support remote access I havent gotten around to implement the shifting between local and remote states. :)

Also, fyi, once Habitat is out of beta I intend to migrate my codebase to Github.

Aegis
Posts: 30
Joined: 04 Jan 2017 22:26

Re: [Android] Habitat - Open Beta test

Post by Aegis » 02 Jan 2018 17:14

Btw, would you appreciate the option to show hidden devices in the app or would you reckon that always hiding them is what makes the most sense?

Provo
Posts: 100
Joined: 19 Oct 2016 19:54

Re: [Android] Habitat - Open Beta test

Post by Provo » 04 Jan 2018 08:26

Aegis wrote:
02 Jan 2018 15:06
I ignore devices where visibility is set to false now. New update being published as I'm typing this ;)
You will also want to ignore devices which have "permanently_hidden" set to true. Devices that are deactivated have this, while their "visibility" parameter could still be set to true. Deactivated devices are both hidden in the normal UI, and unusable in apps.
Aegis wrote:
02 Jan 2018 17:14
Btw, would you appreciate the option to show hidden devices in the app or would you reckon that always hiding them is what makes the most sense?
Personally I don't think I would use this feature, but others might find it useful, I don't know. But if you go for this, I suggest that even with "show hidden devices" set, it should still ignore the deactivated ones (the ones with "permanently_hidden" set to true).

Aegis
Posts: 30
Joined: 04 Jan 2017 22:26

Re: [Android] Habitat - Open Beta test

Post by Aegis » 04 Jan 2018 10:06

Provo wrote:
04 Jan 2018 08:26
Aegis wrote:
02 Jan 2018 15:06
I ignore devices where visibility is set to false now. New update being published as I'm typing this ;)
You will also want to ignore devices which have "permanently_hidden" set to true. Devices that are deactivated have this, while their "visibility" parameter could still be set to true. Deactivated devices are both hidden in the normal UI, and unusable in apps.
Aegis wrote:
02 Jan 2018 17:14
Btw, would you appreciate the option to show hidden devices in the app or would you reckon that always hiding them is what makes the most sense?
Personally I don't think I would use this feature, but others might find it useful, I don't know. But if you go for this, I suggest that even with "show hidden devices" set, it should still ignore the deactivated ones (the ones with "permanently_hidden" set to true).

Thanks for great feedback. I'll handle

Code: Select all

permanently_hidden
devices right away! I'll happily take any other ideas and suggestions you might have :)

fez
Posts: 71
Joined: 20 Jul 2015 23:03

Re: [Android] Habitat - Open Beta test

Post by fez » 05 Jan 2018 01:00

I tried different methods (browser, old app, new app, this app) but all of them have some flaws.
Here are the ones I observed until now:
- elements generated by Forecast.io Weather App are not displayed (but this is no major issue since you embedded the weather info on top of the home)
- the UI element generated by the Heating Control App is not displayed/controls are not available
- custom icons are not imported
- in landscape mode the weather information takes almost half of the screen. on the remaining portion the elements/text size is small, disproportional
- there is no full-screen option
I really like that there is no remote connection. I just want a local status monitor on a tablet.
This is great work so far, I just wanted to point out the above points to make it even better for my use case: using it as a status display on a tablet in landscape mode.
Thanks.
Last edited by fez on 06 Jan 2018 12:18, edited 1 time in total.

Aegis
Posts: 30
Joined: 04 Jan 2017 22:26

Re: [Android] Habitat - Open Beta test

Post by Aegis » 05 Jan 2018 15:07

Great feedback fez. I'll look into it.

- I will be updating the UI to be more compatible with both tablets and landscape orientations. The dashboard will be the first to be updated.
- I havent really considered a full screen option but I see your use case.
- Support for custom icons are on my to-do list and will hopefully be included in the next update.
- I have no experience with the "Heating Control App" so please feel free to elaborate on this issue.

Thanks again! :)

Post Reply