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

Maybe a bug in the Examples File: AnyDevice #113

Closed
huddx01 opened this issue Sep 12, 2021 · 4 comments
Closed

Maybe a bug in the Examples File: AnyDevice #113

huddx01 opened this issue Sep 12, 2021 · 4 comments
Assignees
Labels

Comments

@huddx01
Copy link

huddx01 commented Sep 12, 2021

Describe The Bug:

State of a Security System is not written correctly when polling

To Reproduce:

I think it should be

     case "SecuritySystemTargetState":
         {
            writeData( device, characteristic, option );

            // Set to done
            writeData( device,"SecuritySystemCurrentState", option );

            break;
         }

instead of...

 case "SecuritySystemTargetState":
     {
        writeData( device, characteristic, option );

        // Set to done
        writeData( device,"SecuritySystemAlarmState", option );

        break;
     }
@ztalbot2000
Copy link
Owner

ztalbot2000 commented Sep 13, 2021 via email

@huddx01
Copy link
Author

huddx01 commented Sep 15, 2021

Hi.

I have tried to implement a securitysystem “dummy” device… which responds correctly.

So I tried to choose the AnyDevice script, which gets/sets the corresponding values….

Thank you so far…

@ztalbot2000
Copy link
Owner

ztalbot2000 commented Sep 15, 2021 via email

@ztalbot2000
Copy link
Owner

Hi I just released v5.1.1 fixing AnyDevice. I also created and tested the new example script SecuritySystem.js

The comments in the script has the config.json that I used as well. There is interesting information I also note in the script.The securitySystemTargetState does not align with the CurrentState. To ARM/DISARM you must run the script from the command line.

if you have further issues, just continue writing to this ticket, even though I will now close it.

take care,
John

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

No branches or pull requests

2 participants