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.)
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%])
1 Like
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?
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.
“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.
1 Like
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.
1 Like
‘upnp’ indicates IP (lan) device discovery etc… Nothing to do with Z-Wave.
2 Likes
OK, so possible something like the MediaRenderer app looking for DNLA devices?
Thanks, for an excellent explanation. Much appreciated.
1 Like
So tired of devices being unavailable. While it is extremely frustrating to me, and very time consuming, the worst part is the family dealing with the issues. You know I keep hearing… our house was fine before I started all this smart stuff. Granted, it becomes un…smart (back to before ST) when things are not working properly, but when someone it trying to use it how it should, and it is not working, that is frustrating. The entire automation aspect of it, has been very unreliable. Maybe I got in at the wrong time, but it sure does feel like there are issues after issues. Maybe I have the wrong brands/devices, but every single brand I own has had it’s issues.
1 Like
So, WTH is going on here.
After not getting a response from SmartThings Support after more than 24 hours, I decided that my issues are similar to what others have experienced which in the end necessitated replacement of the hub.
I ordered a new hub, and when I got home, I checked the status of the current one, and it was still showing the Z-Wave State as “Not functional”.
About an hour later, the courier dropped the new hub off and I immediately started with its setup. While the Mobile ST App was doing the initial configuration, I checked the status of my current hub again, and now it was all of a sudden showing the Z-Wave State as “Functional”. At first, I thought I made a mistake and was looking at the new hub, but not so.
I still have many devices showing that they are offline and response to commands from the ST App, is sluggish (or non-response in a few instances.)
Question is - what next. Do I go through the effort of migrating to the new hub…
Add me to the list of users with unavailable devices. One zwave+ motion switch, one zwave dimmer switch, and one zwave light bulb.
I would literally break down in tears if my stuff just stopped working. I know its bound to happen but I am so not ready! I hope you all get it worked out.
1 Like
And now, everything is “unavailable.”
I find that compound devices (is that the correct word? e.g. Fibaro’s Double switches/relays and devices using child handlers) are more prone to losing connection with the hub, than the other devices. Whenever there are connection issues, you can be sure that the Fibaro Double Switches; Aeon Energy meters and - multi-sensors are the first to go (not to say Fibaro and Aeon are the culprits - it is just that I try to limit my devices to those from Fibaro and Aeon).
I have noticed a symptom which I have previously missed - I have a few devices on which the sync fails to complete after a configuration change, reporting “Sync Incomplete”. No matter what, I can’t get these devices to complete a sync successfully. Don’t know if that is related to my connectivity problems or due to some other issues (like troublesome device handlers). I also don’t know how many devices have this issue, as most device handlers don’t give a clear indication in the app that the sync failed. Is anyone else experiencing this as well?
If i were an ST engineer i’d look into Z-Wave Multichannel devices with endpoints that advertise the same or similar command classes.
This would fit the Fibaro Double switch issues and some other issues i’ve noticed on my end.
For example: i’ve tried a Z-Wave switch that has extra, configurable inputs, but as soon as i set it up to advertise 2 of the same endpoint, ST doesn’t recognize the device anymore. On the RF level i see the device correctly answer all commands, but where my handler code should be running the configure() function nothing appears either on RF or my log prints with the ST app still showing detecting devices.
1 Like
I set this weekend aside to migrate to a new hub, as I was convinced that my problems with ST are due to a faulty hub. I finished pairing all devices by this morning and started migrating my webCoRE piston and rebuilding my ActionTiles panels.
I have been busy with that for the past few hours and had about 16 pistons up and running with about half of my ActionTiles Panels rebuilt.
A few minutes ago, I realised that my lights were not turned off by the Piston which should have done so. Next, I noticed that the water geyser that was supposed to be turned off a bit earlier had not turn off either. It is then that the horror struck me - all Z-wave devices have stopped responding. None of them is responding. So, I’m back to square one. Two hours ago, the hot water switch (Aeon Heavy Duty Switch) was responding instantaneously to inputs, almost as if it was hard-wired.
I’m for the first time considering giving up…
Your zwave devices… How many are plugged in or hard wired?
Battery operated devices do not act as repeaters. It’s possible you have a weak mesh.
Also, when you rebuild, about every ten devices you add run a zwave repair from the ide, not from the mobile app.
Running the repair definitely helps.
This is very good advice! As your mesh grows, it is worth doing this…