But I am using the android bridge. May be that there is something different to the original bridge.
-
is there anyone using Nuki dooropener
-
Can you configure the bridge and see if battery status is something you can enable for the http web server
And if its not possible to get the info. You can hide the battery via the device config xAttributeOptions name: batteryLevel, hidden : enable
-
Thd bridge software is rel. 1.4.6. Last updatd in 01.2021
To configure is only the ip adress, port and api token. -
This problem is related to the android bridge. My native bridge is on version 2.9.1 (new HW version).
Your JSON response is the old style before the update which included the battery percent update. This was with version (2.7.0 (new HW) / 1.17.0 (old HW) -> https://developer.nuki.io/t/nuki-bridge-firmware-release-notes-public-releases/2797BTW: As I read in the last days the android bridge development will end -> https://nuki.io/de/blog/nuki-news-de/update-zur-nuki-android-bridge-app-das-ende-einer-aera-ist-auch-immer-ein-neuer-anfang/
-
Thanx for this “bad” info.
This means, it will be better to switch over to the original nuki bridge.
In the past I think, the android bridge was not so stable and very often not available. So in my mind I think it is not necessary to invest more time in this product.
Thanks a lot for your time and your invested know-how. Was really helpful for me. -
For the extra info item I would propose to add them as by default hidden attributes. If they are supported by your bridge, you can unhide them via the xAttributeOptions.
The extra info items are:
- batteryChargeState (0-100%)
- batteryCharging ( true | false)
- doorsensorState (door open | door closed)
Let me know if this is an workable approach and if this list is complete.
An alternative that is future proof and maintainer friendly. Adding extra info items via the device config. If you know the item name used by the bridge, you can add it, give it optional a unit and acronym and it will show up in the gui.
I will implement this alternative in the next version.
-
I released version 0.9.22
In this release you can add extra information fields (if your Nuki bridge is supporting it) => More info
After upgrading open the device config and save (for all the NukiDevices).
This is to get the extra information fields config active. -
I made the update and it works as nice as the last version! Thanks for this nice peace of software.
Some goodies for the wiki:
A list of possible attributes would be helpful,. I think not everybody knows how to get the attributes.
Just a hint in the wiki likehttp://<ip address>:8080/list?token=<your token>
to get:[ { "deviceType": 0, "nukiId": 12345678, "name": "Nuki HWR", "firmwareVersion": "2.9.10", "lastKnownState": { "mode": 2, "state": 3, "stateName": "unlocked", "batteryCritical": false, "batteryCharging": false, "batteryChargeState": 74, "doorsensorState": 2, "doorsensorStateName": "door closed", "timestamp": "2021-02-10T19:26:35+00:00" } } ]
Not a must, but a nice feature in the config would be a pull down menu for the type, because just “string” and “numbers” are available.
-
You are right I forgot the boolean. One + more for the pull down
-
In version 0.9.24, I added:
- instructions to get the available extra fields from the bridge
- localisation for button names and attribute acronyms and values
The ‘original’ button names are ‘lock’ and ‘unlock’. If your localisation works, the buttons can have already local language names.
If not and or you want to change it the button names in your language, check your language file in /pimatic-app/node_modules/pimatic/locale.
And if you are for example Spanish look in file es.json for "lock’ : “bloquear” and ‘unlock’: “desbloquear”. Otherwise add the two lines to the localization file. -
I found the update to 0.9.25. In my case with this version the states of
StateName
anddoorsensorStateName
are not shown anymore in my English test environment?
-
Yes, I did. I will try later on an other machine.
-
I know. Before I run version 24. There it was fine.
-
I now made a test on my Windows Laptop, my Chromebook (never seen the Nuki plugin on it) and my Android smartphone with a fresh installed Firefox browser. Always the same.