ptz0n/homebridge-verisure

 Platform plugin for Homebridge allowing to manage and control Verisure devices.

homebridge-verisure's Issues

Support for hoobs

Just moved my homebridge setup from my Mac to a product called hoobs (amazing).
It simplifies the whole homebridge experience but needs this:

https://github.com/hoobs-org/HOOBS/wiki/6.4-Developing-Plugins

To be able to configure a plug in without having to touch the config file. I have the plug in installed already but had to add it manually. Not sure how much work that’s needed but could be beneficial for future users.

Possibility to hide change state for alarm?

Is it possible to hide state change for the alarm? I find it insecure to have that as a switch in Home on iOS.

TypeError: Cannot read property 'UUID' of null

Today, I made a fresh install of homebridge. When adding verisure I got the following issue:

There is a TypeError when initializing SMARTCAMERA1, while according to the readme, it is supported. Now my homebridge won't start without deleting the SMARTCAMERA (temporary) from my verisure system

[9/14/2017, 7:43:33 PM] ---
[9/14/2017, 7:43:34 PM] Loaded plugin: homebridge-verisure
[9/14/2017, 7:43:34 PM] Registering platform 'homebridge-verisure.verisure'
[9/14/2017, 7:43:34 PM] ---
[9/14/2017, 7:43:34 PM] Loaded config.json with 3 accessories and 1 platforms.
[9/14/2017, 7:43:34 PM] ---
[9/14/2017, 7:43:34 PM] Loading 1 platforms...
[9/14/2017, 7:43:34 PM] [Alarm] Initializing verisure platform...
[9/14/2017, 7:43:34 PM] Loading 3 accessories...
[9/14/2017, 7:43:34 PM] [Woonkamer Speakers] Initializing Sonos accessory...
[9/14/2017, 7:43:34 PM] [Keuken Speakers] Initializing Sonos accessory...
[9/14/2017, 7:43:34 PM] [verwarming] Initializing NefitEasy accessory...
Load homebridge-verisure.verisure
[9/14/2017, 7:43:34 PM] [Woonkamer Speakers] Found a playable coordinator device at 192.168.178.18 in zone 'Woonkamer' for accessory 'Woonkamer Speakers' in accessory room 'Woonkamer'
[9/14/2017, 7:43:34 PM] [Keuken Speakers] Found a playable coordinator device at 192.168.178.29 in zone 'Keuken' for accessory 'Keuken Speakers' in accessory room 'Keuken'
[9/14/2017, 7:43:36 PM] [Alarm] Initializing platform accessory 'Rökdetektor (zolder)'...
[9/14/2017, 7:43:36 PM] [Alarm] Initializing platform accessory 'Rökdetektor (hal)'...
[9/14/2017, 7:43:36 PM] [Alarm] Initializing platform accessory 'SMARTCAMERA1 (Woonkamer)'...
[9/14/2017, 7:43:36 PM] [Alarm] Device SMARTCAMERA1 is not yet supported
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:138
    if (existing.UUID === service.UUID) {
                                 ^

TypeError: Cannot read property 'UUID' of null
    at Accessory.addService (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:138:34)
    at /usr/lib/node_modules/homebridge/lib/server.js:418:19
    at Array.forEach (native)
    at Server._createAccessory (/usr/lib/node_modules/homebridge/lib/server.js:402:14)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:364:32)
    at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
    at /usr/lib/node_modules/homebridge-verisure/index.js:126:9
    at /usr/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:79:7
    at Request._callback (/usr/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:27:17)
    at Request.self.callback (/usr/lib/node_modules/homebridge-verisure/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at Request.<anonymous> (/usr/lib/node_modules/homebridge-verisure/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/homebridge-verisure/node_modules/request/request.js:1091:12)

Lock error when using Siri to lock & unlock homebridge-verisure v1.7.0-rc.1

Working:
Buttons in Home app works correctly.
Voice commands locks & unlocks smartlock correctly.
Push messages are correct.

Erroneous:
Siri reports locking & unlocking failed.
Home app needs to be restarted to reflect the true state of the Smartlock.

Video of the problem:
https://youtu.be/UqI8YclttoA

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from 22.5.1 to 22.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v22.6.0

22.6.0 (2019-05-22)

Features

• rules: add no-commented-out rule (#262) (14d83ef)

Commits

The new version differs by 9 commits.

• 14d83ef feat(rules): add no-commented-out rule (#262)
• 83ff198 chore: migrate no-jest-import to typescript (#259)
• 718c08c chore: upgrade @typescript-eslint
• ca2aa27 chore: port lowercase-name to TypeScript (#258)
• 3df0058 chore(ci): run danger with lts version of node
• 48e3a59 chore: precompile with babel (#257)
• 8670804 chore: bump deps
• 05eb11a chore: fix lint error
• dff6446 docs: link to eslint-plugin-jest-formatting

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Smoke detector as an actual smoke detector

Currently the Verisure smoke detector shows up as a temperature and humidity sensor in HomeKit. Would it be possible to define it as an actual HomeKit smoke detector as well?

Possibility to change auto lock status on/off with a switch

It would be nice feature to to disable / enable auto locking of the Yale doorman smart lock via HomeKit switch. This is doable via Verisure API.

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from 22.3.0 to 22.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v22.3.1

22.3.1 (2019-03-12)

Bug Fixes

• no-identical-title: not reporting when using backticks (#237) (4f8ef6d), closes #232

Commits

The new version differs by 3 commits.

• 4f8ef6d fix(no-identical-title): not reporting when using backticks (#237)
• 42d2d42 chore: refresh lockfile
• 3a1dc2d chore(package): update to [email protected] (#228)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Pass email and password as environment variables

It would be nice if email, password and other sensitive values could be read from environment variables.

Something like:

$ [email protected] VERISURE_PASSWORD=password123 homebridge

It would allow for checking in config.json files without sensitive key/values.

Error giid

Hi, trying to start but get this error message:
[2017-3-24 14:57:14] Loading 0 accessories...
Load homebridge-verisure.verisure
/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:50
giid = typeof installation == 'string' ? installation : installation.giid

TypeError: Cannot read property 'giid' of undefined

//Björn

Starting without connection to Verisure

This will result in the plugin starting, but zero accessories exposed. Might also be the cause of HomeKit loosing configuration for given accessories when this happens.

Idéa: Kill Homebridge when we cannot initiate the Verisure platform. Process managers should try restarting.

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from 22.20.0 to 22.20.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v22.20.1

22.20.1 (2019-10-26)

Bug Fixes

• valid-title: check if node has arguments first (#436) (e961e21)

Commits

The new version differs by 2 commits.

• e961e21 fix(valid-title): check if node has arguments first (#436)
• 7eae625 docs: fix valid-title documentation (#434)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Yale Doorman "Status"

Yale Doorman Lock/Unlock Is running perfect.

My door are closing automatically after few seconds. And then the door is displayed as open in Apple Home app.

Can you add check for door status?

I think you can use my earlier information when you added Yale Doorman Lock/Unlock.

Bridged accessory not reachable

This is more a question on help to find out what's going wrong.

Running homebridge-verisure 1.8.0

It starts up fine - and I can both see status, get updates and also control it (turn alarm on and off etc).

But after a while - I get a problem.

In the eve iOS app it says "The bridged accessory is not reachable. Make sure Wi-Fi is enabled and try again".

In the iOS home app it says only "No response".

But only for the bridged verisure accessories - the bridged netatmo, harmony and nest accessories are all working fine.

If I look in the logs for homebridge all I see is lots of info lines like:

2018-6-14 11:24:57] [Verisure] info Alarm (Havna allé): Getting current alarm state.
[2018-6-14 11:24:57] [Verisure] info Alarm (Havna allé): Getting current alarm state.
[2018-6-14 11:24:57] [Verisure] info Siren (Inngangspartiet): Getting current temperature value.
[2018-6-14 11:24:57] [Verisure] info Inngangsdør: Getting current sensor state.
[2018-6-14 11:24:57] [Verisure] info PIR2 (Inngangspartiet): Getting current temperature value.
[2018-6-14 11:25:51] [Verisure] info Alarm (Havna allé): Getting current alarm state.
[2018-6-14 11:25:51] [Verisure] info SmartLock (Inngangsdør): Getting current lock state.

From that it looks to me as if homebridge is running fine.

Any ideas how to debug this further given that it's only the verisure ones that are getting into this state?

Lock status not updating if using lock without HomeKit.

Goal: To use both HomeKit and Verisure App/Tags/Keypad with Yale Doorman and still have always lock/unlock status updates on Homekit.

Solution: Add simple polling with customized interval

Cannot arm away when arm state is home

The API does not allow this and the resource return an error.

Fix: When switching between armed states, first disarm.

AutoLockState

The AutoLockState service is always unreachable while the lock itself is reachable.

No polling for magnetic sensor values

Everything is showing up and working except the magnetic sensors. If I open a door it's not reflected in the home app. Poll interval is set to 60

TypeError: Cannot read property 'filter' of undefined

I've added the platform to my array of platforms with the following structure:

{
  "platform" : "verisure",
  "name" : "Verisure",
  "email": "[email protected]",
  "password": "secret",
  "alarmCode": "nnnn"
}

Homebridge stopped responding after this addition, and running it in debug mode gives me the following errors:

[2/16/2019, 8:34:36 AM] [Verisure] Initializing platform accessory 'Alarm (my address)'...
[2/16/2019, 8:34:36 AM] [Verisure] TypeError: Cannot read property 'filter' of undefined
    at Alarm.getServices (/usr/lib/node_modules/homebridge-verisure/lib/accessories/alarm.js:90:7)
    at Server._createAccessory (/usr/lib/node_modules/homebridge/lib/server.js:378:36)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:364:32)
    at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
    at verisure.getToken.then.then.then (/usr/lib/node_modules/homebridge-verisure/lib/platform.js:98:9)
    at process._tickCallback (internal/process/next_tick.js:109:7)
(node:25714) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: This callback function has already been called by someone else; it can only be called one time.

Maybe this is an issue for https://github.com/ptz0n/node-verisure but since I'm using this plugin I figured I might as well add the issue here.

Let me know if I can provide any further details.

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from 6.5.1 to 6.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v6.6.0

• 39dfe08 Update: false positives in function-call-argument-newline (fixes #12123) (#12280) (Scott O'Hara)
• 4d84210 Update: improve report location for no-trailing-spaces (fixes #12315) (#12477) (Milos Djermanovic)
• c6a7745 Update: no-trailing-spaces false negatives after comments (fixes #12479) (#12480) (Milos Djermanovic)
• 0bffe95 Fix: no-misleading-character-class crash on invalid regex (fixes #12169) (#12347) (Milos Djermanovic)
• c6a9a3b Update: Add enforceForIndexOf option to use-isnan (fixes #12207) (#12379) (Milos Djermanovic)
• 364877b Update: measure plugin loading time and output in debug message (#12395) (Victor Homyakov)
• 1744fab Fix: operator-assignment removes and duplicates comments (#12485) (Milos Djermanovic)
• 52ca11a Fix: operator-assignment invalid autofix with adjacent tokens (#12483) (Milos Djermanovic)
• 0f6d0dc Fix: CLIEngine#addPlugin reset lastConfigArrays (fixes #12425) (#12468) (Toru Nagashima)
• 923a8cb Chore: Fix lint failure in JSDoc comment (#12489) (Brandon Mills)
• aac3be4 Update: Add ignored prop regex no-param-reassign (#11275) (Luke Bennett)
• e5382d6 Chore: Remove unused parameter in dot-location (#12464) (Milos Djermanovic)
• 49faefb Fix: no-obj-calls false positive (fixes #12437) (#12467) (Toru Nagashima)
• b3dbd96 Fix: problematic installation issue (fixes #11018) (#12309) (Toru Nagashima)
• cd7c29b Sponsors: Sync README with website (ESLint Jenkins)
• 8233873 Docs: Add note about Node.js requiring SSL support (fixes #11413) (#12475) (Nicholas C. Zakas)
• 89e8aaf Fix: improve report location for no-tabs (#12471) (Milos Djermanovic)
• 7dffe48 Update: Enable function string option in comma-dangle (fixes #12058) (#12462) (YeonJuan)
• e15e1f9 Docs: fix doc for no-unneeded-ternary rule (fixes #12098) (#12410) (Sam Rae)
• b1dc58f Sponsors: Sync README with website (ESLint Jenkins)
• 61749c9 Chore: Provide debug log for parser errors (#12474) (Brad Zacher)
• 7c8bbe0 Update: enforceForOrderingRelations no-unsafe-negation (fixes #12163) (#12414) (Sam Rae)
• 349ed67 Update: improve report location for no-mixed-operators (#12328) (Chiawen Chen)
• a102eaa Fix: prefer-numeric-literals invalid autofix with adjacent tokens (#12387) (Milos Djermanovic)
• 6e7c18d Update: enforceForNewInMemberExpressions no-extra-parens (fixes #12428) (#12436) (Milos Djermanovic)
• 51fbbd7 Fix: array-bracket-newline consistent error with comments (fixes #12416) (#12441) (Milos Djermanovic)
• e657d4c Fix: report full dot location in dot-location (#12452) (Milos Djermanovic)
• 2d6e345 Update: make isSpaceBetweenTokens() ignore newline in comments (#12407) (YeonJuan)
• 84f71de Update: remove default overrides in keyword-spacing (fixes #12369) (#12411) (YeonJuan)
• 18a0b0e Update: improve report location for no-space-in-parens (#12364) (Chiawen Chen)
• d61c8a5 Update: improve report location for no-multi-spaces (#12329) (Chiawen Chen)
• 561093f Upgrade: bump inquirer to ^7.0.0 (#12440) (Joe Graham)
• fb633b2 Chore: Add a script for testing with more control (#12444) (Eric Wang)
• 012ec51 Sponsors: Sync README with website (ESLint Jenkins)
• 874fe16 New: pass cwd from cli engine (#12389) (Eric Wang)
• b962775 Update: no-self-assign should detect member expression with this (#12279) (Tibor Blenessy)
• 02977f2 Docs: Clarify eslint:recommended semver policy (#12429) (Kevin Partington)
• 97045ae Docs: Fixes object type for rules in "Use a Plugin" (#12409) (Daisy Develops)
• 24ca088 Docs: Fix typo in v6 migration guide (#12412) (Benjamim Sonntag)
• b094008 Chore: update version parameter name (#12402) (Toru Nagashima)
• e5637ba Chore: enable jsdoc/require-description (#12365) (Kai Cataldo)
• d31f337 Sponsors: Sync README with website (ESLint Jenkins)
• 7ffb22f Chore: Clean up inline directive parsing (#12375) (Jordan Eldredge)
• 84467c0 Docs: fix wrong max-depth example (fixes #11991) (#12358) (Gabriel R Sezefredo)
• 3642342 Docs: Fix minor formatting/grammar errors (#12371) (cherryblossom000)
• c47fa0d Docs: Fix missing word in sentence (#12361) (Dan Boulet)
• 8108f49 Chore: enable additional eslint-plugin-jsdoc rules (#12336) (Kai Cataldo)
• b718d2e Chore: update issue template with --eslint-fix flag (#12352) (James George)
• 20ba14d Sponsors: Sync README with website (ESLint Jenkins)
• 566a947 Sponsors: Sync README with website (ESLint Jenkins)
• 070cbd0 Sponsors: Sync README with website (ESLint Jenkins)

Commits

The new version differs by 53 commits.

• 879c373 6.6.0
• c8ba30a Build: changelog update for 6.6.0
• 39dfe08 Update: false positives in function-call-argument-newline (fixes #12123) (#12280)
• 4d84210 Update: improve report location for no-trailing-spaces (fixes #12315) (#12477)
• c6a7745 Update: no-trailing-spaces false negatives after comments (fixes #12479) (#12480)
• 0bffe95 Fix: no-misleading-character-class crash on invalid regex (fixes #12169) (#12347)
• c6a9a3b Update: Add enforceForIndexOf option to use-isnan (fixes #12207) (#12379)
• 364877b Update: measure plugin loading time and output in debug message (#12395)
• 1744fab Fix: operator-assignment removes and duplicates comments (#12485)
• 52ca11a Fix: operator-assignment invalid autofix with adjacent tokens (#12483)
• 0f6d0dc Fix: CLIEngine#addPlugin reset lastConfigArrays (fixes #12425) (#12468)
• 923a8cb Chore: Fix lint failure in JSDoc comment (#12489)
• aac3be4 Update: Add ignored prop regex no-param-reassign (#11275)
• e5382d6 Chore: Remove unused parameter in dot-location (#12464)
• 49faefb Fix: no-obj-calls false positive (fixes #12437) (#12467)

There are 53 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of hap-nodejs is breaking the build 🚨

The devDependency hap-nodejs was updated from 0.5.0 to 0.5.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

hap-nodejs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 16 commits.

• 94fc227 0.5.1
• 75913a6 Update to protocol version 1.1.0 (#723)
• 82105ae Update Advertiser.ts (#722)
• c047cd2 HomeKit accessory types (#725)
• 972ced4 Fixed: floating point values are now validated correctly again (#729)
• e87f774 Apple TV remote (#708)
• 926862a Fix parameter declaration for init function (#718)
• 6ffef81 Fixed: the session username was treated to uniquely identify an session. Howevery it uniquely identifies every user in a home (#719)
• 1081ab0 Update Core.ts (#710)
• 49e9261 Update README.md (#707)
• b6f842e * Implement /characteristics response according to the spec (#706)
• 2cc06c2 Reimplement /pairings route to match the HAP spec (#702)
• cfbb936 Set default values when creating a CameraRTPStreamManagment service (#705)
• 0eb59c1 Fixed: resource/snapshot requests for bridged cameras now work as intended (#704)
• 6de35b0 Fixed: AccessoryLoader now loads typescript files correctly (#703)

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

How can i arm and disarm ?

Only things this done is temp status for me, how can i arm and disarm ?
Also: Smartcamera was not supported.

Smoke detectors as triggers

Is it possible to make the smoke detectors act as triggers for automation? For the time being I can only use the magnetic door sensors do that. It would be smooth being able to for example have all the lights go to 100% if a smoke detector goes off. Or if you could have a smart plug enabled heating device turned on if the temperature goes below a set value.

Support for motion sensor/camera

I'd like support for the motion sensors (cameras). It's not possible to watch a live feed through the cameras so obviously we can't support the cameras, but could it be possible to support the motion detectors within them?

Has these already been excluded for some technical reasons or are there any possibilities to support them?

TypeError: Cannot read property 'giid' of undefined

Hi,

It seems like the underlaying verisure plugin can't get any installations from the API:

/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:50

giid = typeof installation == 'string' ? installation : installation.giid
                                                                    ^

TypeError: Cannot read property 'giid' of undefined
    at Object.overview (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:50:73)
    at /usr/local/lib/node_modules/homebridge-verisure/index.js:90:16
    at /usr/local/lib/node_modules/homebridge-verisure/index.js:37:7
    at Request._callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:45:7)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-verisure/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)

It's been working great for a day or so, but now homebridge won't start because of this. Could it be that Verisure is throwing us away for some reason?

Farenhight insted of Celsius.

Hi! sins the latest ios update i see the Verisure components as Farenhight insted of Celcius. Login on Verisure and ofc its np there.

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from 22.13.0 to 22.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v22.13.1

22.13.1 (2019-07-22)

Bug Fixes

• valid-describe: ignore describe.each (#337) (ed2a0f6), closes #334

Commits

The new version differs by 23 commits.

• 6cbaa0f chore(prefer-todo): migrate to TS (#335)
• ed2a0f6 fix(valid-describe): ignore describe.each (#337)
• d0a8428 chore(no-test-callback): migrate to TS (#321)
• ccbe766 chore(prefer-strict-equal): migrate to TS (#329)
• ee81058 chore(no-test-prefixes): migrate to TS (#328)
• e938636 chore(consistent-test-it): migrate to TS (#327)
• 26ddedd chore(expect-expect): migrate to TS (#325)
• 4200e76 chore(prefer-spy-on): migrate to TS (#326)
• 3a22ef1 chore(no-if): migrate to TS (#324)
• 4270fca chore(no-export): migrate to TS (#323)
• 12e601a chore(no-hooks): migrate to TS (#322)
• f3c654c chore(no-focused-tests): migrate to TS (#314)
• c455100 chore(prefer-inline-snapshots): migrate to TS (#319)
• 41ed53a chore(no-duplicate-hooks): migrate to TS (#318)
• 384b788 chore(no-test-return-statement): migrate to TS (#320)

There are 23 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Error when initializing unsupported device "HUMIDITY1"

I have a humidity sensor and when I try to start Homebridge I get the following error:

[1/30/2017, 1:18:16 PM] Loaded plugin: homebridge-verisure
[1/30/2017, 1:18:16 PM] Registering platform 'homebridge-verisure.verisure'
[1/30/2017, 1:18:16 PM] ---
[1/30/2017, 1:18:16 PM] Loaded config.json with 0 accessories and 1 platforms.
[1/30/2017, 1:18:16 PM] ---
[1/30/2017, 1:18:16 PM] Loading 1 platforms...
[1/30/2017, 1:18:16 PM] [Verisure] Initializing verisure platform...
Load homebridge-verisure.verisure
[1/30/2017, 1:18:18 PM] [Verisure] Initializing platform accessory 'HUMIDITY1 (Vind)'...
[1/30/2017, 1:18:18 PM] [Verisure] Device HUMIDITY1 is not yet supported
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:128
if (existing.UUID === service.UUID) {
^

TypeError: Cannot read property 'UUID' of null
at Accessory.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:128:34)
at /usr/local/lib/node_modules/homebridge/lib/server.js:418:19
at Array.forEach (native)
at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:402:14)
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:364:32)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
at /usr/local/lib/node_modules/homebridge-verisure/index.js:105:9
at Request._callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:59:7)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/request/request.js:186:22)
at emitTwo (events.js:106:13)

Disable Auto-lock switch with iOS 13 accessory bundling

Hi. Is it possible to remove the auto-lock switch via the config file? After iOS 13 some accessories are bundled together under one tile in HomeKit. The Yale Doorman in Verisure does this it appears. The lock itself and the auto-lock switch bundles together under the lock tile and now shows the state of the auto-lock (on/off and not the lock status (open/locked) on the lock tile. And since the auto-lock is just a power plug switch it is shown as powered on/off.

I would love if there was a way to remove or disable the auto-lock switch from Homekit so only the open/locked state showed on the lock tile.

Thank you for your hard work on this plugin, I really love it and appreciate it :)

Armed / disarmed and door / window status?

Hi,

Do you have plans to include door / window status and alarm status (armed / disarmed)?

  "armState": {
    "statusType": "DISARMED",
    "date": "2017-01-01T00:00:00.000Z",
    "name": "Johnny Walker",
    "changedVia": "TAG"
  },
  
      "doorWindowDevice": [
      {
        "deviceLabel": "HJKL 6789",
        "area": "entrance door",
        "state": "CLOSE",
        "wired": true,
        "testDate": "2017-01-01T00:00:00.000Z"
      }
    ]  

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from 22.9.0 to 22.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v22.10.0

22.10.0 (2019-07-17)

Features

• rules: adds no-if rule (#293) (28bd1dc)

Commits

The new version differs by 7 commits.

• 28bd1dc feat(rules): adds no-if rule (#293)
• 7ebdc0e chore: enforce import destructure order
• 31c7cef chore: convert to import/export (#302)
• 9f858cb chore: delete tests instead of ignoring them with babel
• c595ba0 chore: do not include tests in published tarball
• 4b4eb78 chore: fix lint error in md file
• d3ea720 chore(docs): fix typo (#304)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Block-scoped declarations not yet supported outside strict mode

Hei.

The plugin installs just fine, but I get the following error starting Homebridge:

_====================
ERROR LOADING PLUGIN homebridge-verisure:
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:404:25)
at Object.Module._extensions..js (module.js:432:10)
at Module.load (module.js:356:32)
at Function.Module.load (module.js:311:12)
at Module.require (module.js:366:17)
at require (module.js:385:17)
at Plugin.load (C:\Users*\AppData\Roaming\npm\node_modules\homebridge\lib\plugin.js:65:22)
at Server. (C:\Users*\AppData\Roaming\npm\node_modules\homebridge\lib\server.js:132:14)
at Array.forEach (native)
====================

I run Homebridge on Windows 10, and trying to run Homebridge in strict mode (node --use_strict homebridge does not work either. Is this a Windows related issue you think?

Yale Doorman/Smartlock does not appear in 1.7.0-rc.0

Have a Smartplug and a Smartlock working in 1.6.0.

Only the Smartplug is showing in 1.7.0
-no sign of the Smartlock, and no error in the homebridge log.

Both working when reverting back to 1.6.0 again.

/usr/local/lib/node_modules/homebridge-verisure/index.js:59

Hi from what i seen before someone posted a problem must like this. But it was closed without any explination to if you solved it or what realy happend.

My RP is all updated but has Node-Js 4.8.
Latest Homebridge And i get what you se when trying to run your plugin.
Other then this problem my Enviroment works flawless with Light dims and other things using my telldus.

[7/6/2017, 4:31:02 AM] Loaded plugin: homebridge-telldus
[7/6/2017, 4:31:02 AM] Registering platform 'homebridge-telldus.Telldus'
[7/6/2017, 4:31:02 AM] ---
[7/6/2017, 4:31:03 AM] Loaded plugin: homebridge-verisure
[7/6/2017, 4:31:03 AM] Registering platform 'homebridge-verisure.verisure'
[7/6/2017, 4:31:03 AM] ---
[7/6/2017, 4:31:03 AM] Loaded config.json with 0 accessories and 2 platforms.
[7/6/2017, 4:31:03 AM] ---
[7/6/2017, 4:31:03 AM] Loading 2 platforms...
[7/6/2017, 4:31:03 AM] [Verisure] Initializing verisure platform...
[7/6/2017, 4:31:03 AM] [Telldus Liv!e] Initializing Telldus platform...
[7/6/2017, 4:31:03 AM] [Telldus Liv!e] Loading accessories...
[7/6/2017, 4:31:03 AM] Loading 0 accessories...
Load homebridge-verisure.verisure
[7/6/2017, 4:31:03 AM] [Telldus Liv!e] Logged in with user: [email protected]
[7/6/2017, 4:31:03 AM] [Telldus Liv!e] Found 0 sensors in telldus live.
[7/6/2017, 4:31:03 AM] [Telldus Liv!e] Found 13 devices in telldus live.
/usr/local/lib/node_modules/homebridge-verisure/index.js:59
  if(VERISURE_DEVICE_NAMES.includes(name)) {
                           ^

TypeError: VERISURE_DEVICE_NAMES.includes is not a function
    at getUniqueName (/usr/local/lib/node_modules/homebridge-verisure/index.js:59:28)
    at /usr/local/lib/node_modules/homebridge-verisure/index.js:95:19
    at Array.map (native)
    at /usr/local/lib/node_modules/homebridge-verisure/index.js:92:46
    at /usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:79:7
    at Request._callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:27:17)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/node_modules/request/request.js:188:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/node_modules/request/request.js:1171:10)
    at emitOne (events.js:77:13)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/node_modules/request/request.js:1091:12)
    at IncomingMessage.g (events.js:260:16)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)

Missing support for Verisure Spain (Securitas Direct)

I was wondering if this config could also work for verisure spain (Securitas direct). As the login is a number, and not an email it doesn't work.

If somebody knows a workaround or a solution, it will be really appreciated

An in-range update of eslint-plugin-jest is breaking the build 🚨

Version 21.21.0 of eslint-plugin-jest was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-jest
Current Version	21.20.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes

v21.21.0

21.21.0 (2018-08-11)

Features

• rules: add prefer-strict-equal (#134) (92b1d5c)

Commits

The new version differs by 2 commits.

• e039fed chore: fix lint
• 92b1d5c feat(rules): add prefer-strict-equal (#134)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Username/password does not match any valid login

hi when i configure your module i have this error message :
Error: <response><status><errorGroup>UNAUTHORIZED</errorGroup><errorCode>AUT_00001</errorCode><errorMessage>Username/password does not match any valid login</errorMessage></status></response> at verisure.getToken.then (/usr/local/lib/node_modules/homebridge-verisure/lib/platform.js:81:72) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7)
but my email and password work in myverisure app. For myverisure app i use username and not email for connect. This plugin it's for verisure https://www.verisure.fr/ ? thanks

Startup error

When I try to start homebridge I get this back.

[2017-9-20 21:43:21] Loaded plugin: homebridge-philipshue
[2017-9-20 21:43:21] Registering platform 'homebridge-philipshue.PhilipsHue'
[2017-9-20 21:43:21] ---
[2017-9-20 21:43:21] Loaded plugin: homebridge-verisure
[2017-9-20 21:43:21] Registering platform 'homebridge-verisure.verisure'
[2017-9-20 21:43:21] ---
[2017-9-20 21:43:21] There was a problem reading your config.json file.
[2017-9-20 21:43:21] Please try pasting your config.json file here to validate it: http://jsonlint.com
[2017-9-20 21:43:21]
/usr/local/lib/node_modules/homebridge/lib/server.js:197
throw err;
^

SyntaxError: Unexpected token } in JSON at position 577
at JSON.parse ()
at Server._loadConfig (/usr/local/lib/node_modules/homebridge/lib/server.js:191:19)
at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:52:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:26:16)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)

My config-file:

{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},

"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",


"platforms": [
    {
        "platform" : "PhilipsHue",
        "name" : "Hue",
        "ip_address": "xx",
        "username": "xxxx"
    }
    {
        "platform" : "verisure",
        "name" : "Verisure",
        "email": "[email protected]",
        "password": "xxxxxxx",
        "doorcode": "xxxxxx"
    }
]

}

Without the verisure platform it works perfectly.

Some ideas?

Disable arm/disarm of alarm

I don't know if it's even possible due to limitations in HomeKit, but I'd prefer to arm and disarm the alarm via Verisures solutions only. In other words, I'd like to see the alarm status and create scenarios based on the status, but not be able to change it. Having a device laying around at home, i.e. an iPad, with Siri enabled would create a potential security breach by simply saying "Hey Siri, disarm the alarm".

Maybe the alarm needs to be exposed as a different accessory, or maybe even multiple accessories like a switch which indicates the status and a motion sensor which triggers if someone sets of the alarm.

I'll probably fork the repo and start playing around in order to see what's even possible. But please enlighten me if this is impossible for some reason :)

Setting alarm state to Night crashes Homebridge

I am running Homebridge through HOOBS in a docker container on a Synology.

When using the homebridge-verisure plugin for homebridge, in the iOS Eve app there are four alarm states: Stay, Away, Night and Disarm. If selecting the Night state, homebridge crashes with the following output in the terminal:

[Homebridge] [4/18/2020, 1:00:34 PM] [verisure] info Alarm (ADDRESS): Setting target alarm state to: 2
[Homebridge] [4/18/2020, 1:00:34 PM] Error: Cannot resolve arm state from unknown input: 2
at Alarm.resolveArmState (/hoobs/node_modules/homebridge-verisure/lib/accessories/alarm.js:34:13)
at Alarm.setTargetAlarmState (/hoobs/node_modules/homebridge-verisure/lib/accessories/alarm.js:58:21)
at Characteristic.SecuritySystemTargetState.emit (events.js:311:20)
at Characteristic.SecuritySystemTargetState.Characteristic.setValue (/hoobs/node_modules/hap-nodejs/lib/Characteristic.js:321:10)
at Bridge. (/hoobs/node_modules/hap-nodejs/lib/Accessory.js:882:22)
at Array.forEach ()
at Bridge.Accessory._handleSetCharacteristics (/hoobs/node_modules/hap-nodejs/lib/Accessory.js:822:8)
at HAPServer.emit (events.js:311:20)
at HAPServer._handleCharacteristics (/hoobs/node_modules/hap-nodejs/lib/HAPServer.js:974:10)
at HAPServer. (/hoobs/node_modules/hap-nodejs/lib/HAPServer.js:209:39)
[Homebridge] [4/18/2020, 1:00:34 PM] Got SIGTERM, shutting down Homebridge...

Would it possible to have the Night alarm state actually activating the Stay state so we can avoid this crash if accidentally clicking "Night"?

/Oskar

return Buffer.from(`CPE/${email}:${password}`, 'ascii').toString('base64')

[Verisure] Initializing verisure platform...
/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:15
  return Buffer.from(`CPE/${email}:${password}`, 'ascii').toString('base64')
                ^

TypeError: ascii is not a function
    at Function.from (native)
    at Function.from (native)
    at buildCredientials (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:15:17)
    at Object.module.exports.auth (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:28:35)
    at getVerisureInstallation (/usr/local/lib/node_modules/homebridge-verisure/index.js:30:12)
    at accessories (/usr/local/lib/node_modules/homebridge-verisure/index.js:87:5)
    at Server._loadPlatformAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:351:20)
    at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:295:16)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:77:36)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:134:18)
    at node.js:962:3

Yale door man

Can I use this plugin for Yale doorman with Verisure?

Only expose selected components to HomeKit?

Hi. Is there a way to select which of the Verisure components that gets exposed to HomeKit? I don't want all the temperature components and such because they only update (from Verisures side) every 6 hours.

Thanks for your work on this plugin :)

Alarm changes state by itself

With latest release I'm getting a weird issue. When setting the alarm to night mode, it switches correctly and the Verisure app shows the same thing. 10 seconds later it switches to home mode in the home app and my devices get notifications of the change. When checking the verisure app it still says that it's on night mode correct behavior. Somehow the home app gets confused of the actual state

TypeError: Cannot read property 'UUID' of null

[Verisure] Initializing platform accessory 'undefined (Kitchen)'...
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:128
    if (existing.UUID === service.UUID) {
                                 ^
TypeError: Cannot read property 'UUID' of null

In my overview, "kitchen" is the temperature sensor that's controlled by Verisure.
So what I can gather, the plugin is unable to read the UUID of this component. It fails with this, so I don't know if it can read any of the smart plugs for instance.

An in-range update of eslint-plugin-jest is breaking the build 🚨

The devDependency eslint-plugin-jest was updated from 21.26.2 to 21.27.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v21.27.0

21.27.0 (2018-11-03)

Features

• add prefer-spy-on rule (#191) (ae7aee9), closes #185

Commits

The new version differs by 3 commits.

• ae7aee9 feat: add prefer-spy-on rule (#191)
• 1f658dd chore: mark no-alias-methods as fixable in readme
• db0fdd8 chore: always install the latest version of yarn

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Night control, not supported ?

Hello,
It seems that the Night Control equipment (Homepad1) is not yet supported.
Do you think that you can add it ?
Thanks a lot.
Antoine

Error UUID of null in Accessory.addService

Just testing out the plugin.

It initializes 3 smoke detectors, the main controller, the speaker but then it finds a PIR2:

[4/8/2017, 11:23:57 AM] [Verisure] Device PIR2 is not yet supported
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:128
    if (existing.UUID === service.UUID) {
                                 ^

TypeError: Cannot read property 'UUID' of null
    at Accessory.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:128:34)
    at /usr/local/lib/node_modules/homebridge/lib/server.js:418:19
    at Array.forEach (native)
    at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:402:14)
    at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:364:32)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
    at /usr/local/lib/node_modules/homebridge-verisure/index.js:111:9
    at Request._callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:59:7)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-verisure/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)

This makes homebridge abort startup.

SubZero temperatures

I have the Verisure climate sensor mounted outdoors. It is now winter in Norway and the temperatures are pretty much below zero degrees Celsius all the time. However, the climate sensor reports 0,0° to the home app. My understanding is that this is caused by some minValue set to 0 somewhere, but I have no idea how to fix/edit this. Can something be done to the plugin?

Cannot read propery giid of undefined

Got this error when trying to launch homebridge after installed the plugin and edited the config.json.

[2017-01-30 12:13:17] [Verisure] Initializing verisure platform...
Load homebridge-verisure.verisure
/usr/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:50
    giid = typeof installation == 'string' ? installation : installation.giid
                                                                        ^

TypeError: Cannot read property 'giid' of undefined
    at Object.overview (/usr/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:50:73)
    at /usr/lib/node_modules/homebridge-verisure/index.js:84:16
    at /usr/lib/node_modules/homebridge-verisure/index.js:31:7
    at Request._callback (/usr/lib/node_modules/homebridge-verisure/node_modules/verisure/index.js:45:7)
    at Request.self.callback (/usr/lib/node_modules/homebridge-verisure/node_modules/request/request.js:186:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/usr/lib/node_modules/homebridge-verisure/node_modules/request/request.js:1081:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/homebridge-verisure/node_modules/request/request.js:1001:12)
    at IncomingMessage.g (events.js:291:16)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)

Here is my config.json:

{
  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 51826,
    "pin": "031-45-154"
  },
  "description": "This is an example.",
  "platforms": [
    {
      "platform": "verisure",
      "name": "Verisure",
      "public_key": "XXXXXXXXXXXXXXX",
      "private_key": "XXXXXXXXXXXXXXX",
      "token": "XXXXXXXXXXXXXXX",
      "token_secret": "XXXXXXXXXXXXXXX",
      "email": "XXXXXXXXXXXXXXX",
      "password": "XXXXXXXXXXXXXXX",
      "unknown_accessories": [
        {
          "id": 5338463,
          "model": "test1",
          "manufacturer": "Nexa",
          "name": "test1"
        },
        {
          "id": 8998040,
          "model": "test2",
          "manufacturer": "Oregon",
          "name": "test2"
        }
      ]
    }
  ]
}

Any idea?