https://janessa.me/esh/org.openhab.binding.amazonechocontrol-2.5.6-fix-leaks-fix-connection.jar
Out of interest - this was the memory use in the openhab container before and after removing the binding.
1 Like
That would be awesome - whenever you get the time Jan - the obvious use of this binding is incredible so many people are grateful for getting it working!
2 Likes
Works fine for me: RPI3, OH 2.5.0 Release Build. Free memory is still decreasing but at a lower rate. Free mem is now 227M (total: 926M) two and a half hours after restart of openhab2.service and was 232M minutes after the restart. So 5M have been consumed since restart. Does anyone know if this is the expectable behaviour on an RPI3?
EDIT: Of course no more errors in opehab.log regarding the binding.
I also run on a RPI3 and I find my free memory does decrease slowly. I have never got to the bottom of why. It takes 2 or 3 weeks to become very low and since I have a scheduled reboot every week it never becomes a problem for me.
Hmm, 21 hours later and Iām down to 30 megs of free RAM. perhaps something else is causing this? I am also using MyQ as someone mentioned earlier. Iāll check to see if there are other updates I should apply here too
openhabian@openHABianPi:~ $ free -h
total used free shared buff/cache available
Mem: 975M 504M 30M 12M 440M 406M
Swap: 99M 0B 99M
openhabian@openHABianPi:~ $
Show bundle:list | grep -i amazon. If itās not a problem in another bundle, youāre probably running a wrong version.
Is this going to be updated on the docker image? Saw 2.5.5 was updated with something a few hours ago, but havenāt figured out where to find the changelog
can i install the linked new bundle version (2.5.6) also on my 2.5.5 OpenHabian on my Rpi4 ?
From my understanding there should be no difference in openhab for any RpiX version (nor windows even). So, if you have a prob with 2.5.5 binding try the version one from J-N-K above. He removed an error (or more than one) from the 2.5.5 release version and named it ā2.5.6-fix-leaks-fix-connectionā.
itās on the correct version I believe:
openhab> bundle:list | grep mazon
82 ā Active ā 80 ā 2.5.6.202006152137 ā openHAB Add-ons :: Bundles :: Amazon Echo Control Binding
openhab>
the date code there is from the 15th. I tried the earlier one (which may be removed) from the 14th.
Iāll have to poke around more to see what else could be causing this. Is there a way to see which modules are using / leaking memory? Iām on OpenhabianPi and have tried sudo apt-get update / upgrades but they are all up to date. Iām on 2.5.5 currently, but a bit weak on linux.
@dotat, I donāt think youāre running low on āfreeā RAM. Your cached memory shows 406M, so you have plenty of memory available to run applications/processes. This disk cached memory is just being temporarily borrowed to speed up the OS, but will lend it back when it is needed by applications.
Hereās some information about memory allocations (with explanation for cached memory):
https://www.cloudways.com/blog/linux-ate-my-ram-memory-myth-busted/
However, if you experience out of memory issues that affect operation then something is definitely wrong with your installation. So hopefully that is not occurring.
- Thomas
Ah thanks, I was actually looking at that and wondering if it was the first or last section of free to be worried about. Much appreciated, Iāll stop the reboots and see how it goes. I was getting some warning (before the update) about something taking more than 5000ms to respond. That search lead me here.
cheers!
I think we have to wait till the 2.5.6 version will be in the latest docker image. I saw there is a 2.5.6-snapshot image, but I didnāt try it yet.
I didnāt realize there was a separate openHAB forum for German-speaking users. There are many openHAB + AmazonEchoControl add-on Beta version users who are just as lost as we seem to be with getting the Beta binding working again 
I miss my functioning smart home - this has been a very dysfunctional and frustrating week.
okay. Will try that. How is the standard process of replacing an released binding in openhab with a later fix-version, which can not be installed by PaperUI but needs to be placed manually to the addons-folder?
Do i have to uninstall the release-binding in paper ui upfront copying the fix-version to the add ons folder?
What i did i described above. Some say, that this does not help long but is overritten. On my rpi itās fine since i installed.
I never did an update of a binding the way you describe but only have red about that.
I updated my Container by using the openhab-cli.
Here is a short manual how to start the cli in the docker container:
then do the update like it is described here:
I get an error by bundle:update.
āError executing command: janessa.meā
Somebody knows what I can do?
Download the jar file and use something like FileZilla to transfer the it to /usr/share/openhab2/addons then restart OH.
EDIT: Using FTP to move the file you may need to check the permissions as it should be -rw-rw-r-- for the jar file. Use ls -al /usr/share/openhab2/addons to verify this. If you need to make a change then use openhabian-config and run fix permissions or manually with sudo chmod a+rw name-of-file-to change
1 Like