Just noticed that in the ST app if you select to control a shade, that along with Open and Close there is now a preset position option as well. However, whenever I try to use that in an automation I get a network error and the automation will not save. I can leave everything the same and select open and closed and it will save. As soon as I change it to Preset it will not. Should this work, or is there something I need to do to get it working?
Up to 5 Pre-set positions are allowed as part of programming the shades, and are simple to setup, change, or remove. An up or down command will move the shade to the next pre-set position. Holding up or down button for 2 seconds bypasses all pre-set positions and the shade will fully open or close. The pre-set function for ST is not active and cannot be saved.
I’m guessing Leviosa is using capability Window Shade for their device, but haven’t mapped the SmartThings preset capability to the presets in their cloud
Jimmy is right that Leviosa is using capability Window Shade. Pre-sets are user programmed independent of ST and are not able to be mapped. We hope ST expands Window Shade capability to enable “raise” and “lower” commands in addition to today’s “full open” and “full close” commands - then the Leviosa pre-sets will work perfectly and simply with ST, as they do already with other home automation systems (e.g. Alexa).
Greetings. I recently installed Leviosa Blinds and was eager to automate them with SmartThings.
I’ve added the groups and can trigger them “manually” with the SmartThings app. However, I cannot setup a custom automation.
I go through all the steps, setting the time etc, when I get to the step of what device I want to trigger, the shades are not in the list… not under the room listing or the A to Z listing.
Can anyone assist with this? I wrote Samsung and their reply was “Leviosa shades are not supported” which is a nonsensical answer.
I called technical support and they suggested adding the Samsung hub “might” help. The certainly sounded unsure. Frustrated.
You say you can manually open and close them with the new app. So you have the ST app linked to your Leviosa zone?
If so you should be able to create a custom automation to open or close at a specific time. I just looked in the new app on mine and when I select devices I can then select any of my shades.
I don’t use the new app for automations per se myself, I have all my automation setup using webcore and virtual switches. When I first got my shades the new app caused me a great deal of problems. So I avoided using it as much as I could. I setup the virtual switches and have automations in the new app that open and close the shades if the virtual switch opens or closes. I then control the virtual switch with webcore and the classic app.
With the new device profile (required by ST), some users have had to unlink and relink their accounts so automations can work. We PM’d you directions - here they are for the group, starting at ST homescreen:
• Add device (the + sign, upper right)
• Select “Leviosa Shades”
• Select ‘Other” (will soon be ‘window treatment’ we are told, as it should be)
• Skip locations, select Next
• Select ‘Done’ on Account linking page, since you are already linked.
• Select DENY on next page, and EXIT
• You are back at account linking page. Select 3 dots on upper right. Select DELETE, and confirm Delete to remove the App.
• Select Other
• Choose locations, select Next
• Select Link Account, and enter Leviosa App email and pw
• Go back to main menu – the icons for your groups appear.
• Now add Automation. (‘+ custom automation’ at the bottom on screen)
Complete setup of automation – your devices will appear.
Update: With the new device profile, commands have been change to simple ‘raise’ and ‘lower’ so pre-set positions are now enabled. For automations, a user can simply set double commands (say, a minute apart) to pass multiple pre-set positions.
For users who do not utilize pre-set positions, the shades will simply travel all the way up or down with a single command.
I followed these instructions with no success.
I will note that the instructions say to “skip locations” but this option does not appear in the app. So I went on to the next step. It seems like the instructions don’t quite match the app.
I have the same issue as Scott. I.e the shades are not showing up in scenes/automations. Without that the ST integration is quite useless.
Also, I’m using the classic app. Is there a workaround to make it work in the classic app? (although it doesn’t even work in the new app automations)
As we noted in PM, ST acknowledges the issue with iOS where the devices are not populating correctly. We will advise you when the issue is resolved.
This is only an issue for iOS - the Android version works properly.
ST acknowledges the issue with iOS where the devices are not populating correctly. We will advise you when the issue is resolved.
This is only an issue for iOS - the Android version works properly.
Leviosa is not listed in the Classic App per guidance from ST. Leviosa is listed in the New App which ST states is the future platform for ST.
I am currently using an android device with the new smartthings app and I am having the same problem as the people above. I’ve tried following the directions to unlink and relink the accounts, but there is no change. The shades also say Checking Status… forever and never update. They are unavailable on the automations screen.
Thanks for letting us know, and we will look into this. We have a new Leviosa App update planned this weekend for both Android and Apple that should address this issue.
In the ide that shades are coming up as Type placeholder - I’m assuming this is not correct. Do you know what type they should be? This may be the problem.
This is expected behavior for new cloud integrations.
Tony - can you post here when the app is updated so we know when to try again?
You can add me to the list. I just added a 5th shade today. I use virtual switches to control the shades so that I can use the classics app to control them. The first 4 still work, but the one I just added does not, it does not show up in automatons so that I can use it with a virtual switch.
It has a nice Shade icon that will open and close, but only if you open and close it with the new app. It will control the shade. If you use the remote or the Alexa skill to open or close the shade it’s state is not being reported back to the new app. I don’t get the metadata error, that I noted in an earlier post when opening the Guest room shade. I still get it when I open the shades I added earlier. I thought about removing and reinstalling everything but I am glad I came back and reread this. I think if I do I will then have none of them working with ST.
See screenshot below. The dining room device is a Leviosa shade. That shade works the Guest room does not.
We released the new Leviosa FW and new Apps today (iOS and Android) on schedule, but these will not impact ST functionality.
Samsung’s code freeze was removed recently after its Developer Conference (SDC wrapped up 10-30-19) and they have now deployed a change to production which improves users’ experiences. Leviosa will be updating its device profile to meet these changes in the next few weeks. They have also introduced a new schema for cloud-to-cloud integrations such as ours. This should facilitate onboarding with faster execution commands (almost 400 ms faster!).
We applaud Samsung’s commitment to improving the user experience, and we will be updating Leviosa Zone device functions to meet new ST requirements shortly (estimate is 12-1-19).
Please see the update we just issued in this space. And we will continue to provide updates as we meet new ST requirements.