Parasoll slow response #36
Comments
|
The log that you posted is that from the doorsensor, the device type shows it to be a motion sensor |
|
I have a flue, so not 100% sharp :-) 2024-04-17 17:56:28.026 DEBUG (MainThread) [custom_components.dirigera_platform] controller update... |
|
I have two Parasoll sensors, they also are quite slow to respond, as I said on #20 (comment) Maybe this might help: |
|
I hope you feel better soon. Try 1.5.3 hub even for open close sensor now processed. Do test and and if it works as expected please close the issue |
|
Status changes instantly in HA when opening and closing the door. Thx a lot Sanjoy, awesome! |
|
Amazing work! Thank you! |
|
Thank you mgums, I will reach out to you for debugging help that I might need |
|
Hi Sanjoy. This night a saw one instance of doormen-detection not being registered in HA. It was visible in the IKEA app though. One of these days I will do more testing and debug tracing when trying to capture such an event. |
|
Please do , not aware of what doormen-detection is
…On Fri, Apr 19, 2024 at 12:25 PM mgums ***@***.***> wrote:
Hi Sanjoy. This night a saw one instance of doormen-detection not being
registered in HA. It was visible in the IKEA app though. One of these days
I will do more testing and debug tracing when trying to capture such an
event.
Regards, Marco
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2X3CWPYEZPMQEPO3Q4UWTY6C5WHAVCNFSM6AAAAABGLUXRKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVHA3TONBXGI>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
I notice with the Parasoll doorsensor, that not every event is captured via Dirigera integration or it comes with a delay. In the IKEA iPhone App I see the door open and close actions immediately.
Is there some sort of delay implemented maybe? When I open the door and close it fast, no change is recorded in HA. In the IKEA app the change is there.
Next to that I see the following in the debug logs, so maybe more is going on?
2024-04-17 17:53:08.243 DEBUG (Thread-2) [custom_components.dirigera_platform] rcvd message : {"id":"891622ef-1e1e-4695-8d61-8039e0b83342","time":"2024-04-17T15:53:08.000Z","specversion":"3.150.0","source":"urn:com:ikea:homesmart:iotc:zigbee","type":"deviceStateChanged","data":{"id":"35342df4-c2f1-4f38-a34e-4b8704e9ebd3_1","type":"sensor","deviceType":"motionSensor","createdAt":"2024-04-15T11:37:10.000Z","isReachable":true,"lastSeen":"2024-04-17T17:50:08.000Z","attributes":{"isDetected":false,"sensorConfig":{"scheduleOn":false,"onDuration":120,"schedule":{"onCondition":{"time":"22:00"},"offCondition":{"time":"06:00"}}},"circadianPresets":[]},"remoteLinks":[]}}
2024-04-17 17:53:08.243 DEBUG (Thread-2) [custom_components.dirigera_platform] Setting 35342df4-c2f1-4f38-a34e-4b8704e9ebd3_1 reachable as True
2024-04-17 17:53:08.244 DEBUG (Thread-2) [custom_components.dirigera_platform] device type of message motionSensor
2024-04-17 17:53:08.245 DEBUG (Thread-2) [custom_components.dirigera_platform] setting is_detected to False
2024-04-17 17:53:08.245 DEBUG (Thread-2) [custom_components.dirigera_platform] attribute sensorConfig not in list of device type motionSensor, ignoring update...
2024-04-17 17:53:08.245 DEBUG (Thread-2) [custom_components.dirigera_platform] attribute circadianPresets not in list of device type motionSensor, ignoring update...
The text was updated successfully, but these errors were encountered: