Author Topic: Any issues with the latest SmartThings patch? Mine stopped working  (Read 5854 times)

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #15 on: January 03, 2017, 03:44:42 pm »
Filtered though a ton of pings & found the following possibly relevant logs. Everything else was just ping or the device rebooting or reconnecting due to some network or power issues. It's a SmartThings 2 by the way with the batteries.

2017-01-02 1:43:34.817 PM MST
1 day ago   HUB      zbjoin: {"dni":"2742","d":"0013A20040BDE6FA","capabilities":"00","endpoints":[{"simple":"38 0104 000   zbjoin: {"dni":"2742","d":"00...      zb

2017-01-02 1:13:11.363 PM MST
1 day ago   HUB      catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00 00 000000F8FF0727000A0010AEB0C3B0C3C5C7CACBCCD2   catchall: 0000 8038 00 00 014...      catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00...

Code: [Select]
zw device: 18, command: 2001, payload: FF
Name Value
archivable true
date 2017-01-03 12:30:09.686 AM MST (2017-01-03T07:30:09.686Z)
description zw device: 18, command: 2001, payload: FF
displayed false
eventSource HUB
hubId 316da450-2919-492f-8767-1637469a5c3c
id 74ce0360-d186-11e6-83b4-1201714b010e
isStateChange false
isVirtualHub false
linkText Home Hub
locationId 8a89578d-9b9b-4e9e-8131-e721aa70a097
name zw device: 18, command: 2001, payload: FF
rawDescription zw device: 18, command: 2001, payload: FF
translatable false
unixTime 1483428609686
value zw device: 18, command: 2001, payload: FF
viewed false

Code: [Select]
zbjoin: {"dni":"2742","d":"0013A20040BDE6FA","capabilities":"00","endpoints":[{"simple":"38 0104 000A 00 03 0000 0101 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"39 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"40 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"}]}
Name Value
archivable true
date 2017-01-02 1:43:34.817 PM MST (2017-01-02T20:43:34.817Z)
description zbjoin: {"dni":"2742","d":"0013A20040BDE6FA","capabilities":"00","endpoints":[{"simple":"38 0104 000A 00 03 0000 0101 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"39 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"40 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"}]}
displayed false
eventSource HUB
hubId 316da450-2919-492f-8767-1637469a5c3c
id 2142c910-d12c-11e6-a589-12cba7846726
isStateChange false
isVirtualHub false
linkText Home Hub
locationId 8a89578d-9b9b-4e9e-8131-e721aa70a097
name zbjoin: {"dni":"2742","d":"0013A20040BDE6FA","capabilities":"00","endpoints":[{"simple":"38 0104 000
rawDescription zbjoin: {"dni":"2742","d":"0013A20040BDE6FA","capabilities":"00","endpoints":[{"simple":"38 0104 000A 00 03 0000 0101 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"39 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"40 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"}]}
translatable false
unixTime 1483389814817
value zbjoin: {"dni":"2742","d":"0013A20040BDE6FA","capabilities":"00","endpoints":[{"simple":"38 0104 000A 00 03 0000 0101 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"39 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","model":"Coop Boss"},{"simple":"40 0104 0302 00 01 0402 00","application":"0A","manufacturer":"Solar-Current","mode
l":"Coop Boss"}]}
viewed false

Code: [Select]
catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00 00 000000F8FF0727000A0010AEB0C3B0C3C5C7CACBCCD2D3B2CFB7C5
Name Value
archivable true
date 2017-01-02 1:13:11.363 PM MST (2017-01-02T20:13:11.363Z)
description catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00 00 000000F8FF0727000A0010AEB0C3B0C3C5C7CACBCCD2D3B2CFB7C5
displayed false
eventSource HUB
hubId 316da450-2919-492f-8767-1637469a5c3c
id e265c930-d127-11e6-b882-0638dd9e0a0a
isStateChange false
isVirtualHub false
linkText Home Hub
locationId 8a89578d-9b9b-4e9e-8131-e721aa70a097
name catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00 00 000000F8FF0727000A0010AEB0C3B0C3C5C7CACBCCD2
rawDescription catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00 00 000000F8FF0727000A0010AEB0C3B0C3C5C7CACBCCD2D3B2CFB7C5
translatable false
unixTime 1483387991363
value catchall: 0000 8038 00 00 0140 00 0000 00 00 0000 00 00 000000F8FF0727000A0010AEB0C3B0C3C5C7CACBCCD2D3B2CFB7C5
viewed false

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #16 on: January 03, 2017, 03:56:06 pm »
It should install the device type automatically. You don't need to download any device types now.   I wonder if you need to delete the coopboss device type from your IDE and then do the install.  Ouch sure sorry for all the problems. 

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #17 on: January 03, 2017, 04:24:39 pm »
That looks like good traffic not seeing any errors.  Tomorrow I will setup a new unit and see if it has any problems joining. 

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #18 on: January 04, 2017, 09:17:55 am »
This morning I pulled a new unit off the shelf and connected it to SmartThings.  I connected it to Hub v2 Rev E with firmware version 000.016.00009.  The IOS version of the SmartThings client was Version: 2.2.3 (1357).  They have changed the install process of new devices yet again (I think it gets better every time) it is just hard to keep the documentation updated.  Since you had installed the custom device type manually I suggest you follow these steps (very sorry you have to do this yet again):

1) Remove the CoopBoss from the ZigBee network by removing the power.  Then hold down the button on the PCB and plug it back in.  This will tell the CoopBoss to remove itself from the ZigBee network.  This also resets the door current so you will have to re-calibrate your door as instructed in the manual.  When your done with this step unplug the CoopBoss for now.

2) Go into your SmartThings IDE and find the CoopBoss under my devices and delete it.  Make sure you delete all duplicates if they exist.

3) While your in the IDE go to the My Device Handlers tab and delete all CoopBoss device types you no longer need them.  The CoopBoss device type is now built into the SmartThings core driver database.

4) At this point you can install your CoopBoss as I did in this video I made this morning.  First turn on the power to the CoopBoss then add it as I did in the video.  Here is the video link.  https://www.youtube.com/watch?v=sa6oAJu3hEY

5) After your reconnected please don't forget to reset your door close current.

I also attached what a screen shot of my hub's join process looked like in the hub log:

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #19 on: January 04, 2017, 10:54:31 am »
Will likely be a few days. 20 degrees out & a foot of snow due this afternoon & tomorrow. I expect the wife will just close the coop & nobody is going out for a bit. Might be able to crack it open & reset it on my way back in from plowing though.

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #20 on: January 04, 2017, 03:04:49 pm »
Understand.  Why couldn't this have happened in the summer!! I will keep checking for an update. 

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #21 on: January 05, 2017, 05:35:24 pm »
Made the discovery that the SmartThings multipurpose sensor is actually Zigbee... Thought it was Z-wave. It looks like I have a good connection to the CoopBoss. Things are a little funky as I deleted it out of SmartThings but haven't gone out to reset the CoopBoss. It's 2 degrees ferenheight here right now with 3" of snow, might be a bit. Looks like I have good signal though & the Xstick is about 5' away from the SmartThings hub.

D052A8358AD50001 - SmartThings hub
000D6F000B193E27 - SmartThings multipurpose sensor
0013A20040A3AD63 - My new Xstick
D052A8358AD50001 - CoopBoss


John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #22 on: January 06, 2017, 05:17:34 am »
Yes that looks like a good radio connection!  Curious to see how it works once you get it reinstalled.  If you still see issues we can now use that xBee stick to get a running log from the coopboss.   

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #23 on: January 08, 2017, 04:26:41 pm »
Decent enough weather today. Reset the hardware & re-added it to Smartthings. Custom definitions were removed earlier. Seems to be working several cycles & 15 minutes later. Keeping my fingers crossed, but it looks good so far.

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #24 on: January 09, 2017, 10:58:58 pm »
Still working, seems to have been something funky with the old custom definition.

Is there any need to install the custom SmartApps? Or is it all integrated into the new native definition?

I'm trying to re-create my routines to open the door after we get up during the week or weekend & I'm going nuts trying to remember where you can configure that.

Checking my CoopBoss under Turn on/off light or switch  or light doesn't open or close it (I assume its toggling one of the outlet relays). I don't see it under Open/close garage doors either. It's been so long since I set them up before the issues I dont remember where I configured it. Or is the open/close option from one of the SmartApps?

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #25 on: January 10, 2017, 05:32:31 am »
The smart-app for alerting when your door is jammed went through certification and was approved.  But for some reason (as of the last time I check) you still had to install it manually.  As for the other smart-apps they should work but I didn't submit them for approval. I wonder if you were using the beta custom device type that had the lock cluster and you were using that in your automation.  Unfortunately the certified driver does not treat the door as a lock.

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #26 on: January 11, 2017, 11:52:00 pm »
Any chance the certified definition will be updated to support the lock/unlock interface? Or do I need  to look at going back to  a custom definition if I want to get that functionality?

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #27 on: January 12, 2017, 05:18:32 am »
Currently I don't have plans to go through the certification process again.  It is pretty long and drawn out.  However, SmartThings just made some major enhancements to the development environment and if they make significant changes to the mobile app I will most likely rewrite the interface and resubmit.

Would it be possible to do what you want if I created a virtual switch for the coop's door?  When you turn the switch on the door would close and off open?  That way you could include the switch in automaton routines.  It would require some setup (in the IDE) on your part but I bet it would work.  Let me know I will kick that around if it will help.

Fallon

  • Guest
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #28 on: January 14, 2017, 12:44:38 am »
I think i'd be fine with a virtual switch to script  opening & closing  activities. No problems messing around in the IDE at all to impliment. I can read & write code, but I'm  by no means a coder.

John Rucker (Solar-Current.com)

  • Administrator
  • Jr. Member
  • *****
  • Posts: 53
    • View Profile
Re: Any issues with the latest SmartThings patch? Mine stopped working
« Reply #29 on: January 21, 2017, 05:09:54 am »
I just posted a virtual CoopBoss custom device handler and virtual coopboss manager SmartApp to http://johnrucker.github.io/CoopBoss-H3Vx/.  I have been testing it the last couple of days and it is working great.  I have also created a install video to walk you through setting it all up.  Basically what it does is allow your CoopBoss door to respond to on / off and lock / unlock commands so you can include it in SmartThings automations.  It allows us to control our coopboss with the amazon echo.  Its a little clunky but we can say "Alexa, turn on north coop door" and she will close the door! 

The virtual CoopBoss also has a set of open / close contacts that represent the door status.  If they are closed the door is closed.  You can include these contacts in your SmartThings Home Monitor routines.  I have mine set to alert me if the coop door is still open 45 minutes after sunset. 

Please let me know if you problems with this!!

Best regards!