Oh the joy of pairing

[DesT]

@krisztianszabo yeah by default the plugin use the default password which is "user", if it's not your case, you can modify the code to change the "default" password to put yours!

[krisztianszabo]

@dest said in Vera or not vera?:

@krisztianszabo yeah by default the plugin use the default password which is "user", if it's not your case, you can modify the code to change the "default" password to put yours!

I guess the interfacepassword needs to be rewritten in I_DSCAlarmPanel1.xml?
I found text to this effect in this file, but unfortunately I couldn't find where to insert the "interface password" instead of "user" ...

@akbooer

"Any password in Vera's device config will be passed cleartext to the MiOS backup servers ..."

I also found the above text in the file. It doesn’t sound too good for the password to be passed to the mios in plain text. Isn't that a problem for me?

[akbooer]

Sorry, I don’t use this plugin, so have no idea what problem you’re trying to solve.

[DesT]

@krisztianszabo The password is only used between openLuup and DSC, so there's no password going out!
Check the the file, you have a line like that:

local password = luup.variable_get(DSC_PANEL_SID, "InterfacePassword", device) or "user"

so you can replace "user" there!

[krisztianszabo]

@dest said in Vera or not vera?:

@krisztianszabo The password is only used between openLuup and DSC, so there's no password going out!
Check the the file, you have a line like that:

local password = luup.variable_get(DSC_PANEL_SID, "InterfacePassword", device) or "user"

so you can replace "user" there!

Yes thanks I found it in the meantime that.

I typed my own password in place of "user", but unfortunately the connection was not established.
Unfortunately, the Dsc Plugin is indicated by a red border.

[DesT]

That's 'cause of what I said to @akbooer , I need to dig a little bit more as the plugin is having a hard time to "stay connected" to the DSC!

[DesT]

@akbooer What's in my plugin code I need to check that can trigger openLuup to reload ?

[krisztianszabo]

@dest said in Vera or not vera?:

That's 'cause of what I said to @akbooer , I need to dig a little bit more as the plugin is having a hard time to "stay connected" to the DSC!

I understand.
I would be happy to offer my help, but I'm afraid you're not going to do much with me ....

[akbooer]

@dest said in Vera or not vera?:

What's in my plugin code I need to check that can trigger openLuup to reload ?

• Creating new child devices?
• When does it happen?
• Do you have Startup and main logs?

[krisztianszabo]

@akbooer
I find that sunrise and sunset happen late on openLuup compared to vera. OpenLuup is delayed for more than 1 hour.
Could this be a localization problem?

[akbooer]

@krisztianszabo said in Vera or not vera?:

Could this be a localization problem?

You perhaps have not set your location correctly in openLuup. The latitude and longitude are initially set in the Lua Startup code, which has as default:

-- You can personalise the installation by changing these attributes,
-- which are persistent and may be removed from the Startup after a reload.
local attr = luup.attr_set

-- Geographical location
attr ("City_description", "Greenwich")
attr ("Country_description", "UNITED KINGDOM")
attr ("Region_description", "England")
attr ("latitude", "51.48")
attr ("longitude", "0.0")

[krisztianszabo]

@akbooer said in Vera or not vera?:

@krisztianszabo said in Vera or not vera?:

Could this be a localization problem?

You perhaps have not set your location correctly in openLuup. The latitude and longitude are initially set in the Lua Startup code, which has as default:

-- You can personalise the installation by changing these attributes,
-- which are persistent and may be removed from the Startup after a reload.
local attr = luup.attr_set

-- Geographical location
attr ("City_description", "Greenwich")
attr ("Country_description", "UNITED KINGDOM")
attr ("Region_description", "England")
attr ("latitude", "51.48")
attr ("longitude", "0.0")

Thank you, I corrected the values. We will see the result when it gets dark ...

[krisztianszabo]

@akbooer
For some reason, after the AltUi "reload engine" I get a "controller did not respond" response with an orange background.
So far, I thought dsc and harmony are not due to connection.
I just deleted my two unconnected devices.
And still this message.
I looked at the logs for the duration of the error message and did not see anything to throw out.
How can I find out the cause of the error?

K

[akbooer]

@krisztianszabo said in Vera or not vera?:

after the AltUi "reload engine" I get a "controller did not respond" response with an orange background.

This is absolutely normal and is simply AltUI noting that connection has been lost during the restart. The only time you need to worry is if there is a timer counting away the seconds for a long time.

[krisztianszabo]

Hi @DesT !
I don't want to urge you, I'm just interested,
do you have any good news about dsc?
Thanks.
K

[krisztianszabo]

Hi @akbooer ,
Another task ahead of me:
I have a 15 channel shutter control module that I want to run under OpenLuup. (if you help I can transfer the plugin files)

The shutter control interface is connected to the vera via usb.
The following setting is in Vera:

Where can I make such settings in openLuup?
Thanks

[PerH]

Probably much the same way as the RFX?
https://smarthome.community/topic/253/setting-up-rfxcom-plugin-in-standalone-openluup?_=1606133137706

baud, parity, etc is set up in the ser2net file.. then connect using IP:Port (127.0.0.1 if its on the local computer)

[krisztianszabo]

@perh
Thanks for the reply and tip.
I installed ser2net, I think it worked fine, but I don't have a / serial directory under the / dev directory .....
What do you think I should do then?

[PerH]

You're running Debian 10.6 right? if so its hidden, but just type cd /dev/serial/by-id/

[PerH]

if not, you can use /dev/ttyUSBxx(whatever usb you device is connected to)