[RELEASE] KNX Commander or how to control KNX home with XBMC video player

  Thread Rating:
  • 1 Votes - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
panzaeron Offline
Junior Member
Posts: 38
Joined: Jun 2009
Reputation: 0
Post: #11
I would say, ab big thank you for your great plugin.

My Platform is OpenELEC PVR and it works without any problems. It is a nice feeling, when the movie starts and the lights dimm down and at the movie end up again Smile
find quote
adm1024 Offline
Junior Member
Posts: 16
Joined: Apr 2009
Reputation: 0
Location: FR
Post: #12
New version
A new version released : 0.1.0
The changes are :
  1. Debug mode
  2. verbosity reduction
  3. return to the normal icon (not xmas icon)
  4. preFrodo compatible


Regards

XBMC AddOn to control your lights with XBMC
(This post was last modified: 2012-08-13 22:53 by adm1024.)
find quote
adm1024 Offline
Junior Member
Posts: 16
Joined: Apr 2009
Reputation: 0
Location: FR
Post: #13
[NEW VERSION]
VERSION 0.1.1 : real debug option to reduce info in xbmc.log
The previous version didn't use the function correctly.

XBMC AddOn to control your lights with XBMC
find quote
leechguy Offline
Member
Posts: 99
Joined: Aug 2009
Reputation: 3
Location: The Netherlands
Post: #14
I had a peek into the code (v.0.1.1) and noticed the following:

Code:
my_xevstop = __addon__.getSetting("XEVSTART")

'XEVSTART' should be 'XEVSTOP'.


Code:
while (xbmc.abortRequested):
    #Execute XBMC STOP Event settings on Device
    if my_xevend=="true":
    linknx_send(my_ip,my_port,my_xevstopcmd,my_xevstopval)
    
    xbmc.log('KNX-Commander: Bye')

Should the 'while' not be a simple 'if' statement instead? When shutting down, xbmc.abortRequested will be true so the 'while' will loop until the script gets killed by XBMC. The 'KNX-Commander: Bye' message appears multiple times in you log I guess..
Thinking about it... you don't need the while (or an if for that matter) at all.

Also, there seems to be only one reference to the 'my_xevend' variable. Basically you are comparing an uninitialized variable with the word "true". The result of this compare will be false so the linknx_send() statement will never be executed. (When disabling the addon, XBMC also complains and writes the error message to the xbmc.log)
When looking at the code I reckon the 'my_xevend' should be 'my_xevstop'.

In the English strings.xml "<string id="69500">LinKNX serveur</string>" should be "<string id="69500">LinKNX Server</string>".

Other than that, cool stuff Smile Now if only this KNX stuff wasn't so @#$# expensive... I haven't decided yet what technology to use, but I'm leaning towards z-wave.
(This post was last modified: 2012-11-09 01:12 by leechguy.)
find quote
adm1024 Offline
Junior Member
Posts: 16
Joined: Apr 2009
Reputation: 0
Location: FR
Post: #15
Hello Leechguy and thanks a lot for your feedback.

I have considered your suggestions and they will be incorporated in the next version with your name.
For information, I started the addon by using the 'X10 Commander' and changing only the X10 part to KNX/LinKNX one. I have not seen the code completely. About Stop XBMC for part I do not use it personally, so I did not tested it. I'll do in the future.

I made some improvements in the FRODO Xbmc alpha version and the future version of the addon will be launch only after FRODO Release Candidate.

Regards

XBMC AddOn to control your lights with XBMC
find quote
Post Reply