search

tonesto7 / homebridge-smartthings

SmartThings Homebridge Plugin
383 stars 766 forks source link

[BUG] Can't Add Homebridge Plugin to Apple Home After V2.1 Upgrade #315

Closed pizzinini closed 4 years ago

pizzinini commented 4 years ago

Any idea? Thank you!

tonesto7 commented 4 years ago

@cladmonitor I sent you a PM with my info on the ST Community

tonesto7 commented 4 years ago

@cladmonitor One thing to try is to use the attribute filters in the SmartApp to filter out Temp from the button and add it

tonesto7 commented 4 years ago

So I hit a minor roadblock with the new button design that I need to overcome. So I might be another day or two :(

roberkane212 commented 4 years ago

@tonesto7 thanks for the update. Is this the ST button you are working on?

tonesto7 commented 4 years ago

I haven't got mine yet. I'm making the buttons dynamic meaning if you pick a single child button it will behave the way it did before. Now if you choose the parent button it will create a section for each button (See the screenshot above)

I'm basically just stuck on getting the right button number event to the correct sub-button

roberkane212 commented 4 years ago

@tonesto7 i like that new option. Looks really cool

roberkane212 commented 4 years ago

@tonesto7 not to bother you with yet another thing lol. Because trust me this is way more important o me than the other. However did you ever get to look into the power strip option?

tonesto7 commented 4 years ago

I haven't even looked at it yet. Once I get this plugin rock solid I promise to give it a look over.

tonesto7 commented 4 years ago

I just wanted to provide an update. It seems a good night's rest has allowed me to resolve my hang-up with the new button design.
I have it working now and I'm just doing some optimization and testing.

With that said I was doing some research yesterday on whether other plugins have experienced issues with StatelessProgrammableSwitch Service.

The homebridge-hue plugin reported the exact same thing and like here only occurs for certain people. So I can't guarantee these new changes are going to be a cure-all, but at least the implementation will be done correctly this time.

The next notice from me here will be with the released plugin announcement.

roberkane212 commented 4 years ago

@tonesto7 thanks man and thanks for all your work on this much appreciated. Wanted to ask another question. Is it had if I don’t get that sentry machine to come up in logs?

roberkane212 commented 4 years ago

NeverMind it’s there

tonesto7 commented 4 years ago

OMG... I am such an idiot... The whole problem was with a type in the attribute name. It's literally the only item that remained in the button code refactor.

roberkane212 commented 4 years ago

@tonesto7 dont be so hard on yourself , you’ve been working hard to get us all happy. So all we can do is appreciate your time and effort

tonesto7 commented 4 years ago

The good news is I will v2.2 release in the next 45 and the buttons are better than ever now.

roberkane212 commented 4 years ago

@tonesto7 Great news!!!!

scoobaspeaz commented 4 years ago

Just as a side question because this thread got me thinking...how do I know if I buy something at the store thats SmartThings compatible that it will work with this plugin? Do most things work but just need some tweaks or is there a specific list of things this plugin supports?

tonesto7 commented 4 years ago

If it supports native ST capabilities it will very likely work.

tonesto7 commented 4 years ago

@roberkane212 Go figure right before i'm ready to release I'm noticing something weird.
It's suddenly not grouping the temp, button, battery into a single accessory. I want to solve it before I release it. Hang tight

roberkane212 commented 4 years ago

@tonesto7 no worries like I told you I’m good I’m 2.0.10 until the update rolls around

tonesto7 commented 4 years ago

@roberkane212 Ok, just pushed out the v2.2.0 update.

Make sure to update the SmartApp too. Let me know whether it works for you or now

roberkane212 commented 4 years ago

@tonesto7 how do I update the app?

tonesto7 commented 4 years ago

just use the github integration or copy/paste/publish over the existing code

roberkane212 commented 4 years ago

@tonesto7 now I’m a little confused lol sorry. Copy and paste what? And all I see in the github is the same instructions as before

roberkane212 commented 4 years ago

@tonesto7 do you maybe have a link?

scoobaspeaz commented 4 years ago

@roberkane212

  1. go to SmartThings IDE (account.smartthings.com)
  2. click on My smart apps
  3. click button "update from repo"
  4. Click the checkmark box in the obsolete
  5. bottom right corner checkmark the publish box
  6. Click execute update.

Once its finished open up Homebridge v2 on your SmartThings app and you will see its version 2.2.0

roberkane212 commented 4 years ago

@tonesto7 nothing I’m obsolete box, is there something I did wrong?

roberkane212 commented 4 years ago

I got it never mind sorry

roberkane212 commented 4 years ago

@tonesto7 i got this error

ERROR: initializeAccessory (fromCache: false) Error:Cannot read property 'toString' of undefined TypeError: Cannot read property 'toString' of undefined at PlatformAccessory.addService (/usr/lib/node_modules/homebridge/lib/platformAccessory.js:54:59) at PlatformAccessory.getOrAddServiceByName (/usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:221:24) at DeviceCharacteristics.button (/usr/lib/node_modules/homebridge-smartthings-v2/src/ST_DeviceCharacteristics.js:174:40) at /usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:107:44 at Array.forEach (:null:null) at ST_Accessories.configureCharacteristics (/usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:104:22) at ST_Accessories.initializeAccessory (/usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:67:25) at ST_Platform.updateDevice (/usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:224:55) at /usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:184:61 at Array.forEach (:null:null) at /usr/lib/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:184:38 at processTicksAndRejections (internal/process/task_queues.js:94:5)

cladmonitor commented 4 years ago

I upgraded smartapp and plugin and I'm getting an error after adding the button.

[1/16/2020, 7:53:40 pm] [DEBUG]: Configure Cached Accessory: Button, UUID: 4b22e7f0-418c-405f-9674-9bbe7a05578b [1/16/2020, 7:53:40 pm] [DEBUG]: Initializing Cached Device 60449248-b8c4-4b8d-a668-e9ed2b426912

[1/16/2020, 7:53:40 pm] [ERROR]: initializeAccessory (fromCache: true) Error:Cannot read property 'toString' of undefined TypeError: Cannot read property 'toString' of undefined at PlatformAccessory.addService (/usr/local/lib/node_modules/homebridge/lib/platformAccessory.js:54:59) at PlatformAccessory.getOrAddServiceByName (/usr/local/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:221:24) at DeviceCharacteristics.button (/usr/local/lib/node_modules/homebridge-smartthings-v2/src/ST_DeviceCharacteristics.js:174:40) at /usr/local/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:107:44 at Array.forEach () at ST_Accessories.configureCharacteristics (/usr/local/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:104:22) at ST_Accessories.initializeAccessory (/usr/local/lib/node_modules/homebridge-smartthings-v2/src/ST_Accessories.js:67:25) at ST_Platform.configureAccessory (/usr/local/lib/node_modules/homebridge-smartthings-v2/src/ST_Platform.js:238:59) at Server._configCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:386:24) at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:93:8) at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10) at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22) at Module._compile (internal/modules/cjs/loader.js:1144:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1164:10) at Module.load (internal/modules/cjs/loader.js:993:32) at Function.Module._load (internal/modules/cjs/loader.js:892:14) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12) at internal/main/run_main_module.js:17:47 [1/16/2020, 7:53:40 pm] [INFO]: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded!

cladmonitor commented 4 years ago

I deleted "accessories" and it seems to resolve that, seems to be related to old cached accessories. I'll test some of the functions but its awesome to see a button in my homeKit :D

cladmonitor commented 4 years ago

hmm so its doing what it did originally after switching to v2, this is hard to explain. If I press it once, HK sees the action, but no other single presses work. I have to use another action the next time such as a hold or double press. So it seems you cant do the same action more than once.

tonesto7 commented 4 years ago

In my experience, it will only execute if the devices are not in the state the action is designed to perform.

roberkane212 commented 4 years ago

@tonesto7 mine worked ok for a little after deleting accessories, however minutes later everything crashed like before :(

tonesto7 commented 4 years ago

well, I give up. I can't break it on my side I've tried i have every different kind of button and it works every time. Make sure you are selecting buttons under the Define Device Type inputs.

cladmonitor commented 4 years ago

This is hard for me to articulate since Im trying to explain physical states. the button is acting like a toggle and not a button.

Once I single press it will only do a different action (hold or double press) so in effect its a three position switch and not a button. I'm not sure this is "by design" since physically its a momentary switch and not a toggle switch.

Mine has been running on my end for a while with no issues so Im not sure what is crashing on his end.

tonesto7 commented 4 years ago

This is hard for me to articulate since Im trying to explain physical states. the button is acting like a toggle and not a button.

When you explain it this way I understand what you are saying.
Let me see if there is something I'm overlooking. I hate how little documentation and examples there are for these StatelessSwitches.

cladmonitor commented 4 years ago

I have to thank my wife for that she helped me re-explain it :P If it helps your plugin logs the correct interaction with the button, its just not making it to homeKit.

roberkane212 commented 4 years ago

@tonesto7 ok so mine is working perfectly now, just got to get my switches so work with the automations now. Thank you so much!!!!!!

tonesto7 commented 4 years ago

@roberkane212 I'm confused! I thought you said it was crashing you homebridge again?

roberkane212 commented 4 years ago

@tonesto7 it was so I deleted accessories and persist folders. Run homebridge and I’m good. Everything works, my reality switch and TP-Link light bulb are a little off, but buttons are working perfect. Once I can figure out the bulb and switch I should be ok. It just gives me a no response for a couple presses then works. Not sure what the issue is with that, but overall it’s working well now

pizzinini commented 4 years ago

The Aeon Minimote is really cool now... the Xiaomi Magic Cubes work, too. Thank you for all the hard work!

roberkane212 commented 4 years ago

@tonesto7 yes thank you so much for all the hard work!!!

tonesto7 commented 4 years ago

I’m going to close this issue out as it’s getting pretty long. Any new issues can be opened as new items. I will attempt to see how we can make the buttons repeatable but there is little documentation about this specific characteristic.

ultrathew commented 4 years ago

@tonesto7 - Although adding buttons no longer crashes my HomeKit instance, they only work sporadically on my Aeon Minimote. All the presses and holds register fine in the Homebridge logs, but rarely actually perform the action programmed to each button. I can tell when a button press is actually going to work when I see it icon bounce slightly in the Home app. There doesn't appear to be any rhyme or reason why this is. The only potentially helpful info I can offer is that performing a long press tends to make the same button work on press and long press, but it's always short-lived and eventually stops working again. Should I start a new item for this? Thanks!

cladmonitor commented 4 years ago

Matthew if you see my comment previously could it be that it won’t let you preform the same press type more than once.

Try this. Hold the button see if it registers as a hold Double press and see if it registers as a double press Single press and see if it registers as a single. Keep doing the above and see if it works with no issue. If it does think it’s related to what I’m seeing with my implementation as well.

On Fri, Jan 17, 2020 at 10:32 AM Matthew Chiavelli notifications@github.com wrote:

@tonesto7 https://github.com/tonesto7 - Although adding buttons no longer crashes my HomeKit instance, they only work sporadically on my Aeon Minimote. All the presses and holds register fine in the Homebridge logs, but rarely actually perform the action programmed to each button. I can tell when a button press is actually going to work when I see it icon bounce slightly in the Home app. There doesn't appear to be any rhyme or reason why this is. The only potentially helpful info I can offer is that performing a long press tends to make the same button work on press and long press, but it's always short-lived and eventually stops working again. Should I start a new item for this? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tonesto7/homebridge-smartthings-v2/issues/45?email_source=notifications&email_token=AH2UNQ5S7GGYNDLIORIW6VLQ6H2UXA5CNFSM4KETNJDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJISIJQ#issuecomment-575743014, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH2UNQYRMUQCOH4PH4C57ODQ6H2UXANCNFSM4KETNJDA .

-- Thanks, Eric Sakariasen CTO - Connetic Corp http://www.connetic.com IT services

instagram http://www.instagram.com/cladmonitor - twitter http://www.twitter.com/cladmonitor - facebook http://www.facebook.com/cladmonitor - web http://www.e-n-a.net

ultrathew commented 4 years ago

Hi @cladmonitor - when you say "registers", do you mean seeing it show up in the Homebridge logs? If so, both button states my device supports (press and long press) have consistently shown up instantly in the log, it just doesn't seem to be getting to HomeKit. Below is an example showing the inconsistent behavior. FWIW, Button 1 controls a Hue light via the Philips Hue Bridge v2, Button 2 controls the same light with different color settings, Button 3 launches a HomeKit scene, Button 4 controls a SmartThings Switch

[1/17/2020, 6:47:45 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed [1/17/2020, 6:47:49 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (1) | Button Value: held Button Press Event... | Button Number: (1) | Button Value: held Button Press Event... | Button Number: (1) | Button Value: held Button Press Event... | Button Number: (1) | Button Value: held [1/17/2020, 6:47:51 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed [1/17/2020, 6:47:53 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (2) | Button Value: held Button Press Event... | Button Number: (2) | Button Value: held Button Press Event... | Button Number: (2) | Button Value: held Button Press Event... | Button Number: (2) | Button Value: held [1/17/2020, 6:47:54 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed [1/17/2020, 6:47:56 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (3) | Button Value: held Button Press Event... | Button Number: (3) | Button Value: held Button Press Event... | Button Number: (3) | Button Value: held Button Press Event... | Button Number: (3) | Button Value: held [1/17/2020, 6:47:58 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed [1/17/2020, 6:48:00 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held [1/17/2020, 6:48:03 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held [1/17/2020, 6:48:03 pm] [SmartThings-v2] NOTICE: Sending Device Command: off | Name: (Mud room Light) | DeviceID: (b215fd4b-f9b2-44dc-8be9-9ea1be2273b9) | SendToLocalHub: (true) Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed [1/17/2020, 6:48:16 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed [1/17/2020, 6:48:17 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed [1/17/2020, 6:48:18 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed [1/17/2020, 6:48:18 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed [1/17/2020, 6:48:18 pm] [SmartThings-v2] NOTICE: Sending Device Command: on | Name: (Mud room Light) | DeviceID: (b215fd4b-f9b2-44dc-8be9-9ea1be2273b9) | SendToLocalHub: (true) [1/17/2020, 6:48:19 pm] [SmartThings-v2] INFO: [Device Change Event]: (Mud room Light) [SWITCH] is on Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held [1/17/2020, 6:48:26 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held [1/17/2020, 6:48:26 pm] [SmartThings-v2] NOTICE: Sending Device Command: off | Name: (Mud room Light) | DeviceID: (b215fd4b-f9b2-44dc-8be9-9ea1be2273b9) | SendToLocalHub: (true) [1/17/2020, 6:48:27 pm] [SmartThings-v2] INFO: [Device Change Event]: (Mud room Light) [SWITCH] is off

cladmonitor commented 4 years ago

No, I mean to say try my steps and see if HomeKit actually registers the presses. The log always registers the press in my case but HomeKit only works if I complete a separate action each time (like my example).

On Fri, Jan 17, 2020 at 10:50 AM Matthew Chiavelli notifications@github.com wrote:

Hi @cladmonitor https://github.com/cladmonitor - when you say "registers", do you mean seeing it show up in the Homebridge logs? If so, both button states my device supports (press and long press) have consistently shown up instantly in the log, it just doesn't seem to be getting to HomeKit. Below is an example showing the inconsistent behavior. FWIW, Button 1 controls a Hue light via the Philips Hue Bridge v2, Button 2 controls the same light with different color settings, Button 3 launches a HomeKit scene, Button 4 controls a SmartThings Switch

[1/17/2020, 6:47:45 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed [1/17/2020, 6:47:49 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (1) | Button Value: held Button Press Event... | Button Number: (1) | Button Value: held Button Press Event... | Button Number: (1) | Button Value: held Button Press Event... | Button Number: (1) | Button Value: held [1/17/2020, 6:47:51 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed [1/17/2020, 6:47:53 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (2) | Button Value: held Button Press Event... | Button Number: (2) | Button Value: held Button Press Event... | Button Number: (2) | Button Value: held Button Press Event... | Button Number: (2) | Button Value: held [1/17/2020, 6:47:54 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed [1/17/2020, 6:47:56 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (3) | Button Value: held Button Press Event... | Button Number: (3) | Button Value: held Button Press Event... | Button Number: (3) | Button Value: held Button Press Event... | Button Number: (3) | Button Value: held [1/17/2020, 6:47:58 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed [1/17/2020, 6:48:00 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held [1/17/2020, 6:48:03 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held [1/17/2020, 6:48:03 pm] [SmartThings-v2] NOTICE: Sending Device Command: off | Name: (Mud room Light) | DeviceID: (b215fd4b-f9b2-44dc-8be9-9ea1be2273b9) | SendToLocalHub: (true) Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed Button Press Event... | Button Number: (1) | Button Value: pushed [1/17/2020, 6:48:16 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed Button Press Event... | Button Number: (2) | Button Value: pushed [1/17/2020, 6:48:17 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed Button Press Event... | Button Number: (3) | Button Value: pushed [1/17/2020, 6:48:18 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed Button Press Event... | Button Number: (4) | Button Value: pushed [1/17/2020, 6:48:18 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is pushed [1/17/2020, 6:48:18 pm] [SmartThings-v2] NOTICE: Sending Device Command: on | Name: (Mud room Light) | DeviceID: (b215fd4b-f9b2-44dc-8be9-9ea1be2273b9) | SendToLocalHub: (true)

room Light) [SWITCH] is on Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held Button Press Event... | Button Number: (4) | Button Value: held [1/17/2020, 6:48:26 pm] [SmartThings-v2] INFO: [Device Change Event]: (Minimote) [BUTTON] is held [1/17/2020, 6:48:26 pm] [SmartThings-v2] NOTICE: Sending Device Command: off | Name: (Mud room Light) | DeviceID: (b215fd4b-f9b2-44dc-8be9-9ea1be2273b9) | SendToLocalHub: (true)

room Light) [SWITCH] is off

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tonesto7/homebridge-smartthings-v2/issues/45?email_source=notifications&email_token=AH2UNQ3CK26DRLU2KCMMQZTQ6H4YZA5CNFSM4KETNJDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJIT47I#issuecomment-575749757, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH2UNQ2OJHFKFQT7WK7KZ7TQ6H4YZANCNFSM4KETNJDA .

-- Thanks, Eric Sakariasen CTO - Connetic Corp http://www.connetic.com IT services

instagram http://www.instagram.com/cladmonitor - twitter http://www.twitter.com/cladmonitor - facebook http://www.facebook.com/cladmonitor - web http://www.e-n-a.net

tonesto7 commented 4 years ago

I’m trying to figure out how to stop this, but the documentation\examples are sparse.

I could use some extra eyes searching for suggestions.

With that said let move this to a new issue.