other problem on PI, maybe because my old SD card or application, without any reason PI can not be accessed, restart service or restart PI not help ... i need to re-copy the image to solve the problem, it happen several times . anyone has same experience ?
I\'m having funnies too...
yesterday, i deleted a bunch of devices from the ST app, - under My Home>Things... then click on the \"thing\", then click the cog to open the thing\'s settings, then click delete and confirm the command... ST comes back & says the thing was successfully deleted from SmartThings...
All great...
Today they\'re back again!!! - and they all show status of \"Offline\" in red... - not surprising really, since the devices in question have been removed from the alarm.config file...How and why has ST re-added the devices I told it to delete? - that is immensely annoying!
Also, I\'m now going through the list and deleting them *again* in the same way as before... like before, ST app says the device is deleted, but when I back out to the list, it\'s still bloody well there... and seems to be staying there.... I deleted a bunch of \"things\" some 15 minutes ago, and they\'re all still in the things list in the ST app... - however, it looks like they do disappear eventually, so I guess that\'s just crappy UI management by the ST app...
One more oddity...there\'s a fair few things in my things list that also show status of \"Offline\" in red... - incorrectly... - these are devices that are still in the alarm.config file, and should be there and working...
How can I be sure just exactly what UHAI reads from the alarm.config file? - could there still be issues due to the different CRLF character between Windows & Mac/Linux? - I\'m downloading the file, editing in Windows Notepad, and re-uploading... this appears to be working OK, - there\'s no complaint about the upload, and the service starts OK... but I don\'t know if I have complete confidence in what is actually being activated by UHAI....
TIA
Paul G
Ok, I\'m a little bit stuck now...
I\'ve tried numerous times to delete the discovered devices in the ST app, and it just constantly fails with the error as per the attached screenshot.
So I have devices that I want to use in the app but am unable to discover, and I have discovered devices that I don\'t want present but am unable to delete... and I think that without deleting some or all devices, I won\'t ever discover any more?? So I appear to be stuck in a catch-22... as it stands, I cannot get my 2 main living room lights into SmartThings... (it would have to be those ones wouldn\'t it!)
Any suggestions as to how I can resolve this? - the \"An unexpected error has occurred\" bar appears almost immediately after I press the big red \"Delete\" button... *behind* that error message is the bit that says \"Select Devices (123 found)\" - this is the list discovered by the Comfort Manager smart app a number of weeks ago now, and steadfastly refuses to ever change, it has been \"stuck\" with the same 123 devices no matter what I do, how many times I change the alarm.config file, or how often I re-run discovery.
Many thanks.
Paul G
Hi All
Apologies for not responding more quickly, I hadn\'t seen there had been so much activity!
Paul,
I have seen this behaviour before, and I think there are 2 core problems:
1. ST isn\'t honouring the request to delete devices - I have experienced this personally and it is annoying. I have a couple of things I am going to try - but i suspect this may be a \'feature\' of the ST platform.
2. Discovery caching. It seems the discovery cache is permanent and on occasion seems to get stuck. I have seen the issue you are having on my test platform with far fewer devices so I\'m not convinced it is a memory issue. I\'m going to add a flush function to the code and i\'ll publish a copy for testing prior to the next release, if all goes to plan i\'ll have it out in the next day or so.
bagushandhoko,
I suspect this is due to file system corruption - to totally fail in the way you indicate leads me to believe you are probably right. SD cards do have a finite life so this might indicate it\'s time to get a new one. Can you confirm what size card it is, as another (outside) possibility is the disk is filling up but this should be managed by the automatic weekly purge of the log files.
Thanks,
Matt
[user=912]mattbrain[/user] wrote: Quote:bagushandhoko,
I suspect this is due to file system corruption - to totally fail in the way you indicate leads me to believe you are probably right. SD cards do have a finite life so this might indicate it\'s time to get a new one. Can you confirm what size card it is, as another (outside) possibility is the disk is filling up but this should be managed by the automatic weekly purge of the log files.
Thanks,
Matt
16 GB, how much recommended size ?
Great stuff. Thanks Matt. I\'ll eagerly await the update before trying the nuclear option :-)
Just as an aside, whilst observing the UHAI status page, I see the load figure is extremely low... typically hovering around 0.05 - 0.08... right now, with not much going on on ST, it\'s at 0.02... Presumably this implies that Pi 3 B is way overkill just for running the UHAI bridge... - I wonder how it would fare on a new Pi Zero W? - heck for a mere tenner, I may get one just to find out...
In the meantime, I still might like to make better use of the current Pi3B by runnning some additional tasks on it alongside the UHAI... Which brings me back to my earlier question: can we get logon access to the Pi so I can enable remote access, perhaps run a GUI, and explore the possibility of getting running a few additional thngs? - I\'m too impatient to wait for the official SONOS skill for Alexa, so in the meantime, I might try experimenting with a 3rd-party skill, such as this one:
https://github.com/rgraciano/echo-sonos#echo-sonos - I need to run an instance of node.js, and I figure the Pi is a good place for that... (unless it\'s already there for the UHAI??)
Cheers.
P.
I\'m running a Pi A or 1 or whatever the first was - it runs at 0.25 load
What is always worth a go is within ST \"Things\" go to the Comfort Bridge and push the refresh button. If your not sure where it is i\'ll send a screenshot.
[user=1738]DavidJ[/user] wrote: Quote:What is always worth a go is within ST \"Things\" go to the Comfort Bridge and push the refresh button. If your not sure where it is i\'ll send a screenshot.
Thanks. I found it OK, and did it, but it seems to have made no difference... :-(
On an unrelated topic, anyone know how the comfort \"Doorbell\" device is supposed to work?
I have a \"Doorbell\" device in my \"Things\"... it shows as status \"On\" - which seems an odd choice... but it doesn\'t do anything.. - I just went & rang my doorbell (Which is a Comfort DP02 doorstation) whilst monitoring the status in the ST app... - the status does not change in the \"right now\" view, and there are no events in the \"recently\" view, so it appears that my doorbell \'Thing\' is not activating in response to comfort doorbell presses...
Should that be automatic, or do I have to configure something? - I figure I could always put an output activation in my doorbell response, then use that other output as a \'Thing\' to get doorbell events into ST... - oh wait... - I can\'t currently discover any new devices can I?... :-(
I\'m trying to use the \"speaker Notify with Sound\" smart app, in conjunction with the SONOS Thing to get announcements when the doorbell is pressed...
TIA
Paul G.