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

Add support for Bitron smoke detector 902010/24 #1063

Merged
merged 5 commits into from Jan 13, 2019

Conversation

ma-ca
Copy link
Contributor

@ma-ca ma-ca commented Dec 21, 2018

Add Bitron smoke detector 902010/24

{
        "config": {
            "on": true,
            "reachable": true
        },
        "ep": 1,
        "etag": "90f0140d0c8eaa982b3e7675ec28ab14",
        "manufacturername": "Bitron Home",
        "modelid": "902010/24",
        "name": "Alarm 18",
        "state": {
            "alarm": false,
            "lastupdated": "none",
            "lowbattery": false,
            "tampered": false
        },
        "type": "ZHAAlarm",
        "uniqueid": "00:12:4b:00:07:7f:13:44-01-0500"
    },

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 21, 2018

Why isn’t it exposed as ZHAFire? What Zone Type does it report? Even if it reports the correct type, I found deCONZ doesn’t always read this attribute early enough, and I ended up whitelisting the Model Identifiers, see

case IAS_ZONE_CLUSTER_ID:

@ma-ca
Copy link
Contributor Author

ma-ca commented Dec 21, 2018

You are right. I did read the IAS Zone cluster attributes and then searched for new devices again.

curl http://xxx/api/xxx/sensors -X POST

Now the the smoke detector has the type ZHAFire.

{
        "config": {
            "on": true,
            "reachable": true
        },
        "ep": 1,
        "etag": "0471718322305776bbf1c851f66fac49",
        "manufacturername": "Bitron Home",
        "modelid": "902010/24",
        "name": "Fire 19",
        "state": {
            "fire": false,
            "lastupdated": "none",
            "lowbattery": false,
            "tampered": false
        },
        "type": "ZHAFire",
        "uniqueid": "00:12:4b:00:07:7f:13:44-01-0500"
    },

@ma-ca
Copy link
Contributor Author

ma-ca commented Jan 2, 2019

I did add the Bitron smoke detector 902010/24 to the whitelist.

model identifier:
- 902010/21
- 902010/21A
- 902010/21B

Changed supported device from 902010/21A to 902010/21 in order to also support 902010/21B see issue dresden-elektronik#1100
@ma-ca
Copy link
Contributor Author

ma-ca commented Jan 8, 2019

Sorry for adding another commit to this PR that is not related to the smoke detector, but this was just a very small change to an existing line in the supported devices.

I changed 902010/21A to 902010/21 in order to also support 902010/21B.

{ VENDOR_NONE, "902010/21A", tiMacPrefix }, // Bitron: door/window sensor

@ma-ca
Copy link
Contributor Author

ma-ca commented Jan 11, 2019

@manup I would like to ask if there is anything missing or wrong in this PR that prevents from merging? I am asking because I would like to create some more PRs.

@manup
Copy link
Member

manup commented Jan 11, 2019

I am asking because I would like to create some more PRs.

I'm unsure, is the ZHAFire issue solved? Maybe prevent the ZHAAlarm to be created for certain model ids?

@ma-ca
Copy link
Contributor Author

ma-ca commented Jan 11, 2019

is the ZHAFire issue solved?

Yes, I have whitelisted the model Id in this commit baad884 in order to enforce the ZHAFire type even when the IAS_ZONE cluster attributes have not been read.

@ma-ca
Copy link
Contributor Author

ma-ca commented Jan 12, 2019

Add Bitron motion sensor 902010/22 to supported model Id list and whitelisted ZHAPresence type.

{
    "config": {
        "duration": 60,
        "on": true,
        "reachable": true
    },
    "ep": 1,
    "etag": "e2d1f50fca44ed1817e87a3455b18fed",
    "manufacturername": "Bitron Home",
    "modelid": "902010/22",
    "name": "Presence 23",
    "state": {
        "lastupdated": "2019-01-12T15:43:32",
        "lowbattery": false,
        "presence": false,
        "tampered": false
    },
    "swversion": "20150216",
    "type": "ZHAPresence",
    "uniqueid": "00:12:4b:00:01:ee:12:b3-01-0500"
}

@manup manup merged commit 8327ef3 into dresden-elektronik:master Jan 13, 2019
@lyncker
Copy link

lyncker commented Mar 10, 2021

Iam just trying to pair a 902010/24 in the newest version of deconz, but it is not recognized. I did not find any information how to reset or set the device in the pairmode... pressing 20 seconds the button does not help... the sensor is not beeing found and the debug log does not show any information ...
maybe you can help me how to handle such a device?

@ma-ca
Copy link
Contributor Author

ma-ca commented Mar 11, 2021

You need to press the button 10 seconds, not 20 seconds.

https://manuals.smabit.eu/len/av2010_24.html#c

Hold the function button on the top of the sensor for about 10 seconds until the red LED illuminates briefly once.
During the search, the LED will light red once every 10 seconds. If the LED flashes 2 times, the device has successfully logged on to your Smart Home system.

@lyncker
Copy link

lyncker commented Mar 11, 2021

perfect , thanks... that worked ...:)

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

Successfully merging this pull request may close these issues.

None yet

4 participants