New Raspberry1-2B+ Images based on OpenWRT (Update 3.5877)

[jensc]

Shite!!

Oh well... looked like something worth trying. I'll check back a year from now and see if things have improved.

Good luck.

[Timeless]

Mmh, according to https://wiki.openwrt.org/toh/raspberry_ ... spberry_pi it seems RPi3 is still unsupported with "OpenWrt's Chaos Calmer" release .

For RPI3 recent openwrt's trunk version is required and actually I'm not able to compile OpenZWave due to strange compiler errors on that trunk version, hence no domoticz package possible for RPI3 , too .

I had no troubles getting open-zwave to work on a RPi3, see my makefiles in this post: Re: Domoticz on OpenWRT

[irimi]

I had no troubles getting open-zwave to work on a RPi3, see my makefiles in this post: Re: Domoticz on OpenWRT

Yes, indeed, your Makefiles are working fine. I'll update my feed, thank you very much !
But attention, the defined archive version 1.5 in your makefile for openzwave build is nearly one year old ! But no problem with recent version 2298 , too.

[Timeless]

Mmh, v1.5 is from 15-Aug-2016 according to the Git Releases. We are only 6 days in 2017 hehe . I think using a trunk version for any software as a stable build is not always advised. And since I'm trying to get this in OpenWRT/LEDE a trunk version of anything will be rejected immediately.

[irimi]

Mmh, v1.5 is from 15-Aug-2016 according to the Git Releases. We are only 6 days in 2017 hehe . I think using a trunk version for any software as a stable build is not always advised. And since I'm trying to get this in OpenWRT/LEDE a trunk version of anything will be rejected immediately.

That's really strange ! From my point of view this tag does not match to archive content. If you unzip it , all files have the date 11.01.2016 and change log may be from January 16 , too !

And recent snapshots are is still v1.4.xxxx if you look at http://old.openzwave.com/snapshots/ . I guess this tag is just the start of v1.5 dev branch, I don' know .

Latest stable is here: http://old.openzwave.com/downloads/. Sure, it is a risk using unstable versions, but I had no problems with openzwave snapshots since the last two years. The big advantage is also newer devices are supported !

[Timeless]

Mmh yeah. It seems that you are correct. Strage way of using tags my opinion.

Normally one should use a release tag when the software is released. And this is also the way they used it in the past. But suddenly they decided to use a tag for a start of a dev version.

Thanks for noticing. Great to know that you also compiled recent trunk with my makefiles. I guess you only changed the archive or git checkout? No patches or makefile changes?

I must say that my experience with OpenZwave and Zwave+ is really uncomfortable. Max uptime I've had since weeks is 4 days. And sometimes OpenZwave uses 100% of a CPU core after startup(or network heal) and the only salution is to restart the OpenZwave component. Sometimes this crashes Domoticz aswell.

[Timeless]

Also something else. I noticed serveral dependencies to "userland". Do you have any idea what that does and why it should be included?

I'm not sure but I don't see that it is already included in OpenWRT/LEDE. And since I've not used any makefiles for userland and Domoticz runs fine without. I assume they are not needed.

[irimi]

The userland package is RPI specific and domoticz uses the command

Code: Select all

vcgencmd

of that package to evaluate RPI temperature and RAM usage, i.e. that is the interface to the "motherboard sensors". But it also contains tools for RPI's hardware e.g. raspicam, HW video decoding.

My RPI 1 is running very stable on openwrt calmer: the system without reboot for 6 months and the domoticz app for about 2 months continuously.
But actually I'm observing the problem that RAM usage of domotcz is increasing 1% per day. After domoticzs is restarted the memory is freed again, hence I assume there is a memory deallocation bug in a static lib or in domoticz code itself. To be checked with gdb .....

[Timeless]

Yeah or maybe it does not garbage collect untill its needed. Do you also use Zwave+ or just normal Zwave?

But ram usage does also work without useland. And why is there need for video drivers? There is no video support in OpenWRT anyway?

Domoticz should stop using the WiringPi and useland for such functions but instead use sysfs for GPIO and /sys/class/thermal/thermal_zone0 for the CPU temp. This will make domoticz more compatible with non-raspberry platforms.

I'm currently using collectd to plot my CPU temperture in agraph which is displayed in LuCI. Because Domoticz does not support it.

[irimi]

I'm using just normal ZWave. Video: maybe for raspicam integration, but I don't have any experience with it .

[Timeless]

Have you once tried to update a new recompiled version of OpenZwave without recompiling and installing thesame version of Domoticz?

[irimi]

Have you once tried to update a new recompiled version of OpenZwave without recompiling and installing thesame version of Domoticz?

As far as I know openzwave is linked statically to domoticz according to CMake config. Since domoticz does not use the dynamic lib, this is not possible. I don't know how to configure the openwrt makefile that domoticz is build with dynamic use of openzwave lib.

[Timeless]

Yeah true, I had to recompile Domoticz to make it work.

[Timeless]

Also note, Domoticz + OpenZwave is now supported in OpenWRT/LEDE see: this