Skip to content
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

Ikea Parasoll #7417

Closed
1 task done
johannescramer opened this issue Dec 6, 2023 · 4 comments · Fixed by #7445
Closed
1 task done

Ikea Parasoll #7417

johannescramer opened this issue Dec 6, 2023 · 4 comments · Fixed by #7445

Comments

@johannescramer
Copy link

Is there already an existing issue for this?

  • I have searched the existing issues and there is none for my device

Product name

Parasoll

Manufacturer

IKEA of Sweden

Model identifier

PARASOLL Door/Window Sensor

Device type to add

Sensor

Node info

parasoll node info

Endpoints and clusters

clusters

Basic

parasoll cluster info

Further relevant clusters

Power Configuration

image

IAS Zone

Zone Status is 0x0000 when closed and 0x0001 when open.
image

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 6, 2023

Could you please read the attribute and re-post screenshots with the values. Make sure to wake the device (by moving the magnet) while reading.

Not yet available here in NL, unfortunately. They also announced a new motion sensor and a leak sensor, see https://www.ikea.com/global/en/newsroom/innovation/parasoll-badring-vallhorn-smart-sensors-231128/.

Looks like a regular IAS Zone contact sensor on endpoint 0x02, which can control lights directly from endpoint 0x01. Doesn't look like there's anything to expose from endpoint 0x01, other than the battery. If I'm being pure, this device would be exposed as two sensors resources:

  • A ZHAOpenClose with uniqueid ending in -02-500. Interesting to see if the device has tampered detection, and if it does periodic and restore reports. Otherwise, we might need an additional binding and attribute report configuration to work around that. We would need to check whether it honours group bindings from the On/Off cluster, and, if so, expose config/group.
  • A ZHABattery with uniqueid ending in -01-0001. Alternatively, the battery could be exposed as config/battery on the ZHAOpenClose resource, as is done on most other sensors resources (although they typically only correspond to a single endpoint). Also need to check whether it reports battery in 0.5% (as per the standard, and with most recent IKEA firmwares) or in full % (as older IKEA firmwares).

@johannescramer
Copy link
Author

Oh, sorry. I'm new to this. I thought it had read the attributes, but apparently not all of them.

Basic cluster attributes

image

Power Configuration

image

Poll control

image

Diagnostics

image

Ikea Specific

image

IAS Zone Basic

image

IAS Zone

image

I hope this is all you need. If you got any other stuff I should try, let me know. I am willing to try stuff, but have limited knowledge about deconz and zigbee in general.

@johannescramer
Copy link
Author

by the way, if you are going to IKEA, it is worth it to ask someone. My IKEA (Germany) got the delivery, but didn't know where to put them. They got them from storage for me.

@SwoopX SwoopX linked a pull request Dec 11, 2023 that will close this issue
@Mimiix Mimiix mentioned this issue Dec 29, 2023
1 task
@hyper2910
Copy link

no status change via mqtt

STATE is evrytime INITIALIZED

as Reading also only the following coming

Readings
IODev | deCONZ | 2023-12-31 12:46:27 -- | -- | -- attrTemplateVersion | Xiaomi_Aqara_MCCGQ11LM_Window_Door_Sensor_20211015 | 2023-12-31 13:06:25 battery | 94 | 2023-12-31 13:03:26 batteryPercent | 94 | 2023-12-31 13:03:26 reachable | 1 | 2023-12-31 13:03:26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants