ToDo List

[mwarning]

• Use Fragments instead of Preference UI classes
  • This would also remove some minor hacks.
• translations
• be able to trigger an https open command and a bluetooth door bell
• parse door return data in various ways (e.g. json) (sort of - regex..)
• translate to Kotlin
• differentiate between locked/closed terminology

[stikonas]

parse door return data in various ways (e.g. json)

This would make app useful for other purposes too, e.g. turning lights on/off. Now LOCKED/UNLOCKED is expected in return data...

[mwarning]

Yes, this is rather limited right now. But making it more generic might also is a UI problem.
How to device that that specific value is present? Maybe a regex. But that might be rather complex to type.

[stikonas]

Regex is probably an overkill. Maybe it's easier to type exact message (similarly to open/close commands).

Regarding UI, that's unfortunately true :(. There are already quite a few fields in that MQTT dialog.

[mwarning]

@stikonas I have added two settings that default to LOCKED and UNLOCKED. They can be regular expressions as well. The code is not test yet.

I think it is ok, since the main target are DIY door systems. In use, someone needs to figure out the parameters and then can exchange the setup via QR-Code. :]

[stikonas]

@stikonas I have added two settings that default to LOCKED and UNLOCKED. They can be regular expressions as well. The code is not test yet.

I think it is ok, since the main target are DIY door systems. In use, someone needs to figure out the parameters and then can exchange the setup via QR-Code. :]

Thanks. It should work. I reviewed the commit, and it looks good to me (I don't really code in Java but it's readable anyway :)).