Agreed, but in this case, it is just such a simple workaround, and the powers that be don’t seem to be adding any new capabilities, so this is a “good enough” way to make it work for now.
That’s why I went ahead and posted the changes needed. I don’t want to update my device type to the public with this workaround. I am ok with other people updating their own device types, because then if something goes wrong, they have a better idea of how to fix it on their own. When the powers that be do add new capabilities, I will update it with the appropriate capability.
2 Likes
This is perfect @baldeagle072, thanks! I understand not wanting to add it to the public device type, I have no problem just modifying mine (as I already did) so thanks for giving me the steps to easily do that.
I don’t have a way to test it yet as I think I have to wait for the latest update in the app store, right @obycode? I don’t know if there is another way to test.
Thanks,
Scott
Right. Unfortunately, getting this one approved has been a little painful, including one rejection because the Apple Watch icon’s background was too close to black 
No problem, I can wait. I just wanted to make sure there wasn’t any testing I could do in the mean time. I just purchased your app so this weekend I will come up with other uses for it 
Thanks,
Scott
1 Like
I know Smart Alarm has an option to use a speech synthesis device:
1 Like
Thanks I wil look into it
Will this cause problems if I use the app on two different devices (e.g. an iPhone and an iPad)?
I.e. after using one device to make changes, will the other device have old data which is out of sync with whats in the cloud, or do you ensure the data stays in sync behind the scenes somehow (e.g. iCloud or validating a “last updated” value against the SmartThings cloud, etc.)?
Good question. If you use SmartRules on more than one device with the same SmartThings account, then currently you will need to manually keep them in sync using the refresh button on the settings page. This is definitely something that we would like to improve on in the future.
Thanks for that. I had installed the lite version on my iPhone and went to buy the full version only to realize my iOS version was prior to 8.2. I didn’t want to upgrade because I am jailbroken so I just installed it on my iPad.
When there is a jailbreak for 8.3 I will be upgrading and installing the full version on it and will have to remember to keep them in sync, although once my iPhone is upgraded I probably won’t use the iPad for SmartRules much.
Good to know though
@baldeagle072 and @obycode, I was able to test with Smart Alarm and both my Pushbullet devices showed in the the list for SA’s speech synthesis. I set my iPhone and set a test phrase for disarm and it worked, so this means it “should” work with the next release of SmartRules. I will try it again when the new version is out and post back.
Thanks for everything!
3 Likes
A couple things I though about that might be nice to have in the future:
- More icon choices and maybe different color options. For me I use the app mainly with the Watch, so anything to help me identify the icons would be good
- Ability to re-order the icons in the iPhone Notifications screen and Watch. Not sure how this could be done - does it sort by some method now?
- Some type of confirmation that the button has been pressed would be nice. On the apple watch I am pretty much having to guess that I am hitting the buttons. Maybe a more dramatic color change or something. Haptic feedback would be great, but do you have access to it in the API yet?
Thanks for the feedback!
I will look into adding some more. I like the idea of selecting colors for the icons as well. I will add these to the todo list.
Reordering of the rules is definitely important and will definitely be coming. The way it will work is just by ordering the rules in the SmartRules app, then the watch will use that same ordering. Currently, they are sorted alphabetically by name in the app, but currently not sorted at all in the QuickTaps.
Currently, it just uses the default button interface, where the color dims a bit. We could definitely do some kind of color change in a future update. The Taptic feedback is curently not exposed to developers, unless we send a push notification, which could be annoying.
Hello I’ve had some minor issues and i was reviewing the logs where I am seeing this constantly. Just thought I would pass this along to you. I am using on iPhone 6+ (iOS 8.4 beta 3)
debug App: modifyRule: Could not save Optional(Error Domain=NSCocoaErrorDomain Code=1560 "The operation couldn’t be completed. (Cocoa error 1560.)" UserInfo=0x170870dc0 {NSDetailedErrors=(
"Error Domain=NSCocoaErrorDomain Code=1570 \"The operation couldn\U2019t be completed. (Cocoa error 1570.)\" UserInfo=0x17067dcc0 {NSValidationErrorKey=command, NSLocalizedDescription=The operation couldn\U2019t be completed. (Cocoa error 1570.), NSValidationErrorObject=[arguments: (\n {\n displayAsCondition = \"after min\";\n displayAsTrigger = \"after min\";\n value = \"\";\n },\n {\n displayAsCondition = 50;\n displayAsTrigger = 50;\n value = 50;\n }\n), thing: {\n}, command: {\n}]}",
"Error Domain=NSCocoaErrorDomain Code=1570 \"The operation couldn\U2019t be completed. (Cocoa error 1570.)\" UserInfo=0x17086b940 {NSValidationErrorKey=thing, NSLocalizedDescription=The operation couldn\U2019t be completed. (Cocoa error 1570.), NSValidationErrorObject=[arguments: (\n {\n displayAsCondition = \"after min\";\n displayAsTrigger = \"after min\";\n value = \"\";\n },\n {\n displayAsCondition = 50;\n displayAsTrigger = 50;\n value = 50;\n }\n), thing: {\n}, command: {\n}]}"
)}), Optional([NSDetailedErrors: (
"Error Domain=NSCocoaErrorDomain Code=1570 \"The operation couldn\U2019t be completed. (Cocoa error 1570.)\" UserInfo=0x17067dcc0 {NSValidationErrorKey=command, NSLocalizedDescription=The operation couldn\U2019t be completed. (Cocoa error 1570.), NSValidationErrorObject=[arguments: (\n {\n displayAsCondition = \"after min\";\n displayAsTrigger = \"after min\";\n value = \"\";\n },\n {\n displayAsCondition = 50;\n displayAsTrigger = 50;\n value = 50;\n }\n), thing: {\n}, command: {\n}]}",
"Error Domain=NSCocoaErrorDomain Code=1570 \"The operation couldn\U2019t be completed. (Cocoa error 1570.)\" UserInfo=0x17086b940 {NSValidationErr...[TRUNCATED]@obycode so the app has been rendered pretty much useless for me over the last few weeks. I have 10-15 rules setup, but only 3-4 show within the app. When I try to log out, login, uninstall, reinstall, authorize or reauthorize ST with the app, nothing works. Ive consistently had crashing issues when trying to refresh or logging into the app. Im at a complete loss at this point.
On a positive note, it looks like the rules I’ve created are functioning as expected, but I am unable to view and/or edit them. Still love the app though
Any ideas?
@the2352, @tonesto7, it looks like you are both seeing the same issue. I apologize for the inconvenience this is causing. This is the key issue that we are working on for version 1.3. Basically, after some combination of rule editing, you end up with some corrupted data, and that corrupted data prevents future saving of the data, resulting in all of the other issues you are seeing. This situation will not occur if you only create and delete rules, no editing.
The way to fix it for now is to:
1 - Logout of SmartRules
2 - Delete SmartRules from your device (don’t delete the SmartApp from SmartThings though)
3 - Reinstall SmartRules
4 - Login
The data which is saved in the SmartApp is not corrupted, just the data on the phone, so all of your rules will be saved, as long as you do not delete the SmartApp. Version 1.2.1 should be released soon, and it helps with these issues, but does not fully solve it. The next release after that, 1.3 will definitely eliminate these issues.
1 Like
+1 vote for making it more obvious when the QuickTaps are pressed from the Notification Center on the iPhone. I almost always can’t tell if the press had been registered or not.
For once, I prefer the way the SmartThings app does it; the button has the spinning pinwheel progress bar on it once the button is pressed, and it stays that way until the command is confirmed by the SmartThings hub.
Also, the icon colors and text of the QuickTap icons in the Notification Center are consistent with the SmartRules app icon, but being subdued colors makes them hard to see/read unless the phone is in torch mode. Maybe make the text (and maybe the icons) white?
1 Like
@obycode Unfortunately I tried the ‘fix’ multiple times without success. Ill be waiting patiently for 1.2.1 and 1.3 to roll out - here’s hoping to sooner than later!
That’s strange. Those steps should resolve all of the issues that we are aware of. Shoot me an email @ support at obycode.com and we’ll take a closer look at what’s going on in your case.
Version 1.2.1 is waiting for Apple and version 1.3 is in progress. I expect for 1.2.1 to be available any day now and we’ll submit 1.3 within a week.
Yeah i’ve noticed that a bunch of my rules aren’t working anymore. Out of my 6 trigger rules only 2 are working at the momment… When I check the logs I see nothing out of the ordinary.