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

Device integration Bitron AV2010/21B window sensor with ext.contact #1100

Closed
Ronoon opened this issue Jan 7, 2019 · 7 comments
Closed

Device integration Bitron AV2010/21B window sensor with ext.contact #1100

Ronoon opened this issue Jan 7, 2019 · 7 comments

Comments

@Ronoon
Copy link

Ronoon commented Jan 7, 2019

bitron5
Could you pls integrate the window sensor

bitron 1
bitron2
bitron3
bitron4

ma-ca added a commit to ma-ca/deconz-rest-plugin that referenced this issue Jan 8, 2019
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
@Ronoon Ronoon changed the title Device intergration Bitron AV2010/21B window sensor with ext.contact Device integration Bitron AV2010/21B window sensor with ext.contact Jan 13, 2019
@Ronoon
Copy link
Author

Ronoon commented Jan 13, 2019

Integration is about 50% done cause only the "Namespace" is recognized but there is something missing in this part or somewhere else:

            case IAS_ZONE_CLUSTER_ID:
            {
                if (modelId.startsWith(QLatin1String("CO_")))                     // Heiman CO sensor
                {
                    fpCarbonMonoxideSensor.inClusters.push_back(ci->id());
                }
                else if (modelId.startsWith(QLatin1String("DOOR_")))              // **Heiman door/window sensor**
                {
                    fpOpenCloseSensor.inClusters.push_back(ci->id());
                }
                else if (modelId.startsWith(QLatin1String("PIR_")) ||             // Heiman motion sensor
                         modelId.startsWith(QLatin1String("902010/22")))          // Bitron motion sensor
                {
                    fpPresenceSensor.inClusters.push_back(ci->id());
                }
                else if (modelId.startsWith(QLatin1String("GAS_")) ||             // Heiman gas sensor
                         modelId.startsWith(QLatin1String("SMOK_")) ||            // Heiman fire sensor
                         modelId.startsWith(QLatin1String("902010/24")) ||        // Bitron smoke detector
                         modelId.startsWith(QLatin1String("lumi.sensor_smoke")))  // Xiaomi Mi smoke sensor

Missing are the integration for 902010/21 +/32

In the commit of Ma Ca was this originally integratet but there is also nothing anymore

@Ronoon
Copy link
Author

Ronoon commented Jan 14, 2019

Just got the including done so the 902010/21 will show up in the API and Tada its working
Just added the line for the 902010/21 into the de_web_plugin.cpp as shown below:

case IAS_ZONE_CLUSTER_ID:
{
if (modelId.startsWith(QLatin1String("CO_"))) // Heiman CO sensor
{
fpCarbonMonoxideSensor.inClusters.push_back(ci->id());
}
else if (modelId.startsWith(QLatin1String("DOOR_")) || // Heiman door/window sensor
modelId.startsWith(QLatin1String("902010/21"))) // Bitron window sensor
{
fpOpenCloseSensor.inClusters.push_back(ci->id());
}
else if (modelId.startsWith(QLatin1String("PIR_")) || // Heiman motion sensor
modelId.startsWith(QLatin1String("902010/22"))) // Bitron motion sensor

manup added a commit that referenced this issue Jan 18, 2019
@manup
Copy link
Member

manup commented Jan 18, 2019

Thanks for figuring this out, I've added this to the repository.

@Ronoon
Copy link
Author

Ronoon commented Jan 22, 2019

Well thx for the integration of this sensor, maybe you could integrate it into the visible part of Phoscon so that it could be used through the app.
Also there is this little issue with the timing problem about the sliders in the app.....

@manup
Copy link
Member

manup commented Feb 2, 2019

The sensor should be visible in 2.05.58, can you please check if it works?

@Ronoon
Copy link
Author

Ronoon commented Feb 2, 2019

Thx again for the integration also it is shown in the sensors tab and working e.g. shows the status open/closed in the Phoscon app

@stale
Copy link

stale bot commented Jun 2, 2019

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.

@stale stale bot added the stale label Jun 2, 2019
@stale stale bot closed this as completed Jun 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants