@eLRIC I’m seeing the same issue with its first generation version (which is essentially the same thing). It’s near my zigate, so that’s not the issue.
I have it configured as a sensor with default_state event. However, the same applies to the switch version I tried.
It says “presence detected” but never goes back to an “empty room” / “nothing detected” state.
Is that state something we have to reset through an automation ourselves? (Let’s say after a minute for example?)
Also… Does anyone know if this sensor also reports light intensity? Lumens or anything else?
I configure them as momentary switches. I’ll provide an example tomorrow
regarding the status not sent, it happened to me with outdoor sensors as well … maybe they don’t like low temperatures
When detection occurs, the switch representation in HA will go from OFF to ON, and switch back 15 secs to OFF. (you can modify ZGT_AUTOTOGGLE_DELAY in zigate/const.py if you want another delay)
Your project and Zigate prevented me from having to get the proprietary Xiaomi gateway. While I don’t think they are worse than, say, Google… I don’t like the idea of anyone having a connection into my home.
Now I just need to find some cheap light sensors because I don’t think the “presence sensors” from Xiaomi report light.
Hello,
can you advise me what I am doing wrong? I have successfully added ZiGate component to Hassio and Xiaomi Motion sensors. My configuration file looks like this
Currently running HA 0.63.3 with python 3.6.4 on a docker image without trouble …
Maybe have a look at your sensor.yaml file (or configuration.yaml) , check if there is a setup attribute somewhere …
~/.homeassistant/custom_components/ directories are up to date.
if I remove ~/.homeassistant/custom_components/sensor then the error vanishes.
I’m upgrading from an old rpi to an atom pc with ubuntu bionic on it. the same config is still working on the rpi, the only difference I can see for now is the python version.
I can see the zigate platform is active, it receives events. switch component also errors with the same message.
Maybe it’s just me, but I don’t see why I should take the trouble to block a closed, proprietary, single manufacturer hub when I can get an open, general purpose hub to do basically the same thing as the proprietary one.
Unless you see a good feature on the hub that I can’t get with Zigate…?
ahh… this drives me crazy. Maybe I am doing something wrong? I am integrating sensors with ZiGate by using NXP TestGUI by following the steps that are described on ZiGate page?
One more thing whenever I connect ZiGate to PC and run TestGUI app it shows that sensors are working. For instance when motion sensor detects movement I receive this message in TestGUI app:
I will use the momentary parameters (usefully advice)
The sensor seems not working properly.
The sensor is in my mailbox and it has no detected today letters.
It seems it need enough “lumens” to work …
If I open the mailbox, with the flashlight now the sensor work, but I will not asking my postman to work with a flashlight the day