GCAL3 - General Discussion

[Stuart]

Thanks

FYI, library "dkjson" (provided by default) is not able to decode this value.

Have to do before :

Code: [Select]

value = value:gsub("'",'"')


Yes -- that's exactly the reverse of how I was creating the json string before saving.  I took a look and I suspect that there was some debug / logging formatting that was being screwed up and I 'fixed' the problem with single quotes (not even thinking single quotes were invalid json).

Also - there is / was no default library in vera at the time / across all versions so I install one that is apparently insensitive to the quotes. "json"

You can try this version - it's just got the offending reformat commented out (2 places) and seemed to work fine in some limited tests I have done.

[vosmont]

Also - there is / was no default library in vera at the time / across all versions so I install one that is apparently insensitive to the quotes. "json"

Since UI7, there's the library "dkjson.lua" in "/usr/lib/lua".

GetVera has not communicated on that (I don't know why)

[CudaNet]

Exactly what Stuart said, I too was utilizing libraries that were insensitive towards single quotations. I typically use either just json or akb-json but then again I'm still on UI5. Good to know nonetheless.

Also - there is / was no default library in vera at the time / across all versions so I install one that is apparently insensitive to the quotes. "json"

Since UI7, there's the library "dkjson.lua" in "/usr/lib/lua".

GetVera has not communicated on that (I don't know why)

[Stuart]

I have an idea for a companion plugin that can be used in the way you describe.   Basically a plugin that trips on every event start and finish and allows your scene(s) to respond depending on how you define them.   I've roughed out the design - it will take a couple of days, so some-time next week I'll post the beta version.

I'm planing on leveraging the gc_jasonEvents field already supported in the plugin, reading that data from one or more calendar plugins (you configure), merging and sorting all events by time order and then triggering the plugin on each event transition.   You can then set up a scene (or scenes) to be triggered by this new plugin, get the event name and whether it was the start or finish (using a couple of lines of LUA) and use that information in any way you want.

Does that sound interesting / usable ?

Having thought about this a little - and noting that some people are going to be pushed for RAM.  I'm now thinking a enhancement to the existing plugin - along these lines:
The rules for the plugin instance would still apply in that only  'eligible events' would be considered.  Whenever an eligible event starts or ends a variable
gc_notify (normally 0) would be set to 1 for one minute and an Luup event raised so you can trigger a scene.

During that one minute 3 new variables would be populated (otherwise they would be blank)
gc_notifyName, gc_notifyValue and gc_notifyType (either "Start" or "End").
You could gather these three variables into your scene and do whatever.

Thoughts / Comments ?




 

[clabos]

Hi
Personally I think your original design sounded better.
- How does the new design copes with events that happen in the same minute?
- Regarding memory - I suppose one will need another plugin (PLEG?) that checks for changes of the gc_notify variable? Unless such a plugin is already installed that will require some overhead too.
/Claes

[Stuart]

Hi
Personally I think your original design sounded better.
- How does the new design copes with events that happen in the same minute?
- Regarding memory - I suppose one will need another plugin (PLEG?) that checks for changes of the gc_notify variable? Unless such a plugin is already installed that will require some overhead too.
/Claes

I have the changes working as a modification to the existing plugin and events in the same minute (start or end) do not seem to be an issue.  This has been working well for a couple of weeks .....

However - I have uncovered some problems within Mios (notifications not working) and am working with their developers to track down the issue (causes Luup to crash when trying to send email.......  I have an idea where the issue lies but it may be a few days yet before we understand the 'why'.

[JackTheMan18]

Hello.
I'm a new user, so please forgive my ignorance.
Does this plugin work with UI7?

Also, let me explain what I'm trying to do.
Based on an entry in my google calendar, I'd like to trigger a scene (just simply turning on lights, etc.)

Is this the app to do that?

Thanks for the help.

Also, can someone point to the documentation for this app?

[Stuart]

YES and YES !! .....   along with a few other things !

The documentation is on page 1 of this thread and is pretty much up to date as of release 1.1.  There are a couple of new capabilities in release 1.2 (in the release notes).

Just follow the instructions closely - especially getting your google credentials and you should be fine.  Enjoy.

[Stuart]

This 1.3b version has an additional trigger that can be used for a variety of purposes.  It triggers on event start and end including overlapping events.  The events must still be 'eligible':
e.g. 1 If you set a keyword - then only events (including overlapping events) with that keyword are 'eligible'.
e.g. 2 To notify on all events - do not set a keyword and all events are 'eligible'.
The trigger is called "Event Start or End" and there are four new variables that can be accessed by Luup Code.  These are:
gc_notify --> either "0" or "1"
gc_notifyName --> the event name
gc_notifyValue --> any event parameter (i.e. the bit in {}) if used
gc_notifyType --> either "Start" or "End"

gc_notify is set to "1" at the Start and End of an event and is reset to "0" 15 sec later.  The other variables are reset to ""

If events have the same start or end time - the notifications are spaced approximately 5 seconds apart.

The beta version can be installed with:

http://<your vera IP>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=7016&Version=27332

[Stuart]

I found a rare condition when the new notifications would repeat.  I have fixed this and re-released V1.3.

You can get to it through the marketplace (likely tomorrow) or directly with this url

<your vera IP>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=7016&Version=3597

[clabos]

Hi
Thank you for v1.3 and the start/end notifications - it works great!!! I did also get some of those repeated messages, glad you fixed that. I have tested it about two weeks in total and it has been very helpful.

I do however have two very strange issue. I am not sure if it is related to GCal3, it seems far fetched...
1) The main issue is that my door sensors stop working properly when I have GCal3 installed. Once I remove it they start to work again. When I open a door the event seems to get stuck in Vera until I close the door again. The open/close events are then triggered more or less at the same time (first "close", then "open"). When I remove GCal3 and manually change the "tripped" and "armed tripped" statuses = 0 when the door is closed it starts to work normally again.
2) The other odd thing is that my BinarySwitch-devices now have got "tripped" variables under "urn:micasaverde-com:serviceId:SecuritySensor1", I don't think they are there by default. That is not a big problem though, it makes some scripts do a few more iterations, but I have a feeling this is connected with the other issue.

Do any of the two issues above have any potential relation with GCal3? I have a love/hate relationship with Vera as she seems to have a mind of her own so I would not be surprised if this is just another of her mood swings.

Again, thanks for the great update.

Edit: After 24 since my last uninstall of GCal3 the issues I talked about above came back! It seems as Gcal3 has nothing to do with this. I am sorry I jumped to that conclusion but it seemed logical earlier.

[Stuart]

BinarySwitch-devices now have got "tripped" variables under "urn:micasaverde-com:serviceId:SecuritySensor1"

Edit: After 24 since my last uninstall of GCal3 the issues I talked about above came back! It seems as Gcal3 has nothing to do with this. I am sorry I jumped to that conclusion but it seemed logical earlier.

GCal3 does use the "urn:micasaverde-com:serviceId:SecuritySensor1" schema but it is normal for devices to reuse other related schemas.  Luup is supposed to take care of keeping everything nicely separated.  I'd guess that the first level of separation is through the device_type (e.g. for GCal3 it is urn:schemas-srs-com:device:GCal:3) and device number and etc.

It's a long shot but have you manually installed any of these devices and perhaps used the same/wrong device_type setting ?

[clabos]

Thanks for the tips. No, I have not installed them manually. I think this behaviour started with the firmware update about 4 weeks ago. I have learned that the updates sometimes fix and sometimes break things. The sensors I am having most problems with are inexpensive Vision ZD2102 in case anyone makes a search on the name, but also my less inexpensive Fibaro sensors seem to be affected. I will contact the support and ask them.

[Stuart]

Thanks for the tips. No, I have not installed them manually. I think this behaviour started with the firmware update about 4 weeks ago. I have learned that the updates sometimes fix and sometimes break things. The sensors I am having most problems with are inexpensive Vision ZD2102 in case anyone makes a search on the name, but also my less inexpensive Fibaro sensors seem to be affected. I will contact the support and ask them.

Have you got this working ?

[ajbaab]

I'm fairly new to Vera and I had (for a while) set up a wakeup mechanism based on gcal with one of the previous gCal apps(no longer works due to Google updates)  I believe I did everything to the T through the files. When I click the calendar it shows my gCalendar. However when I click check it simply states, "Next event", "In bypass mode", "."
I even tried from my iCal using the ical link. Same thing simply states, "Next event", "In bypass mode", "." .  I have not figured out where the logs show when I put it in debug mode.

From that is it possible to discern what I'm doing wrong?

Thank you!