Lights dont function properly
Closed this issue · 25 comments
In 1.8 i can turn a light off and never get it back on.
[11/17/2021, 14:21:43] [Security System] Error: Failed to change light state: Error: POST https://www.alarm.com/web/api/devices/lights/94428553-1201/turnOn failed: 423
at post (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:489:15)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at authenticatedPost (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:433:17)
at ADCPlatform.changeLight (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:909:5)
anyone else experiencing? still have this after the 1.11 patch installed via terminal. all other functions seem solid. can turn lights off, but cannot turn any on.
Also, prior to the reset issues if the code was modified with brightness=true it would get the lights to turn on consistently.
I'm also having this problem. I can turn off the light but it will not turn it back on
Any thoughts on the issue?
I'm also experiencing a similar issue with 1 of my 2 lights, which I thought was strange. One works flawlessly, the other one I can't turn on or off. Everything else works solid so far.
I've deleted this device from cache, but still not working.
[1/6/2022, 9:22:53 PM] [Security System] Updating light Master Light (96029166-1207), state=false, prev=true
[1/6/2022, 9:25:59 PM] [Security System] Error: Failed to change light state: Error: POST https://www.alarm.com/web/api/devices/lights//turnOn failed: 423
at post (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:489:15)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at authenticatedPost (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:433:17)
at ADCPlatform.changeLight (/homebridge/node_modules/homebridge-node-alarm-dot-com/src/index.ts:909:5)
I am having the same issue. Has anyone had success at all?
Same issue here i can turn all lights off but only can turn one light back on. Any solution to this issue?
For those having issues with lights I have two questions: 1) What type of lights are you trying to control? Z-wave devices directly communicating with your panel or a cloud to cloud integration (i.e., Lutron). 2) Are the devices on/off switches or dimmers?
I have a mix of both in my setup but primarily Lutron devices which are natively HomeKit supported (I exclude the ADC versions of my Lutron devices to not create dupes). I do have one z-wave on/off device directly communicating with my panel but haven't experienced any issues with it. Hence, I'm wondering if this is a dimmer related problem. I remember previous issues with the dimmer implementation.
Zwave to ADT panel no dimmers connected to alarm.com one light works all others don’t but all the same switches
Same issue here. Alarm.com. All Dimmable lights work. Regular non-dimmable lights can be turned off but not turned on
Error: Failed to change light state: Error: POST https://www.alarm.com/web/api/devices/lights/94329577-1211/turnOn failed: 423
at post (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:489:15)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at authenticatedPost (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:433:17)
at ADCPlatform.changeLight (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:909:5)
Any ideas appreciated
@kwallac has submitted a PR to correct this issue on the node-alarm-com repo (the interface module for this plugin). I can't test this PR but if some of the folks having issues could test and report back we can hopefully merge his fix.
I don't know if it is the best but you can install a PR directly with npm
npm install /#pull//head
so something like npm install node-alarm-dot-com/node-alarm-dot-com#pull/23/head
Try at your own risk.
The fix requires an extra parameter (isDimmer) to be passed to the node-alarm-dot-com method. I have a PR for the homebridge-node-alarm-dot-com plugin that does and have tested end-to-end and all works. Not sure how to manage the dependency though as it assumes the node-alarm-dot-com/node-alarm-dot-com#23 PR has been accepted as version 1.1.11
@kwallac I only see a PR for the node-alarm-dot-com interface nothing for home-bridge-node-alarm-dot-com?
Hi @ngori I went ahead and created #93
but as mentioned requires an update to the node-alarm-dot-com library per node-alarm-dot-com/node-alarm-dot-com#23
I've tested that it works with both types of lights (dimmable and non-dimmable)
Can someone please guide me through on how to implement the fix? I'm a complete newbie. I would highly appreciate that! I can reimburse you for your time! Thank you
@ChrArk If you are using Homebridge UI interface plugin you can click on the wrench, then "Install Previous Version", then from the version list the beta with the change implemented will be at the top.
@ngori Thank you again everything works fine now! Thank you to everyone who made all this possible and shared it with the public! One more question I ordered a Z-shield for the raspberry PI but it seem like I don't even need that? Can someone explain why and when its needed and when not? I'm assuming it functions similar to a hub which we have the IQ pad for correct?
I'm not familiar with the z-Shield but it looks like a Zigbee interface for Home Assistant. The IQ panel has only limited Zigbee functionality for use with the image sensors. It doesn't support other devices (lights, switches, outlets). The IQ panels do have decent z-wave functionality. So it just depends on what you are trying to do if you need the Z-Shield.
@ngori Thank you again everything works fine now! Thank you to everyone who made all this possible and shared it with the public! One more question I ordered a Z-shield for the raspberry PI but it seem like I don't even need that? Can someone explain why and when its needed and when not? I'm assuming it functions similar to a hub which we have the IQ pad for correct?