@dest I think you have more important things than this.
Please let me know if you have any progress on the matter.
Thanks in advance.
K

@dest said in Vera or not vera?:

@akbooer Last time, the thing I remember, the plugin was unable to "connect" to the socket on the DSC controller!

I would need to recreate my DSC device on openLuup and disable Vera for being able to test!

DSC.zip

Hi @DesT!

Maybe you may have fixed the dsc plugin error?

@perh said in Vera or not vera?:

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

After many attempts, he finally succeeded.
Ser2net installed, restarted, ser2net.conf configured.
MySensors plugin is not red, startup lua does not write an error.

However:

The children's tools were not made, but the shutters did not appear.
Do they need to be created manually?

I think I also reached the limit ....

@perh said in Vera or not vera?:

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

There is no ttyUSB file in the / dev directory.
There are several tty files numbered here, but without USB ...

@perh
How can I check if I am using debian 10.6?
I tried to type, but unfortunately there is no such directory ...

@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?

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, haven't you experienced this?

@perh said in Imperihome - missing devices:

That was it.

/cgi/Imperihome.lua: Changed "newTarget" to "newTargetValue" at line 385, 672 and 675. (i would upload the updated lua file, but im missing priveleges)

This was not an issue before, has there been changes on this in openluup?

@mrFarmer - FYI

I modified the right lines, it really works now!
At the same time, I can see the icons on the imperihome flashing as if they are constantly reloading ...

@perh

Yes, local tools are good for me too ...
It would be good if the error could be fixed.

The biggest trouble is that I don’t see an alternative to replacing the imperihome.

I'm sorry @PerH!
I didn't see the same mistake.
I don't have a z-way yet, I thought it was your fault for it ....
Also I have the categories, sub categories ...

Do I see that you don't have a solution to the problem yet?

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

Hi @mrFarmer,

I also have a question about ImperiHome:
I'm trying to configure imperihome with openluup.
Imperihome recognizes the new system, with all devices, status feedback is perfect.
If I turn on something on imperihome, it will seem to be temporarily turned on and then turn off. Device does not actually change.
Can you help me with what could be the problem?
Thanks.
Krisztian

@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 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 ...

@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?

@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 ....

@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 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?