Gcal Search device error setting variable from device attribute

variables
#21

My bad!!!

That version only added location attribute. Just updated github to version 20180325.1, which includes the eventTime attribute.

#22

I fixed it. Change your device handler for the attributes to string not number and it works

#23

Yeah, that will work too. I was worried that changing that in the DTH might break existing users’ integrations, so I just added the eventTime attribute instead.

#24

Just an FYI eventTime doesn’t work with all day events. Also, just a thought, rename it to eventOpenTime and add eventCloseTime

It doesn’t populate the eventTime attribute for all day events. It shows as — in the device tile
Also, is there a way to search multiple variations of strings? Ie. “no school” “spring recess” “paerent teacher” etc

#25

Hi. I’m curious as to whether anything further developed from this conversation. I believe I’m using the current GCal code versions. Event Time does seem to populate (albeit in UTC) for all-day, multi-day events but Close Time does not. I wouldn’t mind just parsing the Event Summary data but am getting some strange results when trying to break down the Event Summay text (there may be ‘non-printable’ characters in there??).

Thanks in advance for any thoughts / ideas on how to get a reliable end time.

#26

What version of the apps and DTH are you using?

#27

Hey there. Thanks for the prompt response. Your question has me thinking about whether or not I might be running out-of-date versions. I assumed I was on the latest versions since “Update from Repo > GCal Search (Master)” provides no update options. Is there some other mechanism that is used to update this code? Apologies if that’s a silly question…still trying to acclimate to the architecture.

Based on the code comments (last update) it looks like I’m running:
GCal Search (def text = 20170326.1)
GCal Search Trigger 20170327.2
GCal Presence Sensor 20170422.1
GCal Event Sensor 20180327.2 (code comments are out of order so not 100% I’m reading this correctly)

THANKS for your help!