schmupu/iobroker.contactid

Contact ID server for burglar alarm system

iobroker.contactid's Issues

Verify Compact mode for your adapter

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

ACK-invalid Format

My Lupusec XT2 (incl. Dongle) does not receive a correct ACK message and repeat sending the CID message

XT2 Config: ip://[email protected]:2001/CID

ioBrocker.contactid Subcirber: CID1
ioBrocker.contactid Subcirber: Lupusec XT2 (and alternatively tested as Lupusec XT2 Plus)

ioBroker Log: contactid.0 | <date&time> | 192.168.x.1:48646 sending following message: [CID2 181401010012843]

XT2 Event Log: Error | Reporter | url='ip://[email protected]:5000/CID', ret=-404, reason='ACK-ungültiges Format', event=760, text='Area 0 Zone 0 : Home Automation'

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/schmupu/ioBroker.contactid

• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2019 Thorsten Stueben [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019 Thorsten Stueben [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Please add your adapter to ioBroker.discovery

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/schmupu/ioBroker.contactid

• [E402] Types of adapter in latest repository and in io-package.json are different "alarm" !== "network"
• [E422] Types of adapter in stable repository and in io-package.json are different "alarm" !== "network"
• [E816] file tsconfig.json found in repository, but not found in .npmignore

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Link Contact ID protocol does not exist anymore

Update stable version in repo from 1.0.1 to 1.0.2

Think about update stable version to 1.0.2

Version: stable=1.0.1 (NaN days old) => latest=1.0.2 (84 days old)
Installs: stable=4 (10.26%), latest=8 (20.51%), total=39
Click to edit

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/schmupu/ioBroker.contactid

• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2019 Thorsten Stueben [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019 Thorsten Stueben [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Please implement discovery function

Like here: https://github.com/ioBroker/ioBroker.discovery/blob/master/lib/adapters/fhem.js

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Defender ST-7 Skynet Italia incorrect format

Describe the bug
Not a bug really, but different messaging for another alarm

To Reproduce
Steps to reproduce the behavior:
Actually you have to buy one to see the messaging.

Expected behavior
The alarm should sent its id first but instead it sends it last

Screenshots & Logfiles
Log from iobroker: (ip addresses are wrong for the obvious reasons)

contactid.0 | 2020-02-15 17:20:11.992 | info | (18233) 10.10.10.10:3635 sending following message: 9701002F"ADM-CID"2222R0L0#13E3186[#13E3186|1302 01 000]
contactid.0 | 2020-02-15 17:20:11.986 | info | (18233) connection from 10.10.10.10:3634 closed
contactid.0 | 2020-02-15 17:20:11.984 | info | (18233) 10.10.10.10:3634 sending following message: 9776002F"ADM-CID"2221R0L0#13E3186[#13E3186|1302 01 000]
contactid.0 | 2020-02-15 17:20:11.978 | info | (18233) connection from 10.10.10.10:3633 closed
contactid.0 | 2020-02-15 17:20:11.976 | info | (18233) 10.10.10.10:3633 sending following message: 575A002F"ADM-CID"2220R0L0#13E3186[#13E3186|1302 01 000]
contactid.0 | 2020-02-15 17:20:11.971 | info | (18233) connection from 10.10.10.10:3632 closed
contactid.0 | 2020-02-15 17:20:11.969 | info | (18233) 10.10.10.10:3632 sending following message: 705F002F"ADM-CID"2219R0L0#13E3186[#13E3186|1302 01 000]

Versions:

• Adapter version: <1.0.0>
• JS-Controller version: 2.2.8
• Node version: 10.19.0
• Operating system: ubuntu 18.04 headless (container on proxmox). Its a fresh install with nothing else on it. Not even another adapter

Additional context
The username (or userid if you may) is 13E3186
You can see it sends it last along with some numbers in brackets. I don't know if it's from the alarm or from the log of broker since it's the first time I use it and I set it up only for getting messages from the alarm and send on telegram if something bad happens. It won't do anything else.
Apart from the formatting which is incorrect and I assume that's the reason it gets disconnected, it also floods the broker with reports. And I mean it FLOODS with messages. For about 3-4 minutes it had 4-5.000 messages. Is that normal? The alarm was armed and not doing anything.

Thanks in advance!

edit: in the CMS setting of the alarm, it has the following :
Server Address: 10.10.10.11 (the address of the broker)
Server Port: 50000
ID account: 13E3186
Password:
Heartbeat times(1-255s): 60
I've left the password empty on purpose since it wouldn't work anyway with your adapter. I assume the rest are okay. (?)

Please check ioBroker.contactid with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Please add to stable repository if shown working for users