GC-100 Device Status Not updating

Plugins & Plugin Development General Plugin Discussion
1

I’ve got the GC-100 working and am able to turn on/off the relays from the Vera dashboard (UI4, Vera 2). However, the status on the relay device (a light bulb since this is implemented as a binary light) does not turn yellow when I turn the relay on. Also, the on/off buttons don’t change to green either to reflect the state of the relay.

Any ideas on why the status is not being reflected for these relays?

Thanks,

Bob

2

I use the iTach which is a mini GC100.
I have fixed the problem … but I have not tested on a GC100.
I changed 3 lines … One change may have been a change to the API … the other two were clearly bugs …

You can install by grabbing the file:
[url=http://rts-services.com/Schaefer/Vera3/I_GC100.xml]http://rts-services.com/Schaefer/Vera3/I_GC100.xml[/url]
Then with VERA 3:
Menu → “Apps” Sub Menu → “Develop Apps” → “Luup Files”
Upload the file you download from above. Check the “Restart Luup after reload” then “GO”

I had to toggle each of the Relay Virtual Buttons a couple times then reload the browser window.
After that everything works great! A few more lines in the startup code would have fixed this minor problem … but you would have still needed to refetch the browser window.

3

If I upload a new I_GC100.xml file and restart LuuP, will my existing devices be altered and do I have to delete the GlobalCache parent device and start over? Or will my existing devices be retained?

4

You should not have to add/remove anything … This just changes the existing implementation to update the status variable.

5

I uploaded the new I_GC100.xml supplied by RichardTSchaefer. Unfortunately, I still don’t see any changes in the status on the UI dashboard. The GC-100 relays seem to continue working just as before even with the new file which had some minor changes in the code.

Which part of the I_GC100.xml file would contain the logic to update the status on the UI?

6

Hi Richard!

I also have a couple of itach units that work flawlessly. Do you get relay status updates in the UI5 (off on)?

I have uploaded the the file you linked but nothing has changed for me. Could you advise what else i could check to get this working?

Cheers
Tim

7

Wow its all working (vera3)!! I uploaded the file a second time and toggled as suggested by Richard and status updated across the three relays!

8

Hi Richard!

I cant send email it seems (maybe because im new to the forum).

Okay - I have two WF2CC units and one WF2IR unit. I have not done much with the IR unit yet but have sent a few ir codes from vera and have got the desired result. I’m a big fan of the Itach units and plan to add a few more to my setup.

I work away from home so I have not tested things locally yet - I did however apply the update remotely and im now able to see the status of the relays (on off) on the UI with the wife confirming that the sprinkler solenoids im controlling did in fact switch!

Thanks heaps for the adjustments you made. The getstate (feedback) part of the system is very important. If there is anything you want me to test or do just let me know.

Cheers
Tim

9

Hi Richard!

When you run the “poll now” from a child contact on the gc100 (wf2cc) a no implementation error is displayed. Since uploading your trunk files to Vera I have been getting status updates to the UI (on or off). Is this status changing after getting values from a “getstate” command to the wf2cc?

I notice that if i change the relay state using another app the change is not reflected on the Vera UI.

If this has not been considered could you advise what I would need to look into/learn etc to have the device poll and reflect changes?

Thanks in advance
Tim

10

By another app you mean someone else connecting via wifi to the iTach ?
What app are you using ?

Or do you mean someone sending SetTarget actions to the Vera pseudo switch ?

I have not looked into all of the details of the plugin (I did not write it).
It might not be constantly monitoring the getstate of the device.
I know it pings the iTach to stay alive. But it might not actually be checking the status. (Assuming there is no reason to unless it tries to change it.)

I made the fix I gave you because it was not working for me in Vera.
I have not looked into other possible problems (Like multiple software components commanding the state of a single iTach)
If I can duplicate it; I can probably fix it.

Because this switch tries to look like a Vera Z-Wave switch … It inherited methods it did not implement; like the poll now. This is a Z-Wave level polling command. The original author implemented those commands at the “Binary Switch” semantic level only.

11

Connecting to the Itach direct using tasker or the ITest (from global cache) app.

Your other comments make sense. I have one of my Itach units controlling retic sprinklers - Vera handles the automatic scheduling, but I have setup some Tasker profiles so that we can turn off on from android homescreens on mobiles tablets etc. Vera is still able to send the scheduling commands of course but it would be great if the status change was sent to Vera. I suppose I could send getstate via Luup but I wouldnt have a clue how to use that info to update Vera or its UI

Thanks for the quick reply!!

12

There are plenty of Android Apps that you can use to turn on/off things via Vera.

If you have to use a screen … I like AutHomation
But I also like to use my HAL interface to just talk to my house.

Please turn on the sprinkler system HAL!

I have yet to get back a response:

I am sorry Rich, I'm afraid I can't do that.
13

Yes big fan of AutHomation and I will give HAL ago!

Thanks for the replies mate!

14

I have finally figured the fix to this relay status problem ;D
I am running UI 1.5.622 with the GC-100.
Go to the original I_GC100.xml file and go to line 245 and replace code.

incoming_data = luup.io.read(); if( incoming_data=="state," .. lug_module_by_child(lul_device) .. "," .. lul_settings.newTargetValue ) then luup.log('good response: ' .. tostring(incoming_data)) luup.variable_watch("urn:upnp-org:serviceId:SwitchPower1","Target",lul_settings.newTargetValue,lul_device) luup.variable_set("urn:upnp-org:serviceId:SwitchPower1","Status",lul_settings.newTargetValue,lul_device) return true else luup.log('bad response: ' .. tostring(incoming_data)) return false end
Runs with out errors in log.