EchoSpeaks -- Can't get temperature trigger to work

I'm trying to set up an EchoSpeaks action to say something like "Spa temperature is now 90 degrees", when the temperature exceeds that threshold.

I'm using a community supplied driver, Pool Controller with a child device "Pool Controller body". I have two devices of type "Pool Controller Body" -- "Pool Temperature" or "Spa Temperature" depending on which body currently has pump active,

I see the correct value of the state variable "temperature" on the Pool Temperature device page. But, I can't get an EchoSpeaks action to trigger;

The custom action is this:

%name% %type% is now %value% %unit%

But, when I try testing using the slider in the EchoSpeaks app, the %value% seems random. I looked at the EchoSpeaks code and it looks like that's what is intended when the action is executed in test mode.

Should the action trigger repeatedly when the temperature conditon is met? Or just once, when it first exceeds it?

I haven't been able to get the action to trigger using less than, equal to , or greater than the threshold.

Looking for an easy answer (like what I'm doing wrong?) before I do a test driver that just has "TemperatureMeasurement" capability and a state variable "temperature" to isolate the problem.

Tried upgrading EchoSpeaks to 4.1.8.0. Now, when I test using the slider in EchoSpeaks, nothing is spoken and I see this in the log:

app:1292021-06-09 12:10:21.526 pm debugAction (v4.1.8.0) | deviceEvtHandler | execOk: false | evtOk :false | devEvtWaitOk: true | evtAd: false | aftRepEvt: false

app:1292021-06-09 12:10:21.524 pm debugAction (v4.1.8.0) | evtWaitRestrictionOk: Last Temperature Event for Device Occurred: (132 sec ago) | Desired Wait: (10 sec) - (true && true) Status: (✓) | OnceDaily: (false)

app:1292021-06-09 12:10:21.518 pm debugAction (v4.1.8.0) | deviceEvtProcNumValue | result: [evtOk:false, evtAd:false] | evtName: temperature | evtVal: 54 | cmd: above | low: null | high: 85.0 | equal: 86.0 | all: false | avg: false

Current temperature is 86 and trigger was set to be over 85.

Using the test slider in other EchoSpeaks (4.1.8.0) actions no longer results in the Echo speaking the message. But, they still works when the action trigger occurs (e.g. when turning on/off switches that are action triggers for EchoSpeaks actions.

@davethomaspilot

You might consider posting your question/issue in the main Echo Speaks thread, linked below. Otherwise, it may not be seen by the folks best equipped to answer it.

1 Like

Ok, thanks. I'll repost it there.

1 Like

Download the Hubitat app