Open stargieg opened 8 years ago
@stargieg OK, I will have a look at the luci packages
@stargieg I'm afraid I'm not knowledgeable enough to deal with luci test packages. I tried to generate luci-app-knxd and luci-app-linknx like I'm used to with other packages. It first complained about not having luac. Now I'm not sure if this must be in staging_dir/host or in the default os path. Using luac within the default os path it creates two ipk files, in my case: -rw-r--r-- 1 user group 5118 Jan 17 16:40 luci-app-knxd_0.2.0-1_ar71xx.ipk -rw-r--r-- 1 user group 4614 Jan 17 16:40 luci-app-linknx_0.2.0-3_ar71xx.ipk Could that be right? If I installed that on my ar71xx device I get a error when accessing the webserver: /usr/lib/lua/luci/ccache.lua:70: error loading module 'luci.controller.knxd' from file '/usr/lib/lua/luci/controller/knxd.lua': /usr/lib/lua/luci/controller/knxd.lua: bad header in precompiled chunk
Now I'm stuck, sorry
Hi @tru7 Thanks for testing. I know this problem. Luac "faster loading, protecting source code from user changes, and off-line syntax error detection" but is not portable. Now I have change this too SrcDiet and opt-in. It is WIP! db18c3e07b74750ded63517ab7fc6e21fe72740f
BTW: I am missing findknxusb for values in the device drop-down-box.
Hi @tru7 you can download ar71xx, x86_alix or x86_kvm_guest (kvm,vmware...) http://firmware-ga.lunatiki.de/firmwares/ on your own risk ;-) It is for testing only.
I started all over and this time a luac tool was created in staging_dir/host together with a bunch of other tools and other luci packages. The new luci-app-knxd and luci-app-linknx seem to work fine now on my Neatgear device. I did not check every detail but it looks OK so far. In my option it's OK to publish them on openwrt/luci and maintain them there. One question: is it supposed to restart the service when the new config is applied? I does not look to do so. I have to stop and start the service manually before it takes over the new arguments. One other disadvantage: when using ps command it's not possible to see all the command arguments. How about only use short version of arguments to see them all?
Hi @tru7
Yes we can use the short form of knxd arguments. I make a pull request for knxd openwrt package. I have some more changes. You can see all arguments with
cat /proc/$(pidof knxd)/cmdline
The luci track the uci changes with ucitrack
uci show ucitrack.@knxd[0]
This option is written by uci-default script. https://github.com/stargieg/packages-automation/blob/master/luci-app-knxd/files/etc/uci-defaults/luci-app-knxd
and /usr/sbin/luci-reload. This works for me. If not i can add function to the apply button.
on_after_commit = function() luci.sys.call("/etc/init.d/knxd restart") end
@mhei @tru7 Here are 2 luci packages for testing and upstream to openwrt/packages https://github.com/stargieg/packages-automation/tree/master/luci-app-knxd https://github.com/stargieg/packages-automation/tree/master/luci-app-linknx
Or can we make a new feed repo named e.g. automation or fieldbus. With these packages. libmbus modbus bacnet-stack knxd linknx sbus sigpi enocen