Closed bieniu closed 3 years ago
It should be supported in 38rc6. Code is in beta, so if You want You may test it by building current beta and uploading to sensor. Or wait for next beta release to check. But for me it should work :smiley:
Great, I'm already using beta to test new features.
New beta on update server (38rc6)
One more thing... sorry for being late
Would it also be possible to add another one text field manufacturer
with a value such as Nettigo
or something similar?
I wonder if the field ID
shouldn't be lowercase. This is safer when it comes to possible typos.
Can be done. So, new TXT field with key manufacturer
, right? Also downcase on ID value is possible. Probably with next beta.
Great, thanks!
OK, commit 8269356046547bb5f6c296fc0d2ca2287b4063f9 done that. With next beta will be deployed
Home Assistant uses
zeroconf
to discover a NAM device on the local network and propose a configuration of the integration to the user. The hostname is checked, if it containsNAM-
that means this is a NAM device.If the user changes the network name in the NAM device configuration, the hostname of the device will also change and the HA will not be able to discover the device.
Adding an additional text
ID
information with the default hostname (NAM-12345678
) would solve this problem.This is an example of mDNS information from Shelly device with
ID
: