| Posted: Friday Mar 3rd, 2017 09:54 pm |
|
1st Post |
Pgordon
Member
back to top
|
As per Matt's request to move issues out to separate dedicated threads, I'm starting one to follow the discussion of the issues I was reporting in the long (now closed) thread; namely that I cannot discover any more devices (I have 123), nor can I delete any of the devices previously discovered...
Matt, I've downloaded the 1.0.1b beta you linked to... - presumably I have to re-image the SD card with this rather than be able to update automatically via the web interface...
Just want to check what impact that will have on the existing set of devices... - is any user data stored on the SD card - other than the alarm.config and the comfigurator CCLX file of course?
Cheers
Paul G.
|
| Posted: Friday Mar 3rd, 2017 09:59 pm |
|
2nd Post |
mattbrain
UCM Pi Users
| Joined: | Tuesday Jun 12th, 2007 |
| Location: | United Kingdom |
| Posts: | 185 |
| Status: |
Offline
|
back to top
|
Hi Paul
The 1.0.1b beta zip only contains updated ST App and Devices, please overwrite those devices on the ST web portal - do not use this image on the SD card as it will break stuff....
Thanks,
Matt
|
| Posted: Tuesday Mar 7th, 2017 08:27 pm |
|
3rd Post |
Pgordon
Member
back to top
|
OK, I'd been otherwise occupied for a few days, so I just this afternoon got round to updating the smartapp & the devicehandlers included in the "b" beta... All went fine on the samsung IDE page.
Then I restarted the ST app on the phone, & went to the discovery page for the Comfort Manager app. I saw the previous 123 discovered devices, but scrolling down below the list I saw an additional "Flush Devices" bar, with "Tap to Show" beneath and a right-arrow indicating another screen to open... - I took this to imply that I could open the next screen and individually select devices to flush from the discovery cache... - but it appears this is not so... when I hit the bar, the next screen opened and informed me that *ALL* devices had been flushed, which I could see to be true when I returned to the discovery screen, where there were no devices shown.
If that is the intended behaviour - could you perhaps put an "are you sure" in there first? - better still, it is technically feasible to make it behave as I believed it would; i.e. to open a screen with all the previously discovered devices listed, with each individually delete-able?
Anyway, too late for that this time round... - all 123 devices were deleted, and thus far 70 devices have been discovered, which I think is somewhere about right, since I did delete a fair few non-essential devices from the alarm.config file, so the total should be quite a bit lower than the previous 123... however, 20+ minutes of discovery later, it's still stuck at 70, I can see there are definitely still some devices missing that should be there...
Unfortunately however, I cannot save them... every time I hit the "Done" button, I get the big red "An unexpected error occurred" bar across the top of the app... I've tried numerous times, and the error is persistent... even after killing & restarting the ST app a few times, and power-cycling the ST hub...
So at the moment, I'd have to declare 1 step forward, - but 2 steps backwards... 
Got any thoughts or suggestions?
Cheers
Paul G.
|
| Posted: Tuesday Mar 7th, 2017 10:09 pm |
|
4th Post |
mattbrain
UCM Pi Users
| Joined: | Tuesday Jun 12th, 2007 |
| Location: | United Kingdom |
| Posts: | 185 |
| Status: |
Offline
|
back to top
|
Hi Paul
The existing devices you have should still be there, this is a discovery flush rather than a device deletion..so nothing should have been deleted yet...
Can you repeat the exercise with the live logging page open on your PC, filtered on the 'Comfort Manager'. This should help identify what is going on with your specific install.
Thanks,
Matt
|
| Posted: Wednesday Mar 8th, 2017 06:54 pm |
|
5th Post |
Pgordon
Member
back to top
|
mattbrain wrote: Hi Paul
The existing devices you have should still be there, this is a discovery flush rather than a device deletion..so nothing should have been deleted yet...
Can you repeat the exercise with the live logging page open on your PC, filtered on the 'Comfort Manager'. This should help identify what is going on with your specific install.
Thanks,
Matt
Yes, thanks Matt, I noticed the actual "things" devices were still there afterwards... :-)
Here's the logging you requested for the activity of pressing the "Done" button on the discovery screen to save the discovered devices.
a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: error java.util.ConcurrentModificationException @ line 149a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug Updated with settings: [searchTarget:urn:http://www.cytech.com:service, selectedDevices:[/upnp/device/desc.xml?udn=ComfortAlarmZone10, /upnp/device/desc.xml?udn=ComfortAlarmZone5, /upnp/device/desc.xml?udn=ComfortAlarmAlarm0, /upnp/device/desc.xml?udn=ComfortAlarmZone3, /upnp/device/desc.xml?udn=ComfortAlarmZone9, /upnp/device/desc.xml?udn=ComfortAlarmZone6, /upnp/device/desc.xml?udn=ComfortAlarmZone1, /upnp/device/desc.xml?udn=ComfortAlarmZone7, /upnp/device/desc.xml?udn=ComfortAlarmZone2, /upnp/device/desc.xml?udn=ComfortAlarmZone4, /upnp/device/desc.xml?udn=ComfortAlarmFlag1, /upnp/device/desc.xml?udn=ComfortAlarmFlag93, /upnp/device/desc.xml?udn=ComfortAlarmFlag33, /upnp/device/desc.xml?udn=ComfortAlarmFlag121, /upnp/device/desc.xml?udn=ComfortAlarmFlag24, /upnp/device/desc.xml?udn=ComfortAlarmCounter43, /upnp/device/desc.xml?udn=ComfortAlarmFlag11, /upnp/device/desc.xml?udn=ComfortAlarmZone37, /upnp/device/desc.xml?udn=ComfortAlarmFlag25, /upnp/device/desc.xml?udn=ComfortAlarmFlag17, /upnp/device/desc.xml?udn=ComfortAlarmFlag143, /upnp/device/desc.xml?udn=ComfortAlarmCounter44, /upnp/device/desc.xml?udn=ComfortAlarmFlag15, /upnp/device/desc.xml?udn=ComfortAlarmFlag32, /upnp/device/desc.xml?udn=ComfortAlarmZone34, /upnp/device/desc.xml?udn=ComfortAlarmFlag155, /upnp/device/desc.xml?udn=ComfortAlarmFlag111, /upnp/device/desc.xml?udn=ComfortAlarmFlag141, /upnp/device/desc.xml?udn=ComfortAlarmFlag152, /upnp/device/desc.xml?udn=ComfortAlarmFlag12, /upnp/device/desc.xml?udn=ComfortAlarmCounter47, /upnp/device/desc.xml?udn=ComfortAlarmFlag146, /upnp/device/desc.xml?udn=ComfortAlarmFlag151, /upnp/device/desc.xml?udn=ComfortAlarmFlag94, /upnp/device/desc.xml?udn=ComfortAlarmFlag112, /upnp/device/desc.xml?udn=ComfortAlarmFlag51, /upnp/device/desc.xml?udn=ComfortAlarmFlag38, /upnp/device/desc.xml?udn=ComfortAlarmCounter46, /upnp/device/desc.xml?udn=ComfortAlarmFlag4, /upnp/device/desc.xml?udn=ComfortAlarmFlag23, /upnp/device/desc.xml?udn=ComfortAlarmFlag26, /upnp/device/desc.xml?udn=ComfortAlarmCounter41, /upnp/device/desc.xm...[TRUNCATED]a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:53: debug getChildDevices(false), children=79a8bfda18-d891-48f2-a68c-962bad379963 15:43:49: debug Starting VerifyDevicesa8bfda18-d891-48f2-a68c-962bad379963 15:43:49: debug Starting sspdDiscovera8bfda18-d891-48f2-a68c-962bad379963 15:43:49: debug Starting ssdpSubscribe
FYI, just a little while ago, I added a couple more CBUS lights into my house, so I've been through the entire process of creating the 2 new CBUS group addresses, mapping them to counters in Comfigurator, updating the UCM flash, stopping the UHAI service, adding the 2 extra counters (and an additional zone as it happens) into the alarm.config file, and uploading both the alarm.config and my updated CCLX file into UHAI, and restarting the service. I can see in the ST discovery that it has increased from 70 to 73, so it has discovered the additional 3 devices, and I can click on the list to get into the tick-box list screen to choose which to publish, where I can see the 3 new devices I just added, and I can tick their boxes... I can "Done" at that screen to revert back to the main discovery screen, but I cannot "Done" there to save the settings, so I cannot get the 3 new devices to appear as Things...
Hope that helps...
Cheers
Paul G.
|
| Posted: Thursday Mar 9th, 2017 08:11 pm |
|
6th Post |
Pgordon
Member
back to top
|
FYI, I just noticed an update to the SmartThings app in the App Store... which I just applied... but it hasn't made any difference to my problem...
:-(
Paul G.
|
| Posted: Wednesday Mar 15th, 2017 11:47 am |
|
7th Post |
Pgordon
Member
back to top
|
It seems to have gone very quiet on here recently... - Hopefully that's a sign of intense head-down 'in the zone' development... :-)
|
| Posted: Wednesday Mar 15th, 2017 03:23 pm |
|
8th Post |
mattbrain
UCM Pi Users
| Joined: | Tuesday Jun 12th, 2007 |
| Location: | United Kingdom |
| Posts: | 185 |
| Status: |
Offline
|
back to top
|
Hi All
Don't worry - Stuff is still being done, just have been focusing on some improvements.
I'm going to update the beta device manager released recently to include a list to remove old devices and fix the issues encountered. I hope to do this tomorrow subject to other activities,
Thanks,
Matt
|
| Posted: Wednesday Mar 15th, 2017 03:54 pm |
|
9th Post |
| Posted: Wednesday Mar 15th, 2017 03:55 pm |
|
10th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
I am glad someone else is feeling the heat!
|
| Posted: Wednesday Mar 15th, 2017 04:11 pm |
|
11th Post |
mattbrain
UCM Pi Users
| Joined: | Tuesday Jun 12th, 2007 |
| Location: | United Kingdom |
| Posts: | 185 |
| Status: |
Offline
|
back to top
|
I think Mr Chiu will be pleased to hear I'm working on schematics at the moment 
|
| Posted: Thursday Mar 15th, 2018 01:45 am |
|
12th Post |
burtonjk
Member
| Joined: | Tuesday Aug 21st, 2012 |
| Location: | |
| Posts: | 22 |
| Status: |
Offline
|
back to top
|
Good Evening
I have an issue adding some devices as follows:
I have enabled 3 more zones in ComfortUploaded the new .cclx to UHAIUploaded an amended UPNP config file to UHAIRestarted UHAIRun the discovery in the Comfort Manager Smart App (the 3 new zones were found)Selected the 3 new zones (only)Pressed DonePressed Save
I then get an error message saying "deviceNetworkId must be unique"
Am I following the correct process to add devices to an existing setup? If so any idea how to recover from the problem and get my devices added.
The log from smartthings is pasted below
Thanks
Jim
a5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:51 PM: error grails.validation.ValidationException: Validation Error(s) occurred during save():- Field error in object 'physicalgraph.device.Device' on field 'deviceNetworkId': rejected value [B827EB6DDEBD]; codes [physicalgraph.device.Device.deviceNetworkId.unique.error.physicalgraph.device.Device.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.error.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.error.java.lang.String,physicalgraph.device.Device.deviceNetworkId.unique.error,device.deviceNetworkId.unique.error.physicalgraph.device.Device.deviceNetworkId,device.deviceNetworkId.unique.error.deviceNetworkId,device.deviceNetworkId.unique.error.java.lang.String,device.deviceNetworkId.unique.error,physicalgraph.device.Device.deviceNetworkId.unique.physicalgraph.device.Device.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.deviceNetworkId,physicalgraph.device.Device.deviceNetworkId.unique.java.lang.String,physicalgraph.device.Device.deviceNetworkId.unique,device.deviceNetworkId.unique.physicalgraph.device.Device.deviceNetworkId,device.deviceNetworkId.unique.deviceNetworkId,device.deviceNetworkId.unique.java.lang.String,device.deviceNetworkId.unique,unique.physicalgraph.device.Device.deviceNetworkId,unique.deviceNetworkId,unique.java.lang.String,unique]; arguments [deviceNetworkId,class physicalgraph.device.Device,B827EB6DDEBD]; default message [{0} must be unique]@line 146 (doCall)a5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:51 PM: debug getChildDevices(false), children=0a5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:51 PM: debug Unable to find master devicea5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:51 PM: debug Looking for /upnp/device/desc.xml?udn=ComfortAlarmZone21a5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:51 PM: debug Installed with settings: [searchTarget:urn:http://www.cytech.com:service, selectedDevices:[/upnp/device/desc.xml?udn=ComfortAlarmZone21, /upnp/device/desc.xml?udn=ComfortAlarmZone22, /upnp/device/desc.xml?udn=ComfortAlarmZone20]]a5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:45 PM: debug Starting VerifyDevicesa5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:45 PM: debug looking for devices urn:http://www.cytech.com:servicea5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:45 PM: debug Starting sspdDiscovera5e3f59f-66bd-440a-be3e-2679db1339e9 9:09:45 PM: debug Starting ssdpSubscribe
|
| Posted: Friday Mar 16th, 2018 02:33 am |
|
13th Post |
burtonjk
Member
| Joined: | Tuesday Aug 21st, 2012 |
| Location: | |
| Posts: | 22 |
| Status: |
Offline
|
back to top
|
Problem solved. I had stupidly added another instance of the Comfort Manager Smart App.
Gone back and did the discovery with the original and all good
Regards
Jim
|
|
