SmartThings Community

WTH happened to my great SmartThings system?


#29

I’m have similar issues to you and it sounds like I’ve got some similar products too. When my system started going haywire I lost 1 of 2 garage door controllers (I’ve got the GoControl ones) it took me some time but I finally got it reconnected. Like you ST would just not find it to re-add it, it sounds like you can’t pair it because it may still think it’s paired with a device. Here’s what I did and it worked for me so YMMV. I tried the IOS app to exclude the device and it didn’t seem to do anything. So I pulled out the laptop and while standing on my ladder in the garage balancing a laptop I put the hub in exclusion mode. I got the little box below it that says it’s in exclusion mode for 15 seconds and pushed the button on the side of the controller again. This time it beeped and I waited another 10-15 seconds. I opened the app on my phone and clicked add an item them pressed the button briefly on the controller. It beeped again and ST found it immediately.

Using the exclusion mode on the phone and then re-adding it via the phone produced no results and it never even beeped. The exclusion mode from the website seemed to work for some reason. Worth a shot at bare minimum. Good luck.


(Tim Gray) #30

What I am doing is moving away from SmartThings. No more cloud based for me. I have a high level of technical ability so I am going over to OpenHAB and bringing my Zwave with me. All the zigbee and my Hub2 will be sold on ebay at a fire sale price.

Smart things is unreliable. Even today I am getting door open notifications from this morning, and I’ts 1pm. I have a very healthy zigbee mesh and a Zwave mesh working … bot both Zwave and Zigbee sensors have huge delays unless I reboot the hub. then it works great and then slowly gets bad again.

All this started right after the last update, which is typical with smart Things. their updates break more than they fix.


(Ryan Little) #31

Issue fixed. Had to exclude and readd.


(Johnny H) #32

So…
i’m in bed at 5:30 AM today, and the garage door opens and my phone dings… apparently “I just arrived” home LOL.

So… Solution is to ditch the phone as a presence sensor and purchase a smartthings sensor and just for today at 20% off.
It seemed to be working fine for weeks, then all of a sudden…

So why even have the choice to utilise the phone as a sensor if you are saying its not predictable??


(Nathan H) #33

I personally use my phone as a presence sensor with few problems, but I don’t have anything automatically open or unlock doors based on my presence. The closest thing I do is disarm SHM. I have a keyfob that I use to unlock the door before I get to it.

One thing I looked at doing was using the Wireless Sensor Tags as a backup presence device. Basically, the garage door or front door would only unlock automatically if both sensors showed present. I use a virtual presence sensor and a CoRE piston that adjusts based on the presence of both devices. Then I only use that virtual presence sensor in other automations. The problem I ran into was the stability of the tags, not the phone. You’re also adding another layer which makes it a little less dependable.

One thing I’ve proposed to ST is an auto presence sensor. Basically, something low power that runs off car battery power, has Z-Wave and/or wi-fi, and works as a presence sensor. That way you could, if you have multiple garage doors, have it automatically open the correct door based on which vehicle pulls up. It would also be useful in my example as a backup presence sensor.


#34

It just depends on local conditions. Some people find the phone works better than the presence sensor fob at their house, other people find the opposite is true.

Many of us use a combination of two devices to improve reliability.

Most people start by trying the official SmartThings mobile app just because you already have it. But if it doesn’t work for you there a number of other options you can try.


(Clayton McCord) #35

I was getting a lot of the offline red exclamation points for a while recently. What I have done to completely correct them is to install Pollster and add the devices as they go offline. I have about 6 devices that were going offline consistently and after setting pollster to poll and refresh them they have not dropped offline once.

It is kind of frustrating that we have to use third party tools for basic functions like this, but at least we have the ability to use them. Unlike many other locked down smart home hubs.

Here is the link to pollster for anyone that needs it.


#36

And unfortunately, this adds more stress on the cloud and could contribute to other issues.


(Hendre) #37

I’m on the verge of giving up. For the past 2 weeks, my life has been ruled and complicated by tech that is supposed to make things easier.
My setup is getting worse by the day. Initially, I could bring the devices back online by rebooting the hub, but that does not even help anymore. I’m down to only being able to (apart from the Hue lights, which work ok) control a few items, mostly Samsung devices like the outlet switch. There is no connection to about a third of the Fibaro and Aeon devices and even those showing as connected in the ST app, don’t respond. If I turn device health on, it shows 22 devices as offline. Even devices like door closure sensors and Aeon’s multi-sensors show as disconnected.
I’ve spent many hours on this forum looking for answers, and I’m sure I’ve tried all - nothing helped. I even changed my internet router to a different service to see if the problem is not related to my internet connection.
I’ve even paused almost all of my webCore pistons in case they might be causing excessive traffic on the network.
No idea what to do next apart from calling this project a fail and going back to manual control. Words can’t describe my disappointment, as I went all out and spent crazy amounts of money on this project - even put Z-wave valves in my water supply line! I’ve already spent far more time getting my home setup than what I have available. And I, unfortunately, don’t have the time to start all over with something like Openhab.
I wanted to do this years ago but waited till I thought by now the system should be stable. To me, it feels like everything is barely beta quality. Looking at the history of the ST app should have made me realise that I’m looking for trouble. The system reminds me of the first Android phone - actually, they were a lot more stable than this system.
I’m sorry for blowing off steam like this - I realise is is annoying to read. I’m just, so disappointed that I have a dysfunctional system after spending so much time and money on what I had thought was going to be an awesome system.


(Hendre) #38

@Nhaley pointed out that I should look in the Hub’s Event List to see what’s happening when I run a network repair. This is kind of a revelation, because looking at the HUB, I see that I have a few “ghost” devices which I’ll have to remove as explained by @ahndee.
But I suppose, just as important, I have heaps of the Err 101 errors discussed here.

Just a small portion of the Hub’s Log:

2017-06-18 1:43:48.381 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:48.381 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:48.380 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:48.378 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:48.058 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:45.235 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:45.230 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:45.227 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:45.227 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:45.225 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:42.045 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:42.045 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:42.044 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:42.043 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:42.040 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:39.194 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:39.193 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:39.192 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:39.191 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:39.191 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:36.298 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:36.289 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:36.289 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:36.284 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:36.284 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:33.108 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding
2017-06-18 1:43:33.107 PM SAST
3 hours ago 	HUB 			Err 101: ZW module not respon... 		Err 101: ZW module not responding

(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy) #39

Here’s a weird but possibly useful suggestion:

Switch to a V1 Hub!

I don’t know what the heck is going on with the sudden flurry of Z-Wave issues, but I presume that it is something specific to the firmware and/or Z-Wave “plus” support in Hub V2.

While there are lots of variables in play, my Z-Wave devices (on a Hub V1, forever) have no issues.


(Hendre) #40

When I have time, I’ll check whether the devices going offline all the time, are included in secure mode and report back if I was able to determine a pattern in this regard.


(Hendre) #41

Is there an easier way to determine if a device was included/joined in secure mode than changing the device handler to the Z-Wave Tweaker DH to get a report from the device?
Would you guys say that it is better to connect “unsecurely”, taking into account the current issues some of us have? (Most of my switches are from Fibaro and my impression is that if they are Z-Wave plus devices, you can only pair them securely, which kind of make this question irrelevant I suppose.)


(Hendre) #42

Since I’m still troubleshooting my issues, I was wondering if it is normal for the Hue Bridge to generate this amount of traffic almost continuously? (I just realized that I’m currently not using any Smart App for the Hue lights - ST discovered the Hue Bridge and lights (connected to the bridge) after I removed Hue B Smart. Should I not at least see the Hue Connect app in my list of Smart Apps?)

The amount of traffic generated, seems strange, especially as nothing is happening to the Hue Lights at the moment. It is daytime and they are supposed to be Off.

94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/39', [name:switch, value:off])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/38', [name:color, value:#FFCE78, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:43 AM: debug createChildDeviceEvent('00178825B18B/35', [name:colorTemperature, value:4000, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:46 AM: debug createChildDeviceEvent('00178825B18B/31', [name:saturation, value:99, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:45 AM: debug createChildDeviceEvent('00178825B18B/2', [name:color, value:#FFC463, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:43 AM: debug createChildDeviceEvent('00178825B18B/35', [name:saturation, value:2, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:45 AM: debug createChildDeviceEvent('00178825B18B/10', [name:colorTemperature, value:6536, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:45 AM: debug createChildDeviceEvent('00178825B18B/24', [name:level, value:100, descriptionText:Level has changed to 100%])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/39', [name:hue, value:13, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/12', [name:colorTemperature, value:4032, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/16', [name:saturation, value:20, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:43 AM: debug createChildDeviceEvent('00178825B18B/17', [name:switch, value:off])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:45 AM: debug createChildDeviceEvent('00178825B18B/1', [name:level, value:100, descriptionText:Level has changed to 100%])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/21', [name:hue, value:20, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/21', [name:color, value:#FFCF76, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:43 AM: debug createChildDeviceEvent('00178825B18B/17', [name:level, value:100, descriptionText:Level has changed to 100%])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/13', [name:switch, value:off])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:43 AM: debug createChildDeviceEvent('00178825B18B/17', [name:hue, value:19, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/17', [name:color, value:#FFB141, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:45 AM: debug createChildDeviceEvent('00178825B18B/26', [name:level, value:100, descriptionText:Level has changed to 100%])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/20', [name:hue, value:23, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/13', [name:saturation, value:0, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/13', [name:color, value:#FFEBBC, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:44 AM: debug createChildDeviceEvent('00178825B18B/36', [name:colorTemperature, value:2439, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/4', [name:saturation, value:70, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:41 AM: debug createChildDeviceEvent('00178825B18B/1', [name:colorTemperature, value:2525, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:41 AM: debug createChildDeviceEvent('00178825B18B/5', [name:level, value:100, descriptionText:Level has changed to 100%])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/5', [name:color, value:#F4F9FF, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/8', [name:color, value:#FFC362, descriptionText:Color has changed, displayed:true])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:41 AM: debug createChildDeviceEvent('00178825B18B/5', [name:colorTemperature, value:6536, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/8', [name:saturation, value:70, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/5', [name:hue, value:53, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:41 AM: debug createChildDeviceEvent('00178825B18B/6', [name:colorTemperature, value:2439, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/8', [name:hue, value:22, descriptionText:Color has changed, displayed:false])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:42 AM: debug createChildDeviceEvent('00178825B18B/8', [name:colorTemperature, value:2421, descriptionText:Color temperature has changed])
    94803faa-d8cf-46dd-8387-f4a499910859  9:33:41 AM: debug createChildDeviceEvent('00178825B18B/28', [name:level, value:100, descriptionText:Level has changed to 100%])

(Hendre) #43

After running the Z-wave repairs yesterday evening, I left the system overnight and rebooted the hub this morning. Until I left home for work, all devices were responding almost immediately when turned on/off from the ST App.

Without changing anything and with very little going on at home, I kept an eye on the system (looking at the logs and turning 3 specific sets of lights on/off every half hour or so. Everything went well, until I checked again a few minutes ago (after not looking at the system for an hour) and now the same devices are not responding anymore. I managed to turn on of them on, but it only responded after about 30 seconds between the time I push the icon in the App, until it showed as being on.

Looking at the Hub Events, I noticed this (unfortunately, I did not check the events log of the Hub this morning when devices were responding to changes from the ST app’s side):

Date	Source	Type	Name	Value	User	Displayed Text
2017-06-19 10:58:25.343 AM SAST
moments ago	HUB		ssdpTerm	upnp:rootdevice		devicetype:04, mac:00178825B18B, networkAddress:C0A80014, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:25.149 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:b...		devicetype:04, mac:00178825B18B, networkAddress:C0A80014, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:25.145 AM SAST
moments ago	HUB		ssdpTerm	uuid:2f402f80-da50-11e1-9b23-...		devicetype:04, mac:00178825B18B, networkAddress:C0A80014, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:20.123 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:20.116 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:20.055 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:94A1A2AA8CAA, networkAddress:C0A8004A, deviceAddress:C000, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:20.055 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:20.054 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:20.054 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:94A1A2AA8CAA, networkAddress:C0A8004A, deviceAddress:C000, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:20.053 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:19.327 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:b...		devicetype:04, mac:00178825B18B, networkAddress:C0A80014, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:19.325 AM SAST
moments ago	HUB		ssdpTerm	uuid:2f402f80-da50-11e1-9b23-...		devicetype:04, mac:00178825B18B, networkAddress:C0A80014, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:19.325 AM SAST
moments ago	HUB		ssdpTerm	upnp:rootdevice		devicetype:04, mac:00178825B18B, networkAddress:C0A80014, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU...
2017-06-19 10:58:18.593 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:18.005 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:18.005 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD6E7D60, networkAddress:C0A80084, deviceAddress:EA61, stringCount:04, ssdpPath:/, ssdpUSN:uuid:07e687f...
2017-06-19 10:58:18.004 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD6E7D60, networkAddress:C0A80084, deviceAddress:EA61, stringCount:04, ssdpPath:/, ssdpUSN:uuid:07e687f...
2017-06-19 10:58:18.004 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD6E7D60, networkAddress:C0A80084, deviceAddress:EA61, stringCount:04, ssdpPath:/, ssdpUSN:uuid:07e687f...
2017-06-19 10:58:18.004 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:38D547B50EC0, networkAddress:C0A80009, deviceAddress:2328, stringCount:04, ssdpPath:/plugins/UPnP/MediaRend...
2017-06-19 10:58:18.001 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD6E7D60, networkAddress:C0A80084, deviceAddress:EA61, stringCount:04, ssdpPath:/, ssdpUSN:uuid:07e687f...
2017-06-19 10:58:17.893 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD740DF0, networkAddress:C0A800AA, deviceAddress:EA61, stringCount:04, ssdpPath:/, ssdpUSN:uuid:8815844...
2017-06-19 10:58:17.892 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD740DF0, networkAddress:C0A800AA, deviceAddress:EA61, stringCount:04, ssdpPath:/, ssdpUSN:uuid:8815844...
2017-06-19 10:58:17.892 AM SAST
moments ago	HUB		ssdpTerm	urn:schemas-upnp-org:device:M...		devicetype:04, mac:0005CD740DF0, networkAddress:C

The question is, is this normal activity of is something generating garbage on my Z-Wave network?


(Hendre) #44

Because devices stopped responding once again, I rebooted the hub (from within the IDE). Immediately after the reboot, I noticed lots of Err 101 errors in the Hub’s Events List.
From the IDE, I disabled the Z-Wave Module and re-enabled it and devices started coming online. They are also responding correctly to input from the ST App.
However, I have now noticed the following, which I have missed up to now and which appears to be abnormal:


As I mentioned, currently the devices are responding despite of this - is the Z-Wave supposed to show as “Not functional”. I’m getting worried that my hub is faulty.


#45

“Zwave not functional” is not good. Assuming you did re-enable zwave again, that’s saying that the radio inside the hub is not working. Definitely report it to support.


(Hendre) #46

Thanks @JDRoberts - I did so after I saw it and came across a post in another thread where a guy had very similar issues as what I’m experiencing after updating his hub to the current firmware. I don’t have much hope though that Samsung will replace the Hub, as I’m outside the officially supported area. I’ve started reading about the migration process - seems like a tedious process. (Some of my devices were installed in the roof-ceiling and are difficult to access.) But I’m so disappointed and desperate at this stage, I’ll do the migration with a smile if that is going to resolve my issues.


(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy) #47

‘upnp’ indicates IP (lan) device discovery etc… Nothing to do with Z-Wave.


(Hendre) #48

OK, so possible something like the MediaRenderer app looking for DNLA devices?