Re: [mh] mqtt_discovery
Giles Godart-Brown <[email protected]> Fri, 6 Feb 2026 09:41:07 +0000
| Newsgroups | gmane.comp.misc.misterhouse.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============4709631722335477169==
Content-Type: multipart/alternative;
boundary="------------209auMeNFB18jBVJkFOcTRV3"
Content-Language: en-GB
This is a multi-part message in MIME format.
--------------209auMeNFB18jBVJkFOcTRV3
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Sorry Brian, but cannot help.
Oddly Z-wave never really caught on here in UK, there is much more Zigbee
Giles
On 06/02/2026 00:34, Brian M wrote:
>
> I'm now using zwave-js-ui to handle direct management of ZWave
> devices, and it works great. It has an API, but I'm using it's MQTT
> facility to publish device states and such, so I'm getting deeper into
> Dave's mqtt_discovery.pm module. My only "problem" (well, nuisance
> issue) is that, based on the data zwave-js-ui provides mqtt_discovery
> is creating MH object names like the following:
>
> mqttd_Brians_Office_Fan_Brians_Office_Fan
> mqttd_Brians_Office_Light_Brians_Office_Light
> mqttd_Entryway_Front_Porch_Entryway_Front_Porch
> mqttd_Garage_Alert_Light_Garage_Alert_Light
>
> These are both redundant and a little unwieldy. I'm sure the
> redundancy comes from the data zwave-js-ui provides, but I haven't
> figured out if mqtt_discovery provides a handy way to customize the
> object names. My first thought was to add a test for an optional
> user-supplied subroutine to build the object name, and if that
> subroutine wasn't provided, keep doing what it's currently doing. But
> before I try to reinvent the wheel I thought I'd ask if there's Dave
> or anyone else has a better, existing way to customize those names.
>
> -Brian M
>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
--------------209auMeNFB18jBVJkFOcTRV3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="4" face="Calibri">Sorry Brian, but cannot help.<br>
Oddly Z-wave never really caught on here in UK, there is much more
Zigbee<br>
Giles<br>
</font><br>
<div class="moz-cite-prefix">On 06/02/2026 00:34, Brian M wrote:<br>
</div>
<blockquote type="cite"
cite="mid:[email protected]">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>I'm now using zwave-js-ui to handle direct management of ZWave
devices, and it works great. It has an API, but I'm using it's
MQTT facility to publish device states and such, so I'm getting
deeper into Dave's mqtt_discovery.pm module. My only "problem"
(well, nuisance issue) is that, based on the data zwave-js-ui
provides mqtt_discovery is creating MH object names like the
following:</p>
<pre class="inner-pre" style="font-size: 16;white-space:pre-wrap;">mqttd_Brians_Office_Fan_Brians_Office_Fan
mqttd_Brians_Office_Light_Brians_Office_Light
mqttd_Entryway_Front_Porch_Entryway_Front_Porch
mqttd_Garage_Alert_Light_Garage_Alert_Light
</pre>
<p>These are both redundant and a little unwieldy. I'm sure the
redundancy comes from the data zwave-js-ui provides, but I
haven't figured out if mqtt_discovery provides a handy way to
customize the object names. My first thought was to add a test
for an optional user-supplied subroutine to build the object
name, and if that subroutine wasn't provided, keep doing what
it's currently doing. But before I try to reinvent the wheel I
thought I'd ask if there's Dave or anyone else has a better,
existing way to customize those names.</p>
<p> -Brian M</p>
<p><br>
</p>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">________________________________________________________
To unsubscribe from this list, go to: <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/misterhouse-users">https://lists.sourceforge.net/lists/listinfo/misterhouse-users</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------209auMeNFB18jBVJkFOcTRV3--
--===============4709631722335477169==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============4709631722335477169==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
--===============4709631722335477169==--