New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API shows light is on but it is off and should be off #1720
Comments
Hello, have you something like websocket log (less informations but easy to obtain) or deconz event log ? |
Hi Smanar, I managed to get deCONZ to log and here is the result: The motion happens at 20:30:53:579 but I got confused on who tells who to do what. The RPi is 127.0.0.1 and .168.100 is from where I access node-red.
|
I started from scratch and just added all lights with on/off buttons. Then inserted the motion sensor and the event listener. The API shows all lights are off, after the motion sensor (not connected) is triggered all lights show that they are on by the API (and you can also see the event gets triggered) but they are not. Can anyone reproduce this? |
And you haven't changed something in phoscon ? No groups ? I can't understand what can make the api send a change notification but without change in reality ... |
Phoscon looks empty I made some groups at first but I deleted them. Every time I enter the mainpage it asks me to Create first group. But it seems like the remote made a light group (see below). I tried with node-red closed and all lights turns on in the API when activating the motion sensor (but the lights stay off) so it is not node-red related. What else can I check? This is the output from the API for groups:
|
Yeah it's normal for the remote, I have same. |
Yeah it is really weird. I'm running headless but ssh -X to the rescue. Wow, the deCONZ X app is amazing compared to the web interface :) So many ways to f**k up things :). But as you suspected the 0006 cluster shows exactly what the lamp is doing so it shows the right value... So might be a bug then? |
I think yes, it can't come from node-red, and you have a clean phoscon config, but it's holidays period ^^, need to wait for a dev. |
I just did a complete re-install of my system to be sure that I didn't change anything that I had forgot and I got the same results. I started with the 2019-07-10-raspbian-buster-lite image on a RPi 3B
then followed the instructions here https://phoscon.de/en/conbee/install#raspbian to step 5 then
and a reboot, using node-red-contrib-deconz to control. Let's hope the devs find the problem because now the re-building of my homeautomation has stopped:( But still, thanks for the amazing sw & hw! |
I think I have found another issue, with the same bug than you #1676 , your motion detector is the ikea one ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi,
I bought the Conbee 2 and started rebuilding my homeautomation system. I installed the Phoscon App on a Raspberry Pi 3B and setup all my Ikea lights and remotes/motion sensor in the Phoscon App (no groups no nothing in the app). Then I started using node-red to control everything. Everything works perfectly but I think I have found a bug. The motion sensor should turn on the entrance light when somebody enters and that works. But when I started building the UI (using node-red-ui) I noticed that when the motion sensor turns on the wanted light the API show that also another light turns on even if it is not. What could be the problem?
This how it looks before I walk pass the motion sensor
and after, light 3 should be on and is and light 4 should be off and is but the API output shows on: true
Thanks in advance!
Nicke
The text was updated successfully, but these errors were encountered: