Add ability for browser to receiver updates to already discovered services.

[NorthernMan54]

I was looking at adding the ability to automatically detect changes to accessories and bridges, and needed the capability to receive TXT record updates. The existing Browser implementation just ignores them, so this pull request adds another event that will emit when a new message is received for an already discovered service.

This change is 100% backwards compatible with existing implementations.

[coveralls]

Pull Request Test Coverage Report for Build 8402488019

Details

• 12 of 13 (92.31%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.07%) to 82.665%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
lib/Browser.js	12	13	92.31%

Totals
Change from base Build 7907585379:	-0.07%
Covered Lines:	367
Relevant Lines:	405

---

💛 - Coveralls

[Supereg]

Thanks for the addition.

EDIT: Oops, forgot some comments, see final comment below.

[Supereg]

Thanks for the addition.

Just had a smaller comment and would love to request the addition of some unit test covering this functionality. Once that is implemented I'm happy to have this PR merged 🚀

[NorthernMan54]

@Supereg Before merging this, I think I need to increment the version in package etc. Does it auto publish to NPM or is it manual ?

FYI - I have been attempting to record the publishing steps for each package here - https://github.com/homebridge/documentation/blob/latest/Repositories.md

[Supereg]

@Supereg Before merging this, I think I need to increment the version in package etc. Does it auto publish to NPM or is it manual ?

FYI - I have been attempting to record the publishing steps for each package here - https://github.com/homebridge/documentation/blob/latest/Repositories.md

It will auto publish if you push a new version tag/commit. So just merge and I will publish for you.
not ideal for people without permissions to publish to main. We could aim for creating a workflow that does that version commit and tag eventually.

[NorthernMan54]

@Supereg Tks Merged

[Supereg]

Just double checked, I thought there was automatic publishing configured for this repository. It's not. It's currently manual. So feel free to create an issue for that. I'm here to help if someone wants to set something up 👍

[NorthernMan54]

#20