tonesto7 / homebridge-smartthings-v2 Goto Github PK

View Code? Open in Web Editor NEW

74.0 74.0 381.0 9.51 MB

SmartThings Homebridge Plugin with is the successor of homebridge-smartthings-tonesto7

JavaScript 77.23% Groovy 22.77%

homebridge-smartthings-v2's Introduction

Hi there 👋

homebridge-smartthings-v2's People

Contributors

Stargazers

Watchers

Forkers

cjschuetze jk3051 nloui jsrichie eduardoribeiro rakeshyoga georgos10 phillipray87 twennywonn rafterk ahzics searchformatt namorp garyjohnson garyjohnsonsmartthings jqnatividad chain000 rgrove loganc58 thilohoppe danybp plinmd morganfreemon jcaramuan thatdonfc rajaram-s s87boyo hognut infinitebulldog adtech99 arcade atownsend vves jimmyla bparnell81 shlomo-rok fibiberlin danielhopkins m1n1kr eric2013264 isejin karpadiem djspammy atoree memodellocos power0877 evaasuka2015 adrixcorp thelost heed822 bromptonista mahmull blue-fire1 parksjm07 charlesgehring mjnhsamsung seonik-j kimyc210 seok5330 truper12 watchwatchmen dt0008 askovi joshuaswarren junhokimm jawgardner farrow32 rookey678 eric-azure mikeb3408 mkhole7 trigger2142 skflrlfdnjs ramset moosequest karlterzaghi qupaking athoscr albaadi bavuchoko leesj87 jonpeng allanbcrawford brown3218 maltcevs justinkelly1 jseunge dmsghks89 acheron1377 mofitn3577 hyeunung heller4chr paddyru jongkwan-lee jtpark77 wkueagle lx3vlll sangjin-moon luiseok noahsevcik

homebridge-smartthings-v2's Issues

TypeError: Cannot read property 'replace' of null

Sentry Issue: HOMEBRIDGE-SMARTTHINGS-12

TypeError: Cannot read property 'replace' of null
  ?, in Array.forEach
...
(3 additional frame(s) were not displayed)

Fridge does not show correct status. (BUG)

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x ] That OAuth is Enabled for the SmartApp under the IDE.
[x ] The SmartApp and Device Handler are using the latest code available.
[x ] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 1
Mobile App Version(Not required): Latest (iOS)
SmartApp Version: (Latest)
Device Handler Version:
Homebridge Version: 0.4.50
NodeJS Version: 12.13.1

Expected Behavior

Tell us what you think should be happening
Homekit should reflect the state of fridge doors and the temperature of both the fridge and the freezer.

Current Behavior

What happens instead of the expected behavior?
Fridge is stuck on open state and temperature is stuck at 0 degrees.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Add fridge according to instructions.

Context

I am not able to check the state of my fridge (in case it is left open) or its temperature.

Please include a copy of any relevant log output to assist in tracking down the bug

No valid versions available for homebridge-smartthings-v2

Great can't wait to try it.
Tried to install it today but I got an error "No valid versions available for homebridge-smartthings-v2"
I'm running a Raspberry pi 3, with HomeBridge in Docker.
unname -a: Linux homebridge 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux

Complete output:
/homebridge # npm i -g homebridge-smartthings-v2
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for homebridge-smartthings-v2

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-03T20_28_43_032Z-debug.log
/homebridge # cat /root/.npm/_logs/2019-12-03T20_26_20_615Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'i',
1 verbose cli '-g',
1 verbose cli 'homebridge-smartthings-v2'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session caaa8e647ac1e228
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 200 https://registry.npmjs.org/homebridge-smartthings-v2 91ms (from cache)
8 silly fetchPackageMetaData error for homebridge-smartthings-v2@latest No valid versions available for homebridge-smartthings-v2
9 timing stage:rollbackFailedOptional Completed in 9ms
10 timing stage:runTopLevelLifecycles Completed in 206ms
11 verbose type tag
12 verbose stack homebridge-smartthings-v2: No valid versions available for homebridge-smartthings-v2
12 verbose stack at pickManifest (/usr/local/lib/node_modules/npm/node_modules/npm-pick-manifest/index.js:39:11)
12 verbose stack at /usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:24:14
12 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
12 verbose stack at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:517:31)
12 verbose stack at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:574:18)
12 verbose stack at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:619:10)
12 verbose stack at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:699:18)
12 verbose stack at _drainQueueStep (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:138:12)
12 verbose stack at _drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:131:9)
12 verbose stack at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:147:5)
12 verbose stack at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
12 verbose stack at processImmediate (internal/timers.js:439:21)
13 verbose cwd /homebridge
14 verbose Linux 4.19.75-v7+
15 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "-g" "homebridge-smartthings-v2"
16 verbose node v12.13.1
17 verbose npm v6.12.1
18 error code ENOVERSIONS
19 error No valid versions available for homebridge-smartthings-v2
20 verbose exit [ 1, true ]

(BUG) Dead Link

The project link in SmartThings Community Installer doesn’t work.

Complete V2 Transition

Opening a placeholder issue to discuss any needed items.

Will this work without a hub?

Will this plugin function without a hub?
I have some robot vacuum cleaners I would like to add, however via Smartthings IDE, I see no option to enter your repo. Is this because I do not have a smartthings hub? (My device are present in the IDE though)

(BUG)

Verify the following before opening an trouble issue

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 2
Mobile App Version(Not required):
SmartApp Version: v2.1.0
Device Handler Version: v2.1.7
Homebridge Version: 0.4.50
NodeJS Version: v10.15.2

Expected Behavior

The logaudit.json file should be opened or explain why not.

Current Behavior

Homebridge cannot open the logaudit.json file. See log below.

Steps to Reproduce (for bugs)

sudo systemctl start homebridge
tail -f daemon.log

Context

Simply starting Homebridge and cleaning up any errors.

This error consistently shows in the daemon.log:

Jan  9 11:37:42 raspberrypi homebridge[2299]: [1/9/2020, 11:37:42 AM][SmartThings-v2]INFO: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded!
Jan  9 11:37:42 raspberrypi homebridge[2299]: 2020-01-09T17:37:42.630Z '[FileStreamRotator] Failed to store log audit at:' 'logaudit.json' 'Error:' { Error: EACCES: **permission denied, open 'logaudit.json'**
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at Object.openSync (fs.js:439:3)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at Object.writeFileSync (fs.js:1190:35)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at Object.FileStreamRotator.writeAuditLog (/usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:246:12)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at Object.FileStreamRotator.addLogToAudit (/usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:320:27)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:437:36)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at EventEmitter.emit (events.js:194:15)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at /usr/local/lib/node_modules/homebridge-smartthings-v2/node_modules/file-stream-rotator/FileStreamRotator.js:483:20
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at process._tickCallback (internal/process/next_tick.js:61:11)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
Jan  9 11:37:42 raspberrypi homebridge[2299]:     at startup (internal/bootstrap/node.js:283:19)
Jan  9 11:37:42 raspberrypi homebridge[2299]:   errno: -13,
Jan  9 11:37:42 raspberrypi homebridge[2299]:   syscall: 'open',
Jan  9 11:37:42 raspberrypi homebridge[2299]:   code: 'EACCES',
Jan  9 11:37:42 raspberrypi homebridge[2299]:   path: 'logaudit.json' }
Jan  9 11:37:42 raspberrypi homebridge[2299]: [1/9/2020, 11:37:42 AM] Homebridge is running on port 51826.

[ISSUE] Thermostat `this.platform.getTempUnit()` Error

First,
I would like to thank you for your project and for being active there. I even took the time to give you a donation even if I am not rich.

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x ] That OAuth is Enabled for the SmartApp under the IDE.
[x ] The SmartApp and Device Handler are using the latest code available.
[x ] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 1 device thermostat not working
Mobile App Version(Not required):
SmartApp Version: homebrige V 2.0.2
Device Handler Version:
Homebridge Version: hub V2
NodeJS Version: V13.3.0

Expected Behavior and ## Current Behavior

Tell us what you think should be happening
-When i start in terminal hombridge i have red error " This.platform.getTempUnit is not a fonction"

-In Homekit first, i don't see the anbiant temperature of the room. but the real problem is, when i put thermostat Temperature in 25 because is winter. He doesn't start to heat. In the log on my Raspberry PI 4 when Hombridge is running no activity on real time log.

When change temperature on my SmartThings (classic) on the same thermostat, is heating and i see activity on raspberry PI 4 real time log. image 3
I forget something, i try procedur when is lock and unlock the heating not working the Lock i working when i dont wanna child change temperature on direct thermostat and is working.

I have the impression that the Homekit doesn't speak to the homebridge of the raspberry Pi

Current Behavior

What happens instead of the expected behavior?

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

(BUG) Samsung Smartthings Motion Sensor and Multipurpose Sensor - no status update

Check the following before opening the problem

** Go through all the points below and put "x" in all the appropriate fields.
If you're unsure about any of them, don't hesitate to ask. We are here to help! **

That OAuth is enabled for SmartApp in the IDE.
SmartApp and Device Handler use the latest available code.
That both SmartApps and device support modules have been published for you in the IDE.

Configuration information

How many devices are detected?: All (14)
Mobile application version (not required):
SmartApp version: 2.0.4
Device support module version:
Homebridge version: QNAP Homebridge - homebridge-config-ui-x v4.6.7 - node.js v12.14.0 - © 2019 oznu
NodeJS version:

Expected behavior

Hombridge does not refresh the status of motion sensor devices and Multipurpose Sensor data is downloaded only once when you reset your homebridge. No update of the motion detection status. no update of door opening or closing, no temperature update from the device

Current behavior

The SmartThings application receives data correctly, but you cannot see it in the homebridge.

Steps to Reproduce (in case of errors)

** Provide a link to a live example or unique set of steps to reproduce this error. If necessary, attach a code to play **

Context

** How did this problem affect you? What are you trying to achieve
The ability to automate from Apple Home
** Providing context helps us find the solution that is most useful in the real world **

Include a copy of the appropriate log output to help track the error

(BUG) Plug In Sends Events Locally Even When Switched Off

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 3
Mobile App Version(Not required):
SmartApp Version: 2.0.4
Device Handler Version: ?
Homebridge Version: HOOBS 3.1.15
NodeJS Version: v12.13.1

Expected Behavior

The smart app does not seem to retain settings. When I go through and add a device, it is added to homebridge, but if I come back to the SmartApp in SmartThings (Classic), the SmartApp interface appears like new. This is causing the "Send Local Commands" toggle switch to persist to the on state, and the plug in is sending local commands to the hub: "| SendToLocalHub: (true)", even though the JSON config has both "local_commands": false & "direct": false.

This is causing switches to hang in the Home app after one activation, and seemingly shutting things down on the homebridge side:

From the terminal output, even when set for local_commands false
"[Homebridge] [1/1/2020, 23:26:43][SmartThings-v2]NOTICE: Updating Global Values | HubIP: 192.168.1.133 | UseLocal: true"

Eventually I get this:
[Homebridge] [1/2/2020, 08:30:35] Unhandled Rejection "RequestError: Error: connect ETIMEDOUT 192.168.1.133:39500".
[Homebridge] [1/2/2020, 08:30:35] Unhandled Rejection "TypeError: callback is not a function".
[Homebridge] [1/2/2020, 08:30:35] RequestError: Error: connect ETIMEDOUT 192.168.1.133:39500
[Homebridge] at new RequestError (/home/hoobs/.hoobs/node_modules/request-promise-core/lib/errors.js:14:15)
[Homebridge] at Request.plumbing.callback (/home/hoobs/.hoobs/node_modules/request-promise-core/lib/plumbing.js:87:29)
[Homebridge] at Request.RP$callback [as _callback] (/home/hoobs/.hoobs/node_modules/request-promise-core/lib/plumbing.js:46:31)
[Homebridge] at self.callback (/home/hoobs/.hoobs/node_modules/request/request.js:185:22)
[Homebridge] at Request.emit (events.js:210:5)
[Homebridge] at Request.onRequestError (/home/hoobs/.hoobs/node_modules/request/request.js:881:8)
[Homebridge] at ClientRequest.emit (events.js:210:5)
[Homebridge] at Socket.socketErrorListener (_http_client.js:406:9)
[Homebridge] at Socket.emit (events.js:210:5)
[Homebridge] at emitErrorNT (internal/streams/destroy.js:92:8)
[Homebridge] at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
[Homebridge] at processTicksAndRejections (internal/process/task_queues.js:80:21)
[Homebridge] [1/2/2020, 08:30:35] TypeError: callback is not a function
[Homebridge] at /home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/src/ST_Client.js:112:21
[Homebridge] at processTicksAndRejections (internal/process/task_queues.js:93:5)
[Homebridge] (node:7884) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
[Homebridge] (node:7884) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2)

Current Behavior

What happens instead of the expected behavior?

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

[ISSUE] HOOBS Plugin Configuration Page Blank

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ X] That OAuth is Enabled for the SmartApp under the IDE.
[ X] The SmartApp and Device Handler are using the latest code available.
[ X] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 0
Mobile App Version(Not required):
SmartApp Version: v1.6.1
Device Handler Version:
Homebridge Version: Hoobs 3.0
NodeJS Version: v12.13.1

Expected Behavior

Tell us what you think should be happening
I should be able to see my devices I linked to the plugin in my home kit.

Current Behavior

What happens instead of the expected behavior?
When plug in is added into Hoobs you no longer get the quick edit config like you did on the previous version of tonesto7 smarthings plug in and No devices are displayed.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug
Unable to determine plugin type for "homebridge-smartthings-v2"
Unable to determine plugin type for "homebridge-smartthings-v2"

(BUG) Duplicate SmartApps in iOS app

Somehow I've ended up with duplicates of the SmartApp on my iPhone. I can't open any of them, and therefore can't remove them. I also can't remove the SmartApp via the IDE because it says the SmartApp is in use. I've contacted SmartThings support and they're working on it. Any ideas on how to fix this while I wait?

Thanks,

Patrick

How do you update the SmartApp?

How do you update the SmartApp from one version to another without just removing it first?

(BUG) Issue after 2.1.0 update

[Homebridge] [1/7/2020, 5:16:42 PM] TypeError: transport is not a constructor
at exports.Logger.Logger.add (/home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/node_modules/winston/lib/winston/logger.js:481:41)
at Logging.getLogger (/home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/src/libs/Logger.js:58:20)
at new ST_Platform (/home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:32:33)
at Server._loadPlatforms (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:293:34)
at Server.run (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:74:14)
at module.exports (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/cli.js:90:12)
at Object. (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/bin/homebridge:10:63)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
[Homebridge] [1/7/2020, 5:16:42 PM][SmartThings-v2]ERROR: uncaughtException: transport is not a constructor
[Homebridge] [1/7/2020, 5:16:42 PM] Got SIGTERM, shutting down service...

[ISSUE] We received a request from a client that didn't provide a valid access_token and app_id Error

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ X] That OAuth is Enabled for the SmartApp under the IDE.
[X ] The SmartApp and Device Handler are using the latest code available.
[X ] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: NONE
Mobile App Version(Not required):
SmartApp Version: 2.02
Device Handler Version:
Homebridge Version: 3.1.1
NodeJS Version:

Expected Behavior

AFTER CONFIG ADDED FROM THE COPIED CODE IN SMARTAPP, HOMEBRIDGE WOULD START AT LEAST AFTER RESTART.

Current Behavior

What happens instead of the expected behavior? HOMEKIT DOESN'T GET NEW DEVICES. HOMEBRIDGE SHOWS THE NEW DEVICES BUT ERRORS IN LOG.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

GETHUB INTEGRATION INSTALL PER INSTRUCTIONS
SMARTAPP INSTALL. SELECTED 9 SWITCHES, SHM MODES
INSTALL PLUGIN VIA HOOBS 3.1.1
COPY TEXT FROM APP AND PAST OVER THE EXISTING CONFIG ADDED ALREADY BY INSTALL.

Context

**How has this issue affected you? What are you trying to accomplish? WANT SMARTTHINGS HOMEBRIDGE INTEGRATION
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug
Unable to determine plugin type for "homebridge-smartthings-v2"
[Homebridge] [12/14/2019, 22:12:21][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:21][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:21][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:22][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:22][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:22][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:22][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:22][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:23][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:24][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id
[Homebridge] [12/14/2019, 22:12:24][SmartThings-v2]ERROR: (update) | We received a request from a client that didn't provide a valid access_token and app_id

(BUG) temperature readings incorrect for sensors

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x ] That OAuth is Enabled for the SmartApp under the IDE.
[ x] The SmartApp and Device Handler are using the latest code available.
[ x] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 64
Mobile App Version(Not required):
SmartApp Version:2.0.1
Device Handler Version:
Homebridge Version:0.4.50
NodeJS Version:10.9.0

Expected Behavior

Tell us what you think should be happening
Contact and motion sensors in Home app should have the same temp as what is listed in smartthings

Current Behavior

What happens instead of the expected behavior?
Temperature settings are showing in home app as much lower than smartthings. Ie the actual reading is 22 degrees Celsius but in home app it’s showing as -5.5 degrees

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Open any sensors
Observe the listed temperature.

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

I use temperature readings in conjunction with automations of some HomeKit only devices such as iHome outdoor plug to operate space heaters in case my furnace stops working when I’m away.

Please include a copy of any relevant log output to assist in tracking down the bug

Unable to add repo

Tried the community installed and it is not installing.
Filed back to the manual and am getting
You don't have access to tonesto7/homebridge-smartthings-v2

Any Ideas?

##** Verify the following before opening a trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?:
Mobile App Version(Not required):
SmartApp Version:
Device Handler Version:
Homebridge Version:
NodeJS Version:

Expected Behavior

Tell us what you think should be happening

Current Behavior

What happens instead of the expected behavior?

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

(BUG) Turning Thermostat to Heat Defaults to 100 Degrees

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?:
Mobile App Version(Not required):
SmartApp Version:
Device Handler Version:
Homebridge Version:
NodeJS Version:

Expected Behavior

Tell us what you think should be happening

Current Behavior

What happens instead of the expected behavior?

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

(BUG) V2.1.12 Thermostats don't refresh in Homekit

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?:
Mobile App Version(Not required):
Smarthin App Version: 2.1.1
Device Handler Version:
Homebridge Version: Hub V2
Homebridge plugin: v2.1.1 - v2.1.12
NodeJS Version: V13.3.0

Expected Behavior

Tell us what you think should be happening

Current Behavior

What happens instead of the expected behavior?

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

hi tonesto7
there is big news... almost works. the problem is when i Heating set point to 22 celsius exemple. The thermostat start to heat, but when i exit homekit and i re-open homekit on my iphone. Is stay to 20 celsius but the heating set point is 22.

When i re-open Homekit there is the information

the information was not saved in the log.

Is it possible to interrogate the heating set point thermostat and push the information in the home kit? i don't know if is possible...

(BUG) ST devices with placeholder type will break Homebridge connectivity

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 1
Mobile App Version(Not required):
SmartApp Version: 2.0.1
Device Handler Version: N/A
Homebridge Version: 2.0.1
NodeJS Version: 10.17.0

Expected Behavior

Tell us what you think should be happening
When adding a device under the Light category, it should add to Homebridge/Home iOS app

Current Behavior

What happens instead of the expected behavior?
When a device is added that has a type of placeholder (I have Kasa/TP-Link and Meross devices added to ST which default to this), Homebridge will no longer update the Home app and all devices will eventually become unresponsive until that placeholder device is removed.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Add a device via the Homebridge v2 SmartApp with a type of placeholder (shows in IDE type column)
Restart Homebridge
View Home iOS app and the device will not show up
If you try to remove Home from iOS app and re-add accessory, it will be unable to connect to Homebridge.

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world
I have several WiFi devices added to ST that I'd like to control with Homebridge and they aren't added. I can work around this by editing the device type in the IDE to something else like Light Capability.

Please include a copy of any relevant log output to assist in tracking down the bug
There are no visible errors when this occurs, even with debug mode enabled.

(BUG) Devices being added twice?

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 2
Mobile App Version(Not required):
SmartApp Version: 2.0.1
Device Handler Version:
Homebridge Version: Homebridge v2.4 / HOOBS v3.1.1
NodeJS Version:

Expected Behavior

Tell us what you think should be happening
Select one device as sensor and other, add one device to homebridge

Current Behavior

What happens instead of the expected behavior?
Plugin tries to create two devices for the same device.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Install the plugin through HOOBS interface
Install the smart app in ST Classic and select one device as sensor and the same device as other
Check logs, see that two devices are being added

Context

How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world
I am trying to migrate from v1 to v2 of the homebridge-smartthings plugin.
I deleted the v1 plugin form homebridge and from the ST Classic app. I installed the new smart app per the instructions.
I installed the plugin through the HOOBS plugin GUI. I placed the config code in the config.json file as instructed.
When run, the plugin attempts to create two devices for the same device and I receive an error.
I have tried to narrow this down to one specific issue but I am having a hard time. I was expecting v2 to work as v1 did, where I could add the same device to many device types and it would not produce duplicates. Maybe this is not the case?

Please include a copy of any relevant log output to assist in tracking down the bug

[Homebridge] [12/11/2019, 11:15:43 AM] Loaded config.json with 2 accessories and 4 platforms.
[Homebridge] [12/11/2019, 11:15:45 AM] Loaded plugin: homebridge-smartthings-v2
[Homebridge] [12/11/2019, 11:15:45 AM] Registering platform 'homebridge-smartthings-v2.SmartThings-v2'
[Homebridge] [12/11/2019, 11:15:45 AM] ---
[Homebridge] [12/11/2019, 11:15:46 AM] [SmartThings-v2] Initializing SmartThings-v2 platform...
[Homebridge] [12/11/2019, 11:15:46 AM][SmartThings-v2]INFO: Homebridge Version: 2.4
[Homebridge] [12/11/2019, 11:15:46 AM][SmartThings-v2]INFO: SmartThings-v2 Plugin Version: 2.0.1
[Homebridge] [12/11/2019, 11:15:46 AM][SmartThings-v2]INFO: Checking Package Version for Updates...
[Homebridge] [12/11/2019, 11:15:47 AM][SmartThings-v2]INFO: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded!
[Homebridge] [12/11/2019, 11:15:47 AM][SmartThings-v2]DEBUG: Refreshing All Device Data
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]WARN: Devices to Remove: (0)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]INFO: Devices to Update: (0)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]GOOD: Devices to Create: (2)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG: Initializing New Device (Front Door Lock | ***)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG: Removing capability: None from Device: Front Door Lock
[Homebridge] HAP Warning: Characteristic 0000001A-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000045-0000-1000-8000-0026BB765291. Adding anyway.
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG:
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG: Setting device data from existing data
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]NOTICE: [CHARACTERISTIC (BatteryLevel) CHANGE] battery (Front Door Lock) | LastUpdate: (Wed Dec 11 2019 11:15:48 GMT-0800 (Pacific Standard Time)) | NewValue: (100) | OldValue: (0)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]INFO: Added Device: (Front Door Lock | ***)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG: Initializing New Device (Front Door Lock | ***)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG: Removing capability: None from Device: Front Door Lock
[Homebridge] HAP Warning: Characteristic 0000001A-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000045-0000-1000-8000-0026BB765291. Adding anyway.
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG:
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]DEBUG: Setting device data from existing data
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]NOTICE: [CHARACTERISTIC (BatteryLevel) CHANGE] battery (Front Door Lock) | LastUpdate: (Wed Dec 11 2019 11:15:48 GMT-0800 (Pacific Standard Time)) | NewValue: (100) | OldValue: (0)
[Homebridge] [12/11/2019, 11:15:48 AM] Unhandled Rejection "Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: devUUID".
[Homebridge] [12/11/2019, 11:15:48 AM] Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: devUUID
[Homebridge] at Bridge.Accessory.addBridgedAccessory (/home/hoobs/.hoobs/node_modules/@hoobs/hap/lib/Accessory.js:268:13)
[Homebridge] at Bridge.Accessory.addBridgedAccessories (/home/hoobs/.hoobs/node_modules/@hoobs/hap/lib/Accessory.js:299:10)
[Homebridge] at Server._handleRegisterPlatformAccessories (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:503:18)
[Homebridge] at Server.<anonymous> (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:33:14)
[Homebridge] at API.emit (events.js:198:13)
[Homebridge] at API.registerPlatformAccessories (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/api.js:154:10)
[Homebridge] at ST_Platform.addDevice (/home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:182:25)
[Homebridge] at toCreate.forEach.device (/home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:147:61)
[Homebridge] at Array.forEach (<anonymous>)
[Homebridge] at client.getDevices.catch.then.resp (/home/hoobs/.hoobs/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:147:38)
[Homebridge] at process._tickCallback (internal/process/next_tick.js:68:7)
[Homebridge] (node:2643) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
[Homebridge] [12/11/2019, 11:15:48 AM][SmartThings-v2]INFO: INFO: Your plugin version is up-to-date
[Homebridge] [12/11/2019, 11:15:49 AM][SmartThings-v2]DEBUG: sendUpdateStatus Resp:

Homebridge plugin delays receiving/processing some events from SmartThings

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ x] That OAuth is Enabled for the SmartApp under the IDE.
[ x] The SmartApp and Device Handler are using the latest code available.
[ x] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 43
Mobile App Version(Not required):
SmartApp Version: 2.0.4
Device Handler Version:
Homebridge Version: 0.4.50, Homebridge plugin version: 2.0.10
NodeJS Version:10.15.2

Expected Behavior

Tell us what you think should be happening
Events (sensor state, lock/unlock, etc.) should propagate from SmartThings to Homebridge nearly instantaneously.

Current Behavior

What happens instead of the expected behavior?
Some events propagate right away, others experience a 8-30 second delay.
ps. This issue did not exist with the homebridge-smartthings v1 smartapp & plugins.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Configure multiple sensors. at least one contact sensor and a motion sensor.
Trigger the sensor(s)
Notice that HomeKit alerts / state updates for the contact sensor are delayed.

TBH, unsure if others are experiencing this issue, but I can easily reproduce it.

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Homekit alerts are delayed, as are automations in Homekit that rely on these events. This also degrades the UX b/c actions (like locking a door) take longer to reflect on the Home app UI (which, for instance, gets stuck on "Locking..." for that time).

Please include a copy of any relevant log output to assist in tracking down the bug

Motion events propagating instantaneously

SmartThings log:
xxxxxxxxx-333f-4112-9303-3d9001a1718c 2:26:05 PM: debug Sending DEVICE Event (Office | MOTION: active) to Homebridge at (10.0.1.x:8000)

Homebridge log:
[12/28/2019, 2:26:05 PM] [INFO]: [Device Change Event]: (Office) [MOTION] is active

Door lock / unlock event takes 10+ seconds to propagate. Have also seen this delay with contact sensors.

SmartThings log:
xxxxxxxxx-333f-4112-9303-3d9001a1718c 2:36:13 PM: debug Sending DEVICE Event (Garage door lock | LOCK: locked) to Homebridge at (10.0.1.x:8000)

Homebridge log (notice the 16 second delay):
[12/28/2019, 2:36:29 PM] [INFO]: [Device Change Event]: (Garage door lock) [LOCK] is locked

(BUG) app_id and access_token changes every time I open the SmartThings Classic app

I have been struggling to update from the old homebridge plugin to v2 and experience two issues:

Whenever I open and make changes to any setting in the SmartThings Classic for the homebridge v-2 smart app, the app_id and access_token changes. I assume this should not be the case, as I would have to update the config file in homebridge every time this happens?
No matter which ST devices I select to show up in homebridge, when I save they are removed

Any advice on what I am doing wrong?

RequestError: Error: connect ETIMEDOUT 10.0.0.5:39500

Sentry Issue: HOMEBRIDGE-SMARTTHINGS-2T

Error: connect ETIMEDOUT 10.0.0.5:39500
  File "net.js", line 1136, in TCPConnectWrap.afterConnect [as oncomplete]

RequestError: Error: connect ETIMEDOUT 10.0.0.5:39500
  File "C:\Users\asantilli\Documents\GitHub\homebridge-smartthings-v2\node_modules\request-promise-core\lib\errors.js", line 14, in new RequestError
    Error.captureStackTrace(this);
  File "C:\Users\asantilli\Documents\GitHub\homebridge-smartthings-v2\node_modules\request-promise-core\lib\plumbing.js", line 87, in Request.plumbing.callback
    self._rp_reject(new errors.RequestError(err, self._rp_options, response));
  File "C:\Users\asantilli\Documents\GitHub\homebridge-smartthings-v2\node_modules\request-promise-core\lib\plumbing.js", line 46, in Request.RP$callback [as _callback]
    plumbing.callback.call(self, err, response, body);
  File "C:\Users\asantilli\Documents\GitHub\homebridge-smartthings-v2\node_modules\request\request.js", line 185, in self.callback
    self._callback.apply(self, arguments)
  File "C:\Users\asantilli\Documents\GitHub\homebridge-smartthings-v2\node_modules\request\request.js", line 881, in Request.onRequestError
    self.emit('error', error)
...
(5 additional frame(s) were not displayed)

(BUG) Device responds then becomes unresponsive

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x ] That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 38
Mobile App Version(Not required): Latest
SmartApp Version: 2.0.1 Latest
Device Handler Version: n/a
Homebridge Version: 0.4.5
NodeJS Version: 13.3

Expected Behavior

Device should not become unresponsive in HomeKit after action.

Current Behavior

Devices respond to initial command, then become unresponsive, “No Response” in HomeKit. They recover a few minutes later, then will respond to a single command, and become unresponsive again. Oddly this only seems to effect Z-Wave devices (Jasco Z-wave Plus dimmers and switches), though I have only tested with a few Zigbee bulbs (my only controllable Zigbee devices).

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Send device command
Send subsequent command
Device becomes unresponsive

Please include a copy of any relevant log output to assist in tracking down the bug

Logged debug to file. Let me know if I should send or paste.

(BUG) v2.1.12 - Does not change the status of devices

Check the following before opening the problem

** Go through all the points below and put "x" in all the appropriate fields.
If you're unsure about any of them, don't hesitate to ask. We are here to help! **

That OAuth is enabled for SmartApp in the IDE.
SmartApp and Device Handler use the latest available code.
That both SmartApps and device support modules have been published for you in the IDE.

Configuration information

How many devices were detected?: 15
Mobile application version (not required):
SmartApp version: 2.1
Device support module version:
Homebridge version: 0.4.50 QNAP
NodeJS version: node.js v12.14.0

Expected behavior

Clicking on the HomeKit application does not change the device status, e.g. turning off / on the light bulb does not respond

Current behavior

NOTICE: Sending Device Command: off | Value: Nothing | DeviceID: (36cc0510-296a-40b9-a987-f562f2268a21) | SendToLocalHub: (true)
NOTICE: Sending Device Command: off | Value: Nothing | DeviceID: (6abe97b3-afd1-4eed-839b-d272966de146) | SendToLocalHub: (true)
NOTICE: Sending Device Command: off | Value: Nothing | DeviceID: (32abb0f0-9266-4dcc-9525-d11d02357dd4) | SendToLocalHub: (true)
NOTICE: Sending Device Command: off | Value: Nothing | DeviceID: (848beed5-3b5d-4a77-9845-71402ad71d6c) | SendToLocalHub: (true)
DEBUG: sendDeviceCommand Resp: undefined
DEBUG: sendDeviceCommand Resp: undefined
DEBUG: sendDeviceCommand Resp: undefined
DEBUG: sendDeviceCommand Resp: undefined

Steps to Reproduce (in case of errors)

** Provide a link to a live example or unique set of steps to reproduce this error. If necessary, attach a code to play **

Context

** How did this problem affect you? What are you trying to achieve
** Providing context helps us find the solution that is most useful in the real world **

Include a copy of the appropriate log output to help track the error

(BUG) Nexia Thermostat Missing from SmartApp

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 16
Mobile App Version(Not required):
SmartApp Version: 2.1.1
Device Handler: Version 2.1.12
Homebridge Version: 0.4.50
NodeJS Version: 12.14.0

Expected Behavior

I should be able to see Nexia devices in the smartapp when configuring devices, since they are linked in smartthings

Current Behavior

Nexia devices are missing in every category in the smartapp and so cannot be enabled in homekit

Steps to Reproduce (for bugs)

Smartthings App: Add -> New Device -> Nexia -> Thermostat
Link Nexia Account
See the Nexia Thermostat enabled in Smartthings App
Goto Homebridge v2 smartapp
The Nexia thermostat is not a visible device

Context

I want to be able to enable my Nexia Thermostat in Homekit

Please include a copy of any relevant log output to assist in tracking down the bug

Filtering out Button capability from a device does not remove the extra button from Home app

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 4
Mobile App Version(Not required):
SmartApp Version: 2.0.3
Device Handler Version: 2.0.10
Homebridge Version: 0.4.50
NodeJS Version: 8.11.1

Expected Behavior

After removing Button capability from a device, the button is should disappear from Home app.

Current Behavior

After removing Button capability from a device, the button is still showing up in Home app.

Steps to Reproduce (for bugs)

Add a device with both Switch and Button capabilities to SmartThings
In the smart app, add the device to HomeKit as Switch (without removing the Button capability)
Once Home app shows a switch and a button for the device, go back to smart app and remove the Switch capability

Context

My GE/Jasco in-wall switch has both Switch and Button capabilities thanks to the DH of "nuttytree : GE/Jasco Z-Wave Plus Dimmer Switch" so I can configure double press behavior. However both v1 and v2 of the plugin renders the switch only as Button in HomeKit, even though I define the type as Switch or Light in the smart app. The solution is to remove the Button capability with the filtering. While doing this after the device already shows up as both Button and Switch, I discovered this issue. I am able to workaround it by unchecking the device as Switch then adding it back.

Please include a copy of any relevant log output to assist in tracking down the bug

Question: Does this allow anything supported by the SmartThings hub to be seen on HomeKit

This is probably a really dumb question but I notice the list of devices that the SmartThings hub connects to is long. Does this allow any device supported by SmartThings hub to also be supported in HomeKit via this Homebridge plugin?

(BUG) v2 doesn't present devices and disables native HomeKit devices.

use## Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[X ] That OAuth is Enabled for the SmartApp under the IDE.
[ X] The SmartApp and Device Handler are using the latest code available.
[ X] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 54
Mobile App Version(Not required): Classic
SmartApp Version: Latest
Device Handler Version: Latest
Homebridge Version: Latest
NodeJS Version: Latest

Expected Behavior

Tell us what you think should be happening
Devices should appear in HomeKit and all existing devices should continue to work.

Current Behavior

What happens instead of the expected behavior?
When using the v2 code, my SmartThings devices don't appear in HomeKit, and, more strangely, everything else in HomeKit (natives devices like ecobee) stop working. When I go back to the deprecated homebridge-smartthings-tonesto7 everything works great. I've tried this both on raspberry pi I built from scratch as well as HOOBS.

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Build HomeBridge RPi from scratch, install v2 plug-in.

Context

**How has this issue affected you? What are you trying to accomplish?

I'm trying to move up to the latest SmartThings homebridge plugin.

Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

Unable to add Homebridge to HomeKit after installing/configuring the smartthings plugin

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 1 light switch
Mobile App Version(Not required):
SmartApp Version: 2.0.1
Device Handler Version:
Homebridge Version: 0.4.50
NodeJS Version: 12.14.0

Expected Behavior

Tell us what you think should be happening
I have a switch, that's added to the SmartThings App. The switch is a Meross switch, from the Meross app (not sure if that would have anything to do with this). Once I add the SmartThings plugin to Homebridge, I would think the devices should then appear in HomeKit.

Current Behavior

What happens instead of the expected behavior?
Once I add the SmartThings plugin to Homebridge, all of my devices using HomeBridge (just a Nest Thermostat for now) shows "No Response." In Homebridge, the light switch shows up in the Accessories tab. I'm also unable to add Homebridge as a bridge to HomeKit if I have the SmartThings plugin installed/configured. Once I remove the smartthings plugin and remove it from the config file, the Nest device shows responsive again.

In Homebridge, the Services shows as running and the console is listening.

Steps to Reproduce (for bugs)

The steps is really just installed the smartthings v2 plugin and configuring it.

Context

**How has this issue affected you? What are you trying to accomplish?
I'm not sure if I'm doing something wrong, or missing a step. Hope this is the correct place to post this. Thanks.

Please include a copy of any relevant log output to assist in tracking down the bug

Smartthings device command not recognized in HB [question]

Hello,

Recently updated to V2 of the ST homebridge via the community installer and updated the JSON to reflect the new plugin. Home app recognizes all my devices in my smartthings app but when trying to send a signal to turn on/off lights, it just hangs. Looking at log files, it seems that there is no "value" to the signal from ST to HB. Can someone point me to the right direction of how to fix it?

When changing to not send send as local commands, the command works, but it takes a very noticeable delay before the command goes through which at that point, is quick to close the home app and open ST app to turn on/off lights

Image of issue log with local commands on: https://imgur.com/a/mZFSCdY

(BUG) August Smart Lock Pro doesn't lock or unlock

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ X] That OAuth is Enabled for the SmartApp under the IDE.
[X ] The SmartApp and Device Handler are using the latest code available.
[X ] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 5
Mobile App Version(Not required):
SmartApp Version: 2.1.1
Device Handler Version: NA
Homebridge Version: 0.4.50
NodeJS Version: 10.12.0

Expected Behavior

Tell us what you think should be happening
Upon sending a homebridge lock or unlock command the device should lock or unlock.

Current Behavior

What happens instead of the expected behavior?
The command never reaches the device

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Added device as "Other" or as "Switch"
Both devices are detected and show up in Homekit with no issue
Command sent to unlock produce the following event:
NOTICE: Sending Device Command: unlock | Value: Nothing | DeviceID: (d200b920-ec6f-4e0d-b166-c66e5d2fd8b5) | SendToLocalHub: (true)
NOTICE: Sending Device Command: lock | Value: Nothing | DeviceID: (d200b920-ec6f-4e0d-b166-c66e5d2fd8b5) | SendToLocalHub: (true)
If Device is unlocked manually the Homekit seems to see it as unlocked but cant do anything to lock it.

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up twith a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

#####Device Added as "Other" in Smart App Debug Log of HB
DEBUG: Initializing New Device (August Smart Lock Pro | d200b920-ec6f-4e0d-b166-c66e5d2fd8b5)
DEBUG: August Smart Lock Pro ' | ' 'lock'
GOOD: [CHARACTERISTIC (function() {
Characteristic.call(this, 'Lock Current State', '0000001D-0000-1000-8000-0026BB765291');
this.setProps({
format: Characteristic.Formats.UINT8,
maxValue: 3,
minValue: 0,
validValues: [0,1,2,3],
perms: [Characteristic.Perms.READ, Characteristic.Perms.NOTIFY]
});
this.value = this.getDefaultValue();
}) GET] lock (August Smart Lock Pro) | LastUpdate: (Sat Jan 11 2020 18:49:14 GMT+0000 (Coordinated Universal Time)) | Value: (1)
GOOD: [CHARACTERISTIC (function() {
Characteristic.call(this, 'Lock Target State', '0000001E-0000-1000-8000-0026BB765291');
this.setProps({
format: Characteristic.Formats.UINT8,
maxValue: 1,
minValue: 0,
validValues: [0,1],
perms: [Characteristic.Perms.READ, Characteristic.Perms.WRITE, Characteristic.Perms.NOTIFY]
});
this.value = this.getDefaultValue();
}) GET] lock (August Smart Lock Pro) | LastUpdate: (Sat Jan 11 2020 18:49:14 GMT+0000 (Coordinated Universal Time)) | Value: (1)
GOOD: [CHARACTERISTIC (function() {
Characteristic.call(this, 'Lock Target State', '0000001E-0000-1000-8000-0026BB765291');
this.setProps({
format: Characteristic.Formats.UINT8,
maxValue: 1,
minValue: 0,
validValues: [0,1],
perms: [Characteristic.Perms.READ, Characteristic.Perms.WRITE, Characteristic.Perms.NOTIFY]
});
this.value = this.getDefaultValue();
}) GET] lock (August Smart Lock Pro) | LastUpdate: (Sat Jan 11 2020 18:49:14 GMT+0000 (Coordinated Universal Time)) | Value: (1)
DEBUG: August Smart Lock Pro ' | ' 'battery'
GOOD: [CHARACTERISTIC (function() {
Characteristic.call(this, 'Battery Level', '00000068-0000-1000-8000-0026BB765291');
this.setProps({
format: Characteristic.Formats.UINT8,
unit: Characteristic.Units.PERCENTAGE,
maxValue: 100,
minValue: 0,
minStep: 1,
perms: [Characteristic.Perms.READ, Characteristic.Perms.NOTIFY]
});
this.value = this.getDefaultValue();
}) GET] battery (August Smart Lock Pro) | LastUpdate: (Sat Jan 11 2020 18:49:14 GMT+0000 (Coordinated Universal Time)) | Value: (100)
GOOD: [CHARACTERISTIC (function() {
Characteristic.call(this, 'Status Low Battery', '00000079-0000-1000-8000-0026BB765291');
this.setProps({
format: Characteristic.Formats.UINT8,
maxValue: 1,
minValue: 0,
validValues: [0,1],
perms: [Characteristic.Perms.READ, Characteristic.Perms.NOTIFY]
});
this.value = this.getDefaultValue();
}) GET] battery (August Smart Lock Pro) | LastUpdate: (Sat Jan 11 2020 18:49:14 GMT+0000 (Coordinated Universal Time)) | Value: (0)
GOOD: [CHARACTERISTIC (function() {
Characteristic.call(this, 'Charging State', '0000008F-0000-1000-8000-0026BB765291');
this.setProps({
format: Characteristic.Formats.UINT8,
maxValue: 2,
minValue: 0,
validValues: [0,1,2],
perms: [Characteristic.Perms.READ, Characteristic.Perms.NOTIFY]
});
this.value = this.getDefaultValue();
}) GET] batteryStatus (August Smart Lock Pro) | LastUpdate: (Sat Jan 11 2020 18:49:14 GMT+0000 (Coordinated Universal Time)) | Value: (0)
INFO: Added Device: (August Smart Lock Pro | d200b920-ec6f-4e0d-b166-c66e5d2fd8b5)
ALERT: Total Initialization Time: (1 seconds)

######These are the only log entries when send an unlock or lock command (Debug is on)
NOTICE: Sending Device Command: unlock | Value: Nothing | DeviceID: (d200b920-ec6f-4e0d-b166-c66e5d2fd8b5) | SendToLocalHub: (true)

NOTICE: Sending Device Command: lock | Value: Nothing | DeviceID: (d200b920-ec6f-4e0d-b166-c66e5d2fd8b5) | SendToLocalHub: (true)

Device Data - Connected as "Other"

{
"name": "August Smart Lock Pro",
"basename": "August Smart Lock Pro",
"deviceid": "d200b920-ec6f-4e0d-b166-c66e5d2fd8b5",
"status": "ONLINE",
"manufacturer": "Unknown",
"model": "Z-Wave Lock Without Codes",
"deviceNetworkId": "07",
"lastActivity": "2020-01-11T18:55:08+0000",
"capabilities": [
"Actuator",
"Battery",
"Configuration",
"Health Check",
"Lock",
"Refresh",
"Sensor"
],
"commands": [
"configure",
"lock",
"ping",
"refresh",
"unlock"
],
"customflags": [ ],
"attributes": {
"DeviceWatch-DeviceStatus": null,
"DeviceWatch-Enroll": null,
"battery": 100,
"checkInterval": 3600,
"healthStatus": null,
"lock": "unlocked with timeout"
},
"eventHistory": [
"Sat Jan 11 18:55:08 UTC 2020 | [lock] | (unlocked with timeout)", <--- Manually unlocked
"Sat Jan 11 18:40:04 UTC 2020 | [lock] | (locked)", <-- Unknown (maybe status req)
"Sat Jan 11 18:40:04 UTC 2020 | [lock] | (locked)", <-- Unknown (maybe status req)
"Sat Jan 11 18:40:00 UTC 2020 | [null] | (lock)", <-- homekit command
"Sat Jan 11 18:39:58 UTC 2020 | [null] | (unlock)", <-- homekit command
"Sat Jan 11 18:32:57 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:52 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:51 UTC 2020 | [null] | (unlock)",
"Sat Jan 11 18:32:47 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:46 UTC 2020 | [null] | (lock)",
"Sat Jan 11 18:32:41 UTC 2020 | [null] | (unlock)",
"Sat Jan 11 18:32:31 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:26 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:24 UTC 2020 | [null] | (lock)",
"Sat Jan 11 18:32:24 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:22 UTC 2020 | [null] | (unlock)",
"Sat Jan 11 18:32:17 UTC 2020 | [null] | (lock)",
"Sat Jan 11 18:32:06 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:03 UTC 2020 | [lock] | (locked)",
"Sat Jan 11 18:32:00 UTC 2020 | [null] | (unlock)"
]
}

[Feature Request] Add Support for Power Strip Characteristic

is there anyway we can get the power strip feature in HomeKit for power strips that work with SmartThings?

[Feature Request] Motion Sensors/Smoke Detectors not showing under SmartThings options

Is your feature request related to a problem? Please describe.
I’m looking to use this plugin together with:

https://github.com/csdozier/device-concord4

This Smartapp, which creates four object types for a security system-

An alarm system (appears to be shown in HomeKit despite not being selected)
Contact sensors (showing up in the sensors menu on the Smartapp and appears in HomeKit)
Motion sensors (shows up in SmartThings as a thing, but not under any menu in the Smartapp and not in HomeKit)
Smoke detectors (same as the motion sensors)

Describe the solution you'd like
I’m hoping to find a way to access and use those other two device types in HomeKit for automations, etc.

Describe alternatives you've considered
At the moment I’m not entirely sure if there are any alternatives for Concord4 systems that might work better (or at all) with HomeKit, but I’m actively searching.

(BUG) SHM changes on ST side do not reflect on Homebridge side

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 1
Mobile App Version(Not required):
SmartApp Version: 2.0.1
Device Handler Version: N/A
Homebridge Version: 2.0.1
NodeJS Version: 10.17.0

Expected Behavior

Tell us what you think should be happening
When SHM state is changed in ST Classic, the device on the Homebridge side should update to reflect change. When SHM state is changed in Home app, it should be updated in ST Classic

Current Behavior

What happens instead of the expected behavior?
Changes to Smart Home Monitor state do not reflect on the Homebridge/Homekit side. Changes are visible in ST Classic when made from the Home app

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

ST Classic > Homebridge (NOT WORKING)

Change SHM to Armed Stay in ST Classic app
View log in IDE
2:57:43 PM: debug Sending LOCATION Event (alarm system status | ALARMSYSTEMSTATUS: stay) to Homebridge at (x.x.x.x:xxxx)
No event is created in Homebridge
Change is not reflected in iOS Home app

Homebridge > ST Classic (WORKING)

Change SHM to Armed Stay in Home app
View event in Homebridge log
[12/8/2019, 3:00:48 PM][SmartThings-v2]NOTICE: Sending Device Command: stay | Value: Nothing | DeviceID: (alarmSystemStatus_...deviceID) | SendToLocalHub: (true)
Event is logged in IDE
3:00:49 PM: debug Sending LOCATION Event (alarm system status | ALARMSYSTEMSTATUS: stay) to Homebridge at (x.x.x.x:xxxx)
Verify change in ST Classic app

Context

**How has this issue affected you? What are you trying to accomplish?
I am not able to control set SHM device on Homebridge/Homekit side to effect change in ST.

Providing context helps us come up with a solution that is most useful in the real world

Please include a copy of any relevant log output to assist in tracking down the bug

SmartThings v2 with google nest login

I upgraded to v2 and everything was working fine but nest stopped working with my username password. I switched to a google account and then followed all the steps to get auth codes from google. I updated my config.json with all the new info but when homebridge reboots all my SmartThings devices show as failed to update. I take the google auth out for homebridge-nest reboot and everything works as before. So need some advice as where to look to get both SmartThings and nest to work under homebridge.

(BUG) Device Change Event doesnt always happen. HomeKit reports incorrect status

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[X ] That OAuth is Enabled for the SmartApp under the IDE.
[ X] The SmartApp and Device Handler are using the latest code available.
[ SmartApps yes but Device Handlers NO ] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 2
Mobile App Version(Not required):
SmartApp Version: 2.0.4
Device Handler Version: None shown in IDE
Homebridge Version: 0.4.50
NodeJS Version: 12.14.0

Expected Behavior

Tell us what you think should be happening
The device event change should switch to off and on soon as the command is issued for off or on.

Current Behavior

What happens instead of the expected behavior?
In the below case many of the times it doesnt actually change the device event so HomeKit, and Homebridge, doesnt know if the device is truly off or on. So it reports the last known status which is wrong.

[1/4/2020, 5:26:57 AM] [NOTICE]: Sending Device Command: off | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:01 AM] [NOTICE]: Sending Device Command: on | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:14 AM] [NOTICE]: Sending Device Command: off | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:25 AM] [NOTICE]: Sending Device Command: on | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:34 AM] [NOTICE]: Sending Device Command: off | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:35 AM] [INFO]: [Device Change Event]: (back light) [SWITCH] is off
[1/4/2020, 5:27:37 AM] [NOTICE]: Sending Device Command: on | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:47 AM] [NOTICE]: Sending Device Command: on | Value: Nothing | DeviceID: (9e0c7cb7-d882-4932-ace8-031bb5c3b25a) | SendToLocalHub: (true)
[1/4/2020, 5:27:48 AM] [INFO]: [Device Change Event]: (back light) [SWITCH] is on

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
It is impossible to create proper scenes or check for status of devices when this occurs.

Please include a copy of any relevant log output to assist in tracking down the bug

(BUG) v2.1.12 Motion Sensor and Multipurpose Sensor - no status update

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x ] That OAuth is Enabled for the SmartApp under the IDE.
[x ] The SmartApp and Device Handler are using the latest code available.
[ x] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?:15
Mobile App Version(Not required): 2.1
SmartApp Version: 2.1.1"
Device Handler Version:
Homebridge Version: 0.4.50
NodeJS Version:

Expected Behavior

After the introduction of the last final update of 2.1.12, they stopped updating their detector status, everything was working today in the previous version, I'm not sure but it was 2.1.7, but I can be wrong.

Current Behavior

What happens instead of the expected behavior?

Steps to Reproduce (for bugs)

Context

Please include a copy of any relevant log output to assist in tracking down the bug

TypeError: Cannot read property '_events' of undefined

Sentry Issue: HOMEBRIDGE-SMARTTHINGS-1P

TypeError: Cannot read property '_events' of undefined
  File "C:\Users\christoph\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_DeviceCharacteristics.js", line 22, in PlatformAccessory.manageGetCharacteristic
    if (!c._events.get) {
  File "C:\Users\christoph\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_DeviceCharacteristics.js", line 220, in DeviceCharacteristics.energy_meter
    _accessory.manageGetCharacteristic(_service, CommunityTypes.KilowattHours, 'energy');
  File "C:\Users\christoph\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_Accessories.js", line 102, in null.<anonymous>
    this.device_types[svc.name](accessory, svc.type);
  ?, in Array.forEach
  File "C:\Users\christoph\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_Accessories.js", line 99, in ST_Accessories.configureCharacteristics
    svcTypes.forEach((svc) => {
...
(5 additional frame(s) were not displayed)

TypeError: Cannot read property 'includes' of null

Sentry Issue: HOMEBRIDGE-SMARTTHINGS-2Q

TypeError: Cannot read property 'includes' of null
  File "C:\Users\shann\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_Transforms.js", line 335, in Transforms.thermostatSupportedModes
    if (sModes.includes("heat") || sModes.includes("emergency heat") || hasHeatSetpoint)
  File "C:\Users\shann\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_DeviceCharacteristics.js", line 426, in DeviceCharacteristics.thermostat
    validValues: this.transforms.thermostatSupportedModes(_accessory.context.deviceData)
  File "C:\Users\shann\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_Accessories.js", line 102, in null.<anonymous>
    this.device_types[svc.name](accessory, svc.type);
  ?, in Array.forEach
  File "C:\Users\shann\AppData\Roaming\npm\node_modules\homebridge-smartthings-v2\src\ST_Accessories.js", line 99, in ST_Accessories.configureCharacteristics
    svcTypes.forEach((svc) => {
...
(5 additional frame(s) were not displayed)

3-speed fan device type (BUG)

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 44
SmartApp Version: Latest
Device Handler Version: Latest
Homebridge Version: Latest

Expected Behavior

Tell us what you think should be happening

I tested the new 3-speed fan device type available in the SmartApp with a Jasco 3-speed fan controller using the default local execution DTH (Dimmer). When using the Fan device type the device shows in HomeKit as a 0-100% variable speed fan (expected). When using the 3-speed fan device type it just shows up as a dimmer light. I have no idea of HomeKit has a specific device type for 3-speed fans, but guessing the intention is that it does not show up as a dimmer light.

[Feature Request] Local Control On/Off By Device

Is your feature request related to a problem? Please describe.
I have a thermostat which breaks when local control is on. The thermostat is a custom device handler/smartapp for Nexia, available at link below. When I turn local control off it works fine, but of course i lose local control for my other devices.

https://community.smartthings.com/t/how-do-you-control-a-nexia-thermostat-with-a-smartthings-hub/34046

Describe the solution you'd like
Ideally override the local control at the device level, kind of how you can exclude certain device capabilities in config

Describe alternatives you've considered
There is an official Nexia integration but it doesn't show up when configuring devices in the smartapp, so i use this one instead. Bug for official Nexia not working: #52

Additional context
Add any other context or screenshots about the feature request here.

(BUG) Security Alarm Displaying when No Such Device Exists

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: 4
Mobile App Version(Not required):
SmartApp Version: 2�.0.4
Device Handler Version: unsure
Homebridge Version: 0.4.50
NodeJS Version: 10.15.2

Expected Behavior

Apple Home should display two Z-Wave Switches and one Water Sensor

Current Behavior

What happens instead of the expected behavior?
Apple Home displays two Z-Wave Switches, one Water Sensor, AND a Security Alarm

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world
Trying to enable Apple Homekit to control the Z-Wave Devices that are currently controlled by my Samsung Smartthings Hub

Please include a copy of any relevant log output to assist in tracking down the bug

(BUG) ETIMEDOUT on macOS Homebridge since last few updates.

This start happening this week - but none of my switches are working, they turn on and the time out with the ETIMEOUT error

NOTICE: Sending Device Command: on | Value: Nothing | DeviceID: (c6926e79-6b24-422c-be29-ec6639baeb27) | SendToLocalHub: (true)
ERROR: sendStartDirect Error:  'Error: connect ETIMEDOUT 192.168.0.13:39500'

It seems to work sometimes and other times time out, or be laggy. Nothing has really changed my end, I did update the firmware of my Draytek router but I don't think it's that. I'm running latest version and app too.

[Feature Request]

Is your feature request related to a problem? Please describe.
Other capabilities for my fridge.

Describe the solution you'd like
I would love to have capabilities such as toggles for: Power Cool, Power Freeze and the Ice Maker. Additionally, it would be much appreciated if the status of the water filter could be added as well. (Perhaps through HMCharacteristicTypeCurrentAirPurifierState?)

Describe alternatives you've considered
The only alternative to this is using Samsung's own app.

(BUG) Refrigerator shows as always open.

After being added to homekit, my fridge only shows as open and 0 degrees.

(BUG) Button accessory does not function correctly

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ x] That OAuth is Enabled for the SmartApp under the IDE.
[ x] The SmartApp and Device Handler are using the latest code available.
[ x] That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?: All
Mobile App Version(Not required):
SmartApp Version: 2.0.3
Device Handler Version: Not using any DH
Homebridge Version: 0.4.50
NodeJS Version: 9.8.0

Expected Behavior

Pressing button should get passed to Homekit as a Button Press in correct order

Current Behavior

Single press does get logged in console but Homekit does not receive this action. A double press works as intended, if after a double press you do a single press it works properly only once.

Steps to Reproduce (for bugs)

No code or other relevant details other than this started after I migrated to v2

Context

Button presses are useless atm.

PLease ask for anything specific to this since console outputs look normal I don't know what specifically needs to be logged for support.

Cannot see my devices in homekit

I've followed all of the instructions and when I set it all up in the smartthings app it said that I dont have to do anything else accept type in these numbers...

So I need help!

(BUG) Repeated errors in homebridge log file

Verify the following before opening an trouble issue

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

That OAuth is Enabled for the SmartApp under the IDE.
The SmartApp and Device Handler are using the latest code available.
That Both the SmartApps and Device Handlers have been Published for You in the IDE.

About Your Setup

How many devices are detected?:
Mobile App Version(Not required):
SmartApp Version: 2.0.4
Device Handler Version: N/A
Homebridge Version: 0.4.50 (via onzu/docker-homebridge)
NodeJS Version: 12.14.0

Expected Behavior

Tell us what you think should be happening

No errors in log file

Current Behavior

What happens instead of the expected behavior?

Repeated error messages in Homebridge log:

BadRequestError: request aborted
    at IncomingMessage.onAborted (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:231:10)
    at IncomingMessage.emit (events.js:210:5)
    at abortIncoming (_http_server.js:492:9)
    at socketOnClose (_http_server.js:485:3)
    at Socket.emit (events.js:215:7)
    at TCP.<anonymous> (net.js:658:12)

I also see the following error frequently, but less often than the one above:

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at parse (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/body-parser/lib/types/json.js:89:19)
    at /homebridge/node_modules/homebridge-smartthings-v2/node_modules/body-parser/lib/read.js:121:18
    at invokeCallback (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:224:16)
    at done (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:213:7)
    at IncomingMessage.onEnd (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:273:7)
    at IncomingMessage.emit (events.js:215:7)
    at endReadableNT (_stream_readable.js:1184:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at parse (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/body-parser/lib/types/json.js:89:19)
    at /homebridge/node_modules/homebridge-smartthings-v2/node_modules/body-parser/lib/read.js:121:18
    at invokeCallback (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:224:16)
    at done (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:213:7)
    at IncomingMessage.onEnd (/homebridge/node_modules/homebridge-smartthings-v2/node_modules/raw-body/index.js:273:7)
    at IncomingMessage.emit (events.js:215:7)
    at endReadableNT (_stream_readable.js:1184:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

Steps to Reproduce (for bugs)

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant

This occurs without any specific action beyond setup. In case it's relevant, I am using a device handler/smartapp for Flair devices described here

https://github.com/tonesto7/homebridge-smartthings-v2/issues/19

Error also occurs when "Send Homekit Commands locally" is turned off.

Context

**How has this issue affected you? What are you trying to accomplish?
Providing context helps us come up with a solution that is most useful in the real world

Updates to devices managed by smartthings-homebridge seem less reliable than other homebridge plugins. Not sure if these errors are responsible for that.

Please include a copy of any relevant log output to assist in tracking down the bug

tonesto7 / homebridge-smartthings-v2 Goto Github PK

homebridge-smartthings-v2's Introduction

Hi there 👋

homebridge-smartthings-v2's People

Contributors

Stargazers

Watchers

Forkers

homebridge-smartthings-v2's Issues

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

I am not able to check the state of my fridge (in case it is left open) or its temperature.

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

First, I would like to thank you for your project and for being active there. I even took the time to give you a donation even if I am not rich.

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior and ## Current Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Check the following before opening the problem

Configuration information

Expected behavior

Current behavior

Steps to Reproduce (in case of errors)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

I use temperature readings in conjunction with automations of some HomeKit only devices such as iHome outdoor plug to operate space heaters in case my furnace stops working when I’m away.

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Verify the following before opening an trouble issue

About Your Setup

Expected Behavior

First,
I would like to thank you for your project and for being active there. I even took the time to give you a donation even if I am not rich.