Lutron RA2 Switch Control

[DonMor]

Ok, I did fix this in the Caseta, will update by next week an other beta to fix it in RA2, this is all the new change how HST use Parent, Child and Standalone. this should not impact the any function of the plugin.

[techguy]

I am running .129.

[DonMor]

What version of LutronRa2 plugin are you running?

[techguy]

Thanks for finding that. My version of Mono was already up to date so I ended up following this guide for HS3 and installed Mono from the mono repository and that seems to have fixed that error.

https://forums.homeseer.com/forum/ho...u-18-04-server

I do still get one error around "Device 55" not having a root:

Device 55 device is a child but does not have a root

This error occurs when I click on the "Devices" tab. Device 55 is the Main Repeater.

[DonMor]

See this post it may help

https://forums.homeseer.com/forum/ho...e-field-issues

[DonMor]

Please do a search for the error and mono you need to update your system it is not an issue of the plugin

[techguy]

This is an Ubuntu 20.04 (latest updates) system.

As for the logs I get those messages from the console output after I run the following command to start HS4:
sudo ./go

I have looked through the log file (HomeSeerLog.hsd) and cannot find the log message anywhere in it.

Here is a more complete output from sudo ./go

06:31:34:6891:[Info]->Checking device parent child relationships...
06:31:34:6906:[Warning]->Issue checking child device (55) LUTRONRA2 Equipment Room MAIN_REPEATER
06:31:34:6908:[Warning]->Device (55) LUTRONRA2 Equipment Room MAIN_REPEATER does not reference a parent, it should reference one parent
06:31:34:6913:[Warning]->Issue checking parent device (56) LUTRONRA2 Equipment Room MAIN_REPEATER
06:31:34:6915:[Warning]->Device (55) LUTRONRA2 Equipment Room MAIN_REPEATER is marked as child, but does not reference any parent
06:31:34:6928:[Info]->Found 1 issue(s) with devices
06:31:34:6930:[Startup]->Start up complete.
Type 'shutdown' to shutdown HomeSeer

> 06:31:34:7008:[Startup]->Scripting is OK and is now running Startup.vb
06:31:34:7075:[TTS]->Speak ():Welcome to Home-Seer
/opt/HomeSeer/./speak.sh: 2: flite: not found
06:31:34:9067:[Info]->System connected to MyHS Service, waiting for acknowledge...
File upload thread started
06:31:34:9567:[Info]->System connected to MyHS Service successfully with license ID <removed>
06:31:35:6139:[LutronRA2 Debug]->Send: <username>
send: <username>
SENT User: <username>

06:31:36:6211:[LutronRA2 Debug]->Send: <password>
send: <password>
SENT Password: <password>

Connected to 192.168.1.65:23
06:31:36:6359:[LutronRA2]->Telnet Login succesfull
Operations with the response
Operations with the response ~ERROR,1
Operations with the response
06:31:54:8276:[Web Server]->Web Server authorized login successful from: 192.168.1.99 User: <username>
Device 55 device is a child but does not have a root<----------------------------------------------------------------------------------------I clicked on the device in the web interface right here
web device 'LutronRA2' on device 55
web device '00:00:01' on device 55
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Operations with the response ~ERROR,1
Operations with the response

[DonMor]

Please post what system are you running, windows? Linux?, also when post the log be sure you copy the date time and type of log

[techguy]

In the new install I don't have any events programed.



I never re-programed any of them in the new HS4 install. Is the database/config stored somewhere else from the HS4 install folder?

[DonMor]

I think you made a loop in the events, your "if device" ( if 1 to 99) change the same "then device" to 10, so your events run and run and run I think.

try to disable it or delete.

[techguy]

Well now I have a bigger issue. HomeSeer crashed and I started to get the error below. I tried to delete all devices and start over but after each time I restarted HomeSeer the devices came back (even with the RA2 plugin completely removed) and I ended up deleting the entire HomeSeer folder and restarting from scratch as I wasn't doing anything yet.

I got HomeSeer licensed and installed the RA2 plugin, but now the RA2 plugin will not register. I went ahead and just enabled it using the trail mode and re-added the Lutron controller. But now when I click on a device on the Device Page I get this error again:

Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_misc: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.
Error in device_prop: The requested operation caused a stack overflow.

I was getting this error before and was able to get it to stop by deleting all devices from the page and re-adding them from the RA2 plugin but that isn't working this time.

[techguy]

It looks like the Do not log is already disabled.




After I press the button on the switch it takes about 3 seconds and this appears in the logs:

Operations with the response ~OUTPUT,13,1,45.26
Response Output99: ~OUTPUT,13,1,45.26
Response Output100: ~OUTPUT,13,1,45.26
Response Output101: 4
setdevice Output~40445.26
fin output~2
fin output~
fin output3~Lamp Module45.26
Ped: ByteObject...
fin output2~
fin output4~
setdevice Output-40445.26
setdevice Output240445.26
Operations with the response ~OUTPUT,13,29,0~OUTPUT,13,30,1,45.26
Response Output99: ~OUTPUT,13,29,0~OUTPUT,13,30,1,45.26
Response Output100: ~OUTPUT,13,29,0~OUTPUT,13,30,1,45.26
Response Output101: 4
Response Output99: ~OUTPUT,13,29,0~OUTPUT,13,30,1,45.26
Response Output100: ~OUTPUT,13,29,0~OUTPUT,13,30,1,45.26
Response Output101: 5
10:15:03:5331:[Event]->Event Trigger "Test New Event"
SwitchDim
10:15:03:6021:[Event]->Event Trigger "Test New Event"
SENT #OUTPUT,13,1,10,00:00:01,00:00:00

SwitchDim
SENT #OUTPUT,13,1,10,00:00:01,00:00:00

Operations with the response
Operations with the response ~OUTPUT,13,1,10.00
Response Output99: ~OUTPUT,13,1,10.00
Response Output100: ~OUTPUT,13,1,10.00
Response Output101: 4
setdevice Output~40410.00
fin output~2
fin output~
fin output3~Lamp Module10
Ped: ByteObject...
fin output2~
fin output4~
setdevice Output-40410.00
setdevice Output240410.00
Operations with the response ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output99: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output100: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output101: 4
Response Output99: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output100: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output101: 5
Operations with the response
Operations with the response ~OUTPUT,13,1,10.00
Response Output99: ~OUTPUT,13,1,10.00
Response Output100: ~OUTPUT,13,1,10.00
Response Output101: 4
setdevice Output~40410.00
fin output~2
fin output~
fin output3~Lamp Module10
Ped: ByteObject...
fin output2~
fin output4~
setdevice Output-40410.00
setdevice Output240410.00
Operations with the response ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output99: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output100: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output101: 4
Response Output99: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output100: ~OUTPUT,13,29,6~OUTPUT,13,30,1,10.00
Response Output101: 5

[DonMor]

Please remove the do not log in the device settings and look the log, this is mine with when the spot light turn on the turn on the chandelier, it is instant

[techguy]

I am now testing some of basic functionality here and I am finding that the response time is fairly slow. From the time that I press the lighting button to the effect/trigger taking place takes about 2-3 seconds. I am hoping that Its just something that I am doing wrong.

Here is my current event.

[DonMor]

new function for what you want to do in the Beta 124

• Set Last Value to Device: change the value of Last in the device
• Set Night Value to Device: set a value for a dimmer, if the light is off and turn to any value send a command to dim at that value (set back to 0 to remove this function or call the events "Reset All Night to None Value to Device" )
• Reset All Night to None Value to Device