OK, so I must use 1883 as a port.
I suppose I have had the proper credentials (only login “addons” without password), but it didn’t work. I also disabled “Reject unauthorized” connections. Even though - it didn’t help.
I will try today afternoon.
[EDIT]
I have MQTT Broker and MQTT Client active on Homey. I suppose it can be a problem. Am I right or it is not important at all?
One more update. I have a hue sensor, i am using the illuminance to set flags, when i add a sensor via your app, ill get the illuminance value, and not the illuminance_lux value.
Ok, so I will check, if switching off MQTT Broker in Homey makes a difference.
No password, cause I just want to make it simple
[SOLVED]
So, the thing was to ADD NEW USER in Home Assistant and allow him to login to HA from local network. Maybe it is because I have updated HA to 2023.07.01.
Now I have the bridge added correctly and all devices registered in HA Zigbee network available (also Blitzwolf SHP-13).
Thanks for the great effort bringing this app to live. Do you think it’s possible for you to add support for this devices
In the past I used deConz app to get the device into homey but as the deConz app has been shutdown, I’m a bit in a bit pressured to find a way to support my 20 switches controlling my house lights
I know z2m does support the devices running Zigbee green power.
Hi @Gruijter, would you be interested in adding a driver for a Tuya 2-gang dimmer and a Tuya 2-gang switch (both in-wall modules)?
Both are functional in Z2M and their 1-gang counterparts are OK in Homey via Z2M; but the 2-gang versions only show LQI (in Homey, that is; in Z2M they are fully functional).
If you like, I can provide the modules (both 2-g dimmer and 2-g switch) and the .svg files.
.
Addendum:
I recently got a radar-based human presence sensor (like a PIR sensor, but with radar) TuYa ZY-M100-L which exposes “illuminance_lux” (instead of “illuminance” like a PIR sensor with lux I have).
Would it be possible to add ‘illuminance_lux’ to the Z2M app? (Presence-by-radar already works, like a PIR presence.)
I have only one so I can’t provide the device, but I can provide temporary acces to my Z2M Pi if that would be beneficial.
It seems I was too optimistic about the 1-gang dimmer. It can be switched on and off from Homey (via Z2M) but the dim level can’t be changed. Which is quite a bummer …
In the case of to illuminance_lux: I think I found a fix. In the capability mapping, Illuminance_lux is written with a capital I instead of an i (line 52).
Changing to lower case ‘i’ fixed it for a local install.
Another one for the wish list: the Ikea E1743 button.
This button exposes an ‘acion’ (enumeration) with the values on, off, brightness_move_down, brightness_move_up and brightness_stop. In de Z2M frontend is the option to add a ‘brightness diff’ to a move_up or move_down action (e.g. every 200 ms, increase brightness with 25).
I do have a button available.
BTW: it seems I fixed the dim level for 1-gang dimmers, by removing both the division and multiplication with a factor 100 from the capability mapping. Succesfully tested with 2 different types of dimmer (Tuya and Nordtronic).
It now reads: brightness: (val) => ['dim', Number(val) / 254, { brightness: Number(val) * 254 }],
There’s a bit of a delay in Homey though, as the level jumps back and forth for one time in the Homey GUI upon changing. But as far as I can tell that’s only a cosmetic inconvenience for the GUI.
V2.0: Greatly extended capability support, including buttons, actions, color lights. Added many flow cards.
Big thanks to @DickO who donated some special devices so I could integrate them. I also bought some new device types myself for testing and integration.
On my mmwave sensor, is see three capabilities. Only, for presence there is no trigger card (value presence changed). I can see it for lux and link quality. There is a tag for ‘presence’ to check within a logics-and card. Is it possible to also add the trigger for presence. That way i can respond on movement (besides zone activity).