WiZ Plugin installed but no devices appear in "Devices" tab Topic is solved

[Pecap]

Hi everyone,

I've successfully installed the Domoticz WiZ Connected plugin on my Raspberry Pi. The plugin appears under Setup → Hardware, and I've configured the correct subnet: 192.168.XXX.0/24.

However, the expected devices do not show up in the Devices tab.

Here's what I've tried so far:

Confirmed UDP communication works:
Using this command, I get a proper response from the bulb:

echo '{"id":1,"method":"getSystemConfig"}' | nc -u -w1 192.168.XXX.236 38899

Response:

{"method":"getSystemConfig","id":1,"env":"pro","result":{"mac":"a8bb504570f2", ...}}

Promiscuous mode is active:
My network interface eth0 is already in promiscuous mode.

Plugin configuration:

Subnet: 192.168.XXX.0/24

Hostname prefix: I've tried default wiz_, and also variations like wiz_,ESP03

Domoticz version:

Version: 2024.7

Build Hash: b317cfab1

Compile Date: 2024-07-13 16:59:31

dzVents Version: 3.1.8

Python Version: 3.9.2 (GCC 10.2.1 20210110)

Despite all this, no devices appear in Domoticz.

Are there any additional steps I might be missing?
Could it be a problem with ARP discovery or something related to the network configuration?

Any help or suggestions would be greatly appreciated!

many thanks in advance

[waltervl]

I do not have this plugin but normally you should look at the log to see log messages of a plugin when something is not running as expected. Menu Setup - Log

Also check the setting to allow creation of new Hardware devices in menu Setup - Settings.

[Pecap]

Hello,

I wanted to give a quick update and thank you for your help!

I found the root cause of my problem:
In the plugin configuration, I had mistakenly entered the wrong subnet – it was set to 192.178.123.0/24 instead of the correct 192.168.123.0/24.

After correcting it, my WiZ lamp immediately appeared under the Devices tab in Domoticz.
Now I can control it perfectly via Domoticz!

Thanks again for your support and suggestions, especially for pointing me towards checking the logs and the hardware settings.
This really helped me find the mistake!