No Devices in MQTT auto discovery client

[KoalaRoel]

After some issues with adding a new Shelly Wave device that is not supported in OpenZWave I learned that OZW is to be discontinued.
I got the new device working by creating my own confg file but the ZWave-JS-UI left me curious...

After some reading, and of course a good backup, I started the migration proces described in the wiki.
This was an interesting proces. Docker was completely new to me and getting Mosquitto and Zwave-JS-UI installed took some time.
Eventually this worked. All my devices showed in the ZWave-JS-UI webinterface. Mosquitto worked, verified with the MQTT-Explorer.

Getting them to show into Domoticz is my issue and question.
I added the "MQTT Auto Discover Client Gateway with LAN interface" in my hardware section with the IP and port settings.
This worked since I got a bunch of new devices in the device page.
When I go to hardware and select settings behind the MQTT client gateway I see nothing.
Here I expected to see all my devices just like behind my old USB controller device.

How do I get them to show up there?
Or is it normal to not have them there?

I am running on RPI Bullseye. Fresh install with old database backup.
Domoticz version 2023 2 stable. Prefer not to update to beta but will do if that is needed.


Thanks

[Yosaxz]

Same issue here.. setup doesn’t show devices in Domoticz. Tried different ports, renamed homeassitant, id/name send switch.

[gizmocuz]

Please note there are TWO different MQTT hardware options.
- MQTT Auto Discovery (Used for ZWaveJS-UI, Zigbee2MQTT and others)
- MQTT Client Gateway, used to send/receive devices between multiple Domoticz instances (But I would use the Domoticz server/client for this!!)

So be carefull to NOT mix these! For ZWaveJS-UI and Zigbee2MQTT you need to use the 'MQTT Auto Discovery' one.

If you get a bunch of new devices under the devices tab, this is expected.
For example, you previously had a switch named 'Outside', now search for the new switch in the devices tab, name it 'Outside New' and add it to your system.
Now press 'Edit' on the old switch (Outside) and press the 'Replace' button, and select 'Outside New', and your done.
Repeat this progress for the other devices

[akamming]

i am trying to do the openzwave migration again... good news is that zwave js ui for the 1st time (tried several times before) now finished the interviewing of the nodes (ofcourse did have to push the buttons on battery powered devices). So apparently several bugs fixed in zwave js ui

But after that I had the same issue yesterday as described here. Don't know if it helps, but for me it had 3 causes
1. Autodiscovery not enabled in zwave js ui (so autodiscovery should be switched on)
2. I referred to localhost for the mqtt server in zwave js ui, but that doesn't work. It should be the actual ip adress (so localhost does noet work. But 192.168.2.x does...)
3. The configured autodiscovery topic in zwave-js-ui was set to homeassistant-2 instead of homeassistant (probably been playing around with the settings too much in earlier attempts. Should be set to homeassisant if you use the default domoticz settings)

[koewacko]

I have exactly the same issue. Followed the migration description (which was very clear and easy to do) and everything went well/
In the Hardware tab, nothing shows up when clicking on SETUP of the MQTT Auto discovery. I do see all the devices showing up in the Domoticz log file as being discovered.

All devices are also showing up under the Devices tab, but when i add the device, they do not show up . I can turn (for example) a light on and off in the Devices tab, but it wont show under Switches (or other categories).

I have Autodiscovery turned on, i used a IP instead of localhost and the autodiscovery topic was still on homeassistent. I can connect with MQTT explorer and also fiddled around with CA certificates, but that only made it worse so i reverted back to non-tsl as it was after the migration.

[gizmocuz]

@koewacko, did you read my previous comment?
Also remember that switches are directly created, all other devices need to be received first (like temperature sensors)

[koewacko]

I read your comment, but since there was no need to keep the logging of the old Zwave devices (as they are all switches), there was no need to use the Replace function in my opinion. Since i deleted the old Zwave devicelike said in the wiki, im not able to Replace them at this moment.

I did exactly what was written in the wiki Migration page and i got to 90%. I got all the Zwave devices in the Devices tab, but when i add the Device (lets say a light switch), its nowhere to be found. I can switch the light via the Devices tab, its just nowhere to be found outside of the devices tab.

My Fibaro Roller Shutters 3 show alot of entries in the Devices tab, but noone of them to control the screens. Only overcurrent status, current values, position 1, position 2 etc etc.

I will see if removing and adding the devices works. No idea what to do.

[gizmocuz]

That could be another issue.
Go to Setup->Users, check that your user account does not have any specific devices set to be displayed/used

[koewacko]

When in the User menu, to the right it has the SET DEVICE button. 22 devices were not selected. Once i selected them all, the device were shown.

Thanks, this made my day!

[waltervl]

When in the User menu, to the right it has the SET DEVICE button. 22 devices were not selected. Once i selected them all, the device were shown.

Thanks, this made my day!

You better remove them all from this list when the user you have has an admin role. Then all devices will be shown automatically and no need to do this action again for new devices in the future.

To assign devices to a user is only needed when you want to limit devices to a specific user (also when using device sharing on different Domoticz environments) https://www.domoticz.com/wiki/User_Mana ... et_Devices

[pcrsdomoticz]

I have the same thing. After updating Domoticz 2024 jan and everything stopped working as my zwave stick was no longer supported.
Just install Z-Wave js ui oh and also Docker, don't worry it's really easy.
followed this
https://www.domoticz.com/wiki/Zwave-JS-UI
In the zwave js ui web interface (:8091) I seen a network, so it seems communication with the dongle is ok, in Domoticz I can add
MQTT Auto Discovery Client Gatewas with LAN interface
but when I press setup.... no devices (filled in the remote address and port 1883)
With docker ps -a , I see both zwavejs and mosquitto are running.
I also tried the recommended mosquitto_pub to send a fake temp device event for testing. That fake device does show up in Domoticz.
Someone an idea?

[waltervl]

Did you activate Auto discover in Zwave-JS-UI?
Check with Mqtt explorer if you see config devices are being created in the Homeassistant folder?

[pcrsdomoticz]

Thanks for the reaction.
I have this option on:
- Create devices in Home Assistant using MQTT discovery. This is an alternative to Home Assistant Z-Wave JS integration
I see no homeassistant folder, but I guess for me that would be domoticz folder, as that is under name in mqtt
What I see there is
* CLIENTS
-ZWAVE_GATEWAY-zwave-js-ui 2 topics 2 messages
-ZWAVE_GATEWAY-domoticz 2 topics 2 messages
driver
status = true
and then a list of node number with topics and messages

They all have format
currentValue = {"time":1705275585109,"nodeName":"","nodeLocation":""}
targetValue = {"time":1705275588480,"nodeName":"","nodeLocation":""}

* zwavedongle
switch
light
sensor
binary_sensor
cover
climate

*SYS
broker
version
uptime
clients
load
messages
store
subscriptions
shared_subscriptions
retained_messages
publish
bytes

I seen nothing with config devices.
Could there be a problem that topics "domoticz" and "zwavedongle" should have the same name?
Also not clear if I should have the
-MQTT Client Gateway with LAN Intereface
or
-MQTT Auto Discovery Client Gatewat with LAN interface
currently I have both (But also tried single one)

[waltervl]

Please recheck the Domoticz Zwave-JS-UI wiki page and make sure you have the correct mqtt prefix names. I think you changed some names and these changes were not correct.

[pcrsdomoticz]

It's working now, not sure why. I read somewhere that version mqtt>2 requires a password. Thought that would be solved with allow anonymous users, but I put a password on it and it worked. But I restarted some services also, so I don't really know what did it.

[pwhooftman]

I can't get mqqt autodiscovery to work.

I have GROTT Server running in docker to catch the traffic from my Growatt server to server.growatt.com, thats al working properly.
I have Eclipse-Mosquitto running in a docker container, and the messages from the grott server are received (see screenshot of MQQT Explorer)
I have set the MQTT auto discovery client in Domoticz to the right ip address & port of the mqtt broker, and set the discorey prefix to energy/growatt, energy, and growatt, but no new devices are created. Where to look further?

Edit: enabled authentication in the MQTT broker, but still no devices are discovered

[waltervl]

It seems GROTT server is not sending MQTT Auto discovery topics.
See the example screenshot in https://www.domoticz.com/wiki/MQTT_AD_R ... ms#Example
the homeassistant or in your case you configered the energy topic should have sensor/switch/binary_sensor/etc config topics.

[pwhooftman]

Thanks! Was just about to come to the same conclusion Just getting acquainted with mqtt:-)

[waltervl]

You could try to make your own mapping from GROTT MQTT topics to Domoticz devices with the mqtt mapper plugin. https://www.domoticz.com/forum/viewtopic.php?t=39279