Vera or not vera?
-
@akbooer said in Vera or not vera?:
No, that's the wrong one. Looking at the update log in the file I see:
-- 2020.10.15 fix possibly missing "station_name" / "home_name" (thanks @Krisztian_Szabo) -- 2020.10.21 another fix for the above (with multiple stations) (thanks again @Krisztian_Szabo)so you need at least 2020.10.21. Update from the development branch.
Would you forward me the github link, where I can download the 10.21 updated files?
-
Just type development into the Netatmo line update box on the Plugins page and click the update button.
-
@akbooer said in Vera or not vera?:
Just type development into the Netatmo line update box on the Plugins page and click the update button.
Grateful thanks!
Netatmo is fine too!Have no idea about a Harmony control error?
-
Has anyone already managed to install the DSC plugin under AltUi?
I have already created the two devices manually in (DSC alarm panel and Partition 1)
In AltUi, but unfortunately I don’t see the possibility to specify many variables. (eg zones, motion detectors, etc.)
Do you have any ideas? -
I’m afraid that I don’t know anything about Harmony or DSC (but I’m glad that you have Netatmo working again.)
-
@DesT said in Vera or not vera?:
I'm very happy with openLuup ( @akbooer ) and having z-wave.me hardware to "talk" with all my zwave devices!
I also use the DSC plugin in vera (for the moment), as I didn't take the time to debug the plugin for DSC and make it works directly in openLuup!
Did you manage to get ahead with how the DSC plugin openLuup works?
At the moment, the DSC plugin works for me under vera as well.
The DSC status feedback in openLuup / AltUi seems a bit slower compared to vera. (Of course this is understandable because that's where the data comes from)A direct, faster connection between DSC and openLuup would be better.
In many cases I have a DSC motion / doorwindow sensor that operates lights. Previously, without OpenLuup, the response was much faster.
Didn't the above cause you a problem?
Thanks to
K -
I have the dsc plugin decoded if you want to give a try to debug it on openluup..
-
@DesT said in Vera or not vera?:
I have the dsc plugin decoded if you want to give a try to debug it on openluup..
The thing is, unfortunately, I am a beginner on the subject.
Can you help me how to find and fix the error? -
@krisztianszabo I would need some time to check that... maybe next weekend! I would need some help of @akbooer for that, 'cause last time it was working fine until an update of openLuup and then it start failing to connect to DSC!
-
Always here to help.
-
OK thank you!
I’m really looking forward to resolving the bug because as long as I don’t have DSC in openluup I can’t leave the vera.K
-
@krisztianszabo I know, I'm in the same situation as you
-
@DesT said in Vera or not vera?:
was working fine until an update of openLuup and then it start failing
...that doesn't sound right!
Are you sure?
-
DesTreplied to akbooer on Nov 15, 2020, 4:16 PM last edited by Crypto Nov 15, 2020, 11:21 AM
-
I just tried it again, and pretty sure the problem is around the connection to DSC. When DSC plugin connect to the controller, the TCP connection open but openLuup reload again... and of course the connection doesn't come back online.
In DSC there's a limitation that only ONE connection at the same time can occur, so while openLuup reload again and again, the connection is still open and can't connect 'cause "envisalink" module refused it!
Under Vera, I'm never getting this issue!
-
@DesT said in Vera or not vera?:
I just tried it again, and pretty sure the problem is around the connection to DSC. When DSC plugin connect to the controller, the TCP connection open but openLuup reload again... and of course the connection doesn't come back online.
In DSC there's a limitation that only ONE connection at the same time can occur, so while openLuup reload again and again, the connection is still open and can't connect 'cause "envisalink" module refused it!
Under Vera, I'm never getting this issue!
I copied the files, it's not related to me either.
What I noticed is that there is no interface password between the variables. It's in Vera's case. This is not problem? EnvisaLink4 is my interface.
Do you think this can work? -
@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!
-
@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" ..."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?
-
Sorry, I don’t use this plugin, so have no idea what problem you’re trying to solve.
-
@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!
66/104