Configuration number not changing after name characteristic update #1128
-
|
I know there has been some changes done recently around the HS DB configuration number.. I’m certain my stuff was working fine some versions ago where updating both a Name and ConfiguredName would result in an increment of the config number of the DB, hence also triggering a notification that would then reflect the name change in Home app. Anyone seeing similar results? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Nothing changed in the code with regard to HS DB number updates, except that I added a new, optional function a while back to force the DB number to update, even if there has been no change to the database. HS would generally NOT not change config number as a result of any changes to the values of any characteristics, though it would change if other attributes of a characteristic changes (such as its PERMS, or TYPE). This may be the result of how the new iOS is handling changes to these characteristics? Apple seems to play with configuredName quite a lot. |
Beta Was this translation helpful? Give feedback.
-
Interesting... maybe I thought the DB number would increment on Name change while in fact the name change notification was instead triggered by a change of status of a contact sensor (motion detector).. I'll investigate this and let you know. Thanks again for the help! |
Beta Was this translation helpful? Give feedback.
-
|
In my case, when a And if I end up changing the |
Beta Was this translation helpful? Give feedback.
-
|
Characteristic::Name is generally not used after pairing is completed. Not all Services make use of ConfiguredName (Apple has no documentation on this). Recommend you start by using open ConfiguredName, and if that works, don't bother with Name. If Name is used, note that changing in the Home App does not cause anything to be updated on the ESP32 device. This is because once the Home App reads Name() upon pairing, it then stores that independently and does not ask for it from the device any further. Unfortunately Apple keeps changing how everything works and yet provides absolutely no documentation --- may have to experiment a bit to see what combinations work best for your specific app. When/if the database config number needs to be updated is also a bit of a mystery with regard to Name updates. |
Beta Was this translation helpful? Give feedback.
-
|
Things seems to be stable if I keep All set. Thanks! |
Beta Was this translation helpful? Give feedback.
Characteristic::Name is generally not used after pairing is completed. Not all Services make use of ConfiguredName (Apple has no documentation on this). Recommend you start by using open ConfiguredName, and if that works, don't bother with Name. If Name is used, note that changing in the Home App does not cause anything to be updated on the ESP32 device. This is because once the Home App reads Name() upon pairing, it then stores that independently and does not ask for it from the device any further.
Unfortunately Apple keeps changing how everything works and yet provides absolutely no documentation --- may have to experiment a bit to see what combinations work best for your specific app. …