App inputs don't always persist when navigating backwards

nayelyz · February 25, 2021, 1:39am

In the Groovy SmartApp, you can fix the number of “main” switches you can use, so you don’t have to generate dynamically the inputs in the next pages.
Using the SmartApp SDK, I created a single-page SmartApp with the following workflow:

Select the list of main switches.
Click in done and create the new sections to configure the list of switches controlled and their behavior.
Allow the installation only when all required values are filled

gist.github.com

https://gist.github.com/nayelyzarazua-bluetrail/1e2862ab15d00463b2c402f543a04126

smartapp.js

'use strict';

const express = require('express');
const bodyParser = require('body-parser');
const SmartApp = require('@smartthings/smartapp');
require('dotenv').config();

const server = module.exports = express();
server.use(bodyParser.json());

This file has been truncated. show original

Here, if the user wants to update the list of “main” switches, the values remain, not like in the Groovy IDE SmartApp.

Topic		Replies	Views
New API PAGE Params? Writing SmartApps	14	961	March 16, 2021
How to pass parameters in href? Writing SmartApps	57	20801	June 7, 2016
Backup Settings and Restore in SmartApps SmartApps & Automations	22	4785	January 14, 2017
Stuck Variables / Inputs General Discussion developers	16	1469	September 13, 2016
Change of enum options between install and update of SmartApp, old values are not removed from setting Writing SmartApps	11	1537	December 22, 2015

App inputs don't always persist when navigating backwards

Related topics