No "Autodiscovery prefix" setting in hardware tab

For devices supporting the Auto Discovery feature. Like ZWaveJS2MQTT, Zigbee2MQTT.

Moderator: leecollings

Post Reply
Roofcat
Posts: 2
Joined: Sunday 23 January 2022 17:54
Target OS: -
Domoticz version:
Contact:

No "Autodiscovery prefix" setting in hardware tab

Post by Roofcat »

hello,

I am quite new to Domoticz, actually I try to accomplish my first setup - Orange Pi Zero with Armbian Buster, zigbee2mqtt with couple of sensors (temperature and humidity, waterleak, door sensor etc), mosquitto and domoticz version: 2021.1 (build 14098). zigbee and MQTT part works fine and I follow wiki instructions (https://www.domoticz.com/wiki/MQTT#Add_ ... Gateway.22) but for MQTT AD client I have no field for setting "Autodiscovery prefix" :(

Am I doing somthing wrong?
regards,
Roofcat
solarboy
Posts: 300
Joined: Thursday 01 November 2018 19:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 2024.6
Location: Portugal
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by solarboy »

This is only available in beta versions of Domoticz for now.
Intel NUC with Ubuntu Server VM (Proxmox),mosquitto(docker),RFXtrx433E,zwavejsUI (docker),Zigbee2mqtt(docker),SMA Hub (docker),Harmony Hub plugin, Kodi plugin,Homebridge(docker)+Google Home,APC UPS,SMA Modbus,Mitsubishi MQTT, Broadlink,Dombus
User avatar
jvdz
Posts: 2189
Joined: Tuesday 30 December 2014 19:25
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.107
Location: Netherlands
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by jvdz »

You are on the right version, but did you select the correct hardware?
Use "MQTT Client Gateway with LAN interface" not "MQTT Client Gateway with LAN interface"
New Garbage collection scripts: https://github.com/jvanderzande/GarbageCalendar
Creo2005
Posts: 25
Joined: Wednesday 26 February 2020 13:39
Target OS: Linux
Domoticz version:
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by Creo2005 »

jvdz wrote: Sunday 23 January 2022 18:34 You are on the right version, but did you select the correct hardware?
Use "MQTT Client Gateway with LAN interface" not "MQTT Client Gateway with LAN interface"
May be: MQTT Auto Discovery Client Gateway with LAN interface ?
And you reminded me of this:
Image
MQTT Client Gateway with LAN interface - not need anymore?
Roofcat
Posts: 2
Joined: Sunday 23 January 2022 17:54
Target OS: -
Domoticz version:
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by Roofcat »

jvdz wrote: Sunday 23 January 2022 18:34 You are on the right version, but did you select the correct hardware?
Use "MQTT Client Gateway with LAN interface" not "MQTT Client Gateway with LAN interface"
I am using "MQTT Auto Discovery Client Gateway with LAN interface" but setup fields looks like that - notrace of Autodiscovery topic field
Image

I wonder what can be wrong?
Regards,
Roofcat
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by EddyG »

If you are using the right hardware: MQTT Auto Discovery Client Gateway with LAN interface
In chrome try F5 or Ctrl-F5
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by EddyG »

In your first post you stated build 14098
This is a picture of build 14098
24.01.2022_18.55.49_REC.png
24.01.2022_18.55.49_REC.png (6.75 KiB) Viewed 1345 times
Notice the text at the end it states "Leave empty for Disabled"
Your screen print states something different.
So what is wrong? And why is in your screen print the type of the hardware missing?
Filip
Posts: 100
Joined: Thursday 03 November 2016 10:12
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by Filip »

Hi,
Is there any solution?

I am using the build:
Version: 2022.2
Build Hash: eea9db734
Compile Date: 2022-11-05 13:05:35
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Oct 31 2022, 14:04:00) [GCC 8.3.0]

Also no field "Auto Discovery Prefix" in the plugin "MQTT Auto Discovery Client Gateway with LAN interface".
Probably because 2 new fields were added compared to the documentation and there is probably a conflict somewhere.
When starting the plugin, the error "Auto Discovery Topic empty!" is generated.

Already did refresh and cleared again the cache of the browser (Chrome).

Any help for solution?
User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by waltervl »

This is definitely a browser cache issue.... Please clear browser cache as instructed on the wiki. Alternatively try a browser session in private/incognito mode.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Filip
Posts: 100
Joined: Thursday 03 November 2016 10:12
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by Filip »

Indeed... In a private browsing it works for whatever reason!
Cleared again the cache of Chrome and now OK...
I don't understand because I already cleared the cache (images only) before... Perhaps had to clear the complete cache!
Anyway thanks for the help and a message for all who reads this: pay attention to clear completely the cache!
Thanks again.
F
User avatar
jvdz
Posts: 2189
Joined: Tuesday 30 December 2014 19:25
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.107
Location: Netherlands
Contact:

Re: No "Autodiscovery prefix" setting in hardware tab

Post by jvdz »

Filip wrote: Tuesday 17 January 2023 21:51 Cleared again the cache of Chrome and now OK...
I don't understand because I already cleared the cache (images only) before... Perhaps had to clear the complete cache!
You always need to clear the complete cache to refresh the js and html files as well or else old code is mixed in causing these issues!
New Garbage collection scripts: https://github.com/jvanderzande/GarbageCalendar
Post Reply

Who is online

Users browsing this forum: boum and 0 guests