Learning to Code

🛎️ Get Help Devices
2

To persist a variable, you need to use “state” to store these variables/values.

Try state.MotionUsed and state.ContactUsed as your “variables”.

3

is there anywhere in particular i need to add this in the driver?

4

Just prefix your current MotionUsed and ContactUsed variables with “state.” in every place you reference those two variables.

5

So I don't need to define them anywhere then. as in this is my variable A? I can just go straight ahead and do this:

if (IP1Type == "Contact" || IP2Type == "Contact") { state.ContactUsed = true
	if (txtEnable)	log.info "At least 1 Contact selected"
	} else { state.ContactUsed = false
	if (txtEnable)	log.info "Contact's not selected"	
			
		   }

	if (IP1Type == "Motion" || IP2Type == "Motion") { state.MotionUsed = true
	if (txtEnable)	log.info "At least 1 Motion selected"
	} else { state.MotionUsed = false
	if (txtEnable)	log.info "Motion not selected"	
			
		   }

then use them like this

if (state.MotionUsed) childDevice.sendEvent(name: "motion", value: motionstate, descriptionText: "IP${cmd.sourceEndPoint} has become ${motionstate}", type: "physical")
if (state.ContactUsed) childDevice.sendEvent(name: "contact", value: currentstate, descriptionText: "IP${cmd.sourceEndPoint} has ${currentstate}ed", type: "physical")
6

Yes, I believe that should work.

1 Like
7

Take a look at this documentation regarding state and atomicState. I believe atomicState May only work in Apps, not Drivers...but I could be wrong about that...:thinking:

https://docs.smartthings.com/en/latest/smartapp-developers-guide/state.html?highlight=state

2 Likes
8

brilliant thanks :sunglasses::+1: worked a treat!

this now appears in the driver

image

1 Like
9

@ogiewon is there a way to clear these variables? I have some devices that i have swapped drivers for and they seem to cling.

10

state.remove("version")
state.remove("Version")
state.remove("sensorTemp")

During development of a driver, I'll make typos like above, or just change my mind, and will add those lines to update(), run it, then remove the lines.

1 Like
11

so no blanket clean, you have to wipe each one separately. I was thinking of having a basic clean driver with a wipe in then could convert back.

12

you should be able to use any of the Groovy Map functions plus any of the underlying Java functions on it as state is just a Map

https://docs.oracle.com/javase/8/docs/api/java/util/Map.html#clear--

13

void clear() ? how do i use is?

14

I'm not 100% sure, but would simply try "state.clear()" and see what happens.

15

Yes, that is correct: state.clear()

1 Like
16

So where do I sign up for the courses? :wink: This is something I would like to get into at some point. Thanks for starting this thread.

1 Like
17

like this?

def configure() {
	WipeState()
}

def WipeState() {
	log.warn "wiping states"
	state.clear()
}
18

Blanket clean is uninstall the driver (not your code but the driver using your code), then install and configure any needed options again. This will get rid of all associated variables and you can start fresh. You should do this before releasing code as well to make sure that it installs from scratch for a new user as you expect it to.

19

now state.clear() works, I built a little blanket clean driver :slight_smile: clears the states and any schedules. Have to start somewhere :laughing:

https://raw.githubusercontent.com/borristhecat/HUBITAT/master/Clean%20Device.groovy

4 Likes
20

whats the difference between

state.remove("temperature")
state.clear("temperature")