EventWatcher and the GC100

Hi,

I need some help on an issue… I’m missing some logging in Event Watcher that is related to my GC100 plugin for the IP2CC device.
[ for details see my config/project: http://forum.micasaverde.com/index.php/topic,29605.0.html ]

Got Event Watcher logging to my Syslog Watcher v4.7.0 (running on an WHS2011).

I don’t get any events registered related to my GC100 / IP2CC actions… Below you find 2 examples of scenes that trigger this device.

08      01/30/15 9:06:22.608    JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x2fbca680>
08      01/30/15 9:06:22.608    JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=6 <0x2fbca680>
08      01/30/15 9:06:22.609    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x2fbca680>
08      01/30/15 9:06:22.609    JobHandler_LuaUPnP::HandleActionRequest argument action=RunScene <0x2fbca680>
08      01/30/15 9:06:22.609    Scene::RunScene running 6 Plisse_OP <0x2fbca680>
08      01/30/15 9:06:22.609    JobHandler_LuaUPnP::HandleActionRequest device: 88 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x2fbca680>
08      01/30/15 9:06:22.610    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x2fbca680>
50      01/30/15 9:06:22.610    luup_log:82: SetTarget device: 88 value: 1 <0x2fbca680>
50      01/30/15 9:06:22.611    luup_log:82: SetTarget send: setstate,1:3,1 <0x2fbca680>
50      01/30/15 9:06:22.615    luup_log:82: bad response: setstate,1:3,1 <0x2fbca680>
01      01/30/15 9:06:22.616    LuaInterface::CallFunction_Job2 device 88 function SSwitchPower1_SwitchPower1_SetTarget_run failed (null) with return false <0x2fbca680>
08      01/30/15 9:06:23.101    JobHandler_LuaUPnP::HandleActionRequest device: 88 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x2c11f680>
08      01/30/15 9:06:23.101    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x2c11f680>
50      01/30/15 9:06:23.102    luup_log:82: SetTarget device: 88 value: 0 <0x2c11f680>
50      01/30/15 9:06:23.102    luup_log:82: SetTarget send: setstate,1:3,0 <0x2c11f680>
50      01/30/15 9:06:23.107    luup_log:82: bad response: setstate,1:3,0 <0x2c11f680>
01      01/30/15 9:06:23.107    LuaInterface::CallFunction_Job2 device 88 function SSwitchPower1_SwitchPower1_SetTarget_run failed (null) with return false <0x2c11f680>

-------------

08      01/30/15 9:06:48.108    JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x2fbca680>
08      01/30/15 9:06:48.109    JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=5 <0x2fbca680>
08      01/30/15 9:06:48.109    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x2fbca680>
08      01/30/15 9:06:48.109    JobHandler_LuaUPnP::HandleActionRequest argument action=RunScene <0x2fbca680>
08      01/30/15 9:06:48.109    Scene::RunScene running 5 Plisse_NEER <0x2fbca680>
08      01/30/15 9:06:48.110    JobHandler_LuaUPnP::HandleActionRequest device: 87 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x2fbca680>
08      01/30/15 9:06:48.110    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x2fbca680>
50      01/30/15 9:06:48.111    luup_log:82: SetTarget device: 87 value: 1 <0x2fbca680>
50      01/30/15 9:06:48.111    luup_log:82: SetTarget send: setstate,1:2,1 <0x2fbca680>
50      01/30/15 9:06:48.116    luup_log:82: bad response: setstate,1:2,1 <0x2fbca680>
01      01/30/15 9:06:48.116    LuaInterface::CallFunction_Job2 device 87 function SSwitchPower1_SwitchPower1_SetTarget_run failed (null) with return false <0x2fbca680>
08      01/30/15 9:06:49.101    JobHandler_LuaUPnP::HandleActionRequest device: 87 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x2c11f680>
08      01/30/15 9:06:49.101    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x2c11f680>
50      01/30/15 9:06:49.103    luup_log:82: SetTarget device: 87 value: 0 <0x2c11f680>
50      01/30/15 9:06:49.103    luup_log:82: SetTarget send: setstate,1:2,0 <0x2c11f680>
50      01/30/15 9:06:49.127    luup_log:82: bad response: setstate,1:2,0 <0x2c11f680>
01      01/30/15 9:06:49.127    LuaInterface::CallFunction_Job2 device 87 function SSwitchPower1_SwitchPower1_SetTarget_run failed (null) with return false <0x2c11f680>

Can you tell me if this is by design or if I have to edit something?

PS.1. I already set the Event Watcher > Advanced > WatchCategories > “ABCDEFGHIJKLMNOPQRSTUVWXYZ” … just to be sure 8)
PS.2. I also checked /port_3480/data_request?id=lr_EventWatcher&report=log to see if it was related to the Syslog output only put also on that page no record is shown.
PS.3. Although the log (above) shows “bad response” and " failed" allot ??? it does work just fine, so the actions/scenes do work.

Thanks in advance!

[quote=“mcalistair, post:1, topic:185668”]I need some help on an issue… I’m missing some logging in Event Watcher that is related to my GC100 plugin for the IP2CC device.
[ for details see my config/project: http://forum.micasaverde.com/index.php/topic,29605.0.html ]

Got Event Watcher logging to my Syslog Watcher v4.7.0 (running on an WHS2011).

I don’t get any events registered related to my GC100 / IP2CC actions

[…]

Can you tell me if this is by design or if I have to edit something?

PS.1. I already set the Event Watcher > Advanced > WatchCategories > “ABCDEFGHIJKLMNOPQRSTUVWXYZ” … just to be sure 8)
PS.2. I also checked /port_3480/data_request?id=lr_EventWatcher&report=log to see if it was related to the Syslog output only put also on that page no record is shown.
PS.3. Although the log (above) shows “bad response” and " failed" allot ??? it does work just fine, so the actions/scenes do work.[/quote]

I’m not familiar with the GC100, but I have just installed the plugin to take a closer look. I see it is a category 1 device (an INTERFACE, class “F” in EventWatcher nomenclature.) If you take a look on the Category Codes display page at the variables that are logged for this category, you will see “— none —”, which explains all!

There’s two solutions:

[ol][li]you can add any device / serviceId / variable to EventWatcher using the [tt]ExtraVariablesFile[/tt][/li]
[li]you can wait for me to understand the GC100 a bit more and select some variables to put into the category “F” list[/li][/ol]

I’ll be as quick as I can at (2).

Hi akbooer,

Thanks for the quick reply! and creating a new dedicated topic for this.
I can confirm what you for F “— none —” in the Category Codes display page.

It has no rush for me so I go for: “2. you can wait for me to understand the GC100 a bit more and select some variables to put into the category “F” list”
This way it will be fixed for everyone and the Event Watcher App will become better for everyone ;D

PS Thanks for all your effort on all the apps you create and maintain!

Cheers

I’ve taken a look at the code and see the GC100 creates child devices of four types, viz.

[ul][li]Serial port[/li]
[li]Relay (Binary Light)[/li]
[li]I/R Port[/li]
[li]TTL Input (Motion Sensor)[/li][/ul]

Without an attached box for it to connect to, it creates none of these for me, of course. So it’s a bit hard for me to understand the exact need.

Surely it’s those child devices which need watching, rather then the GC100 itself? Perhaps I am not understanding its operating mode. Can you enlighten me (specifically by listing serviceId/variable names you want to watch?)

I understand its difficult wen you don’t have the device… some clarification.

The plugin is build for the actual GC100 [ Products ]
But iTach range is a subset of this and fully compatible. I’ve got the IP2CC [ Products ]

After installing the app it indeed installs 3 switches for me (I renamed them) see attached: parent_child.png
The details of the child’s are identical (except the ID of course) see attached: child_details.png

I would like to see the status change of the on/off (1/0) be reported by Event Watcher.

Does this make it more clear or do you need more input?

Thanks

If this is a full snapshot of all the child device variables (albeit a mosaic of several shots), then I am perplexed, because I don’t see a [tt]Status[/tt] device variable. To see this change you should be watching category 3 devices (“X” in EventWatcher-speak) but if it’s not there then you won’t see anything!

PS: I take it that you are in Zeeland?

[quote=“akbooer, post:6, topic:185668”]If this is a full snapshot of all the child device variables (albeit a mosaic of several shots)…

PS: I take it that you are in Zealand[/quote]

Yes the 2 screenshots pasted together show everyting except 1 var named “restricted” it was cropped, sorry. But indeed no Status.

No i’m in Gelderland but I like their motto :wink: :smiley:

OK. Strange that the plugin doesn’t maintain these. You would have the same problem, then, with any Vera remote app not being able to ascertain their state?

I wonder if there are any useful device variables under the GC100 device which reflect the status?

No i'm in Gelderland but I like their motto ;) :D
Most appropriate for our struggles with Vera!

Maybe the attached (Patched GC100 Driver) will solve your problem.

Hi Richard, can you elaborate on this “patch”? Who created it and what is changed?

I did (over a year ago) and it fixes the relay status.

Nice!!! Richard and Akbooer it solved ;D

After uploading the patched .xml and reloading it now shows extra parameters.
See: parameters.png

My syslog now also shows the events:

30-1-2015 19:34,Info,192.168.2.202,X [088] Plisse_Op, Status = 0
30-1-2015 19:34,Info,192.168.2.202,X [088] Plisse_Op, Status = 1
30-1-2015 19:33,Info,192.168.2.202,X [087] Plisse_Neer, Status = 0
30-1-2015 19:33,Info,192.168.2.202,X [087] Plisse_Neer, Status = 1

Thanks!

Good news indeed!

Is the App Store version not updated?

Nope, I downloaded the GC100 from the app store +/- 1 month ago and it doesn’t contain this fix provided by RTS.