WIZ Socket and WIZ bulb conflict

[aanton77]

Hello everyone,
I have the following problem with a WIZ socket that is integrated in Home Bridge. This socket has worked perfectly for a long time and was correctly integrated into Home Bridge. Due to a new installation of Home Bridge, this socket now appears both as a socket and as a bulb in the Home Bridge device overview. It no longer functions as a socket and can therefore no longer be controlled.

[27.11.2024, 08:41:25] [WizSmarthome] Updating accessory: Wiz Unknown Bulb cc40854d0b22 [formerly Wiz Wiz Socket cc40854d0b22]

How can I solve the problem? How can I remove the incorrect entry for the bulb so that Home Bridge recognizes this device correctly as a socket again and can therefore also switch it?

Many thanks for your support!

[astr0nut]

I seem to have the same problem. The socket is listed as a light. During a child bridge restart, the log says:
[11/29/2024, 8:34:27 PM] [WizSmarthome] Updating accessory: Wiz socket
[11/29/2024, 8:34:28 PM] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.

[Kinodim]

I get the same warning and this seems to prevent switching my sockets

[mark-weathersby]

I fixed this in my instance by changing:

static is = (device: Device) => {
return ["SHRGB", "SHDW", "SHTW"].some((id) => device.model.includes(id)) // Bulbs
|| device.model.startsWith("ESP20_") // Light Pole
|| device.model.startsWith("ESP25_"); // LED String lights

to

static is = (device: Device) => {
return ["SHRGB", "SHDW", "SHTW"].some((id) => device.model.includes(id)) // Bulbs
|| device.model.startsWith("ESP20_"); // Light Pole

in src/accessories/WizLight/index.ts and dist/accessories/WizLight/index.js. It looks like the LED string lights use the same kind of switch as the new outlet, so the outlet was recognized as a light.

[lmbranco]

This issue seems to be introduced with version 3.2.6 and has been happening most probably since then.
I was not able to add two new Wiz Smart Plugs, identified as ESP25_SOCKET_01, and that were always being identified as Unknown Bulb.
I reverted to version 3.2.5 and the problem was solved, I can now use both Plugs without issues.

[eriktheviking]

This issue seems to be introduced with version 3.2.6 and has been happening most probably since then. I was not able to add two new Wiz Smart Plugs, identified as ESP25_SOCKET_01, and that were always being identified as Unknown Bulb. I reverted to version 3.2.5 and the problem was solved, I can now use both Plugs without issues.

This fixed my issue. It couldn't recognize my wiz plug as a plug, and it was unresponsive. Now it works, and works well.

[felixkluge]

I am having the same issue with version 3.2.12. Downgrading to v3.2.5 helped.