More available RAM after 2.5.2 update

Lounge
1

I have a C7 that I just updated to 2.5.2 along with the new Sonos Integration.

My Hub went from between 200M-300M of available ram to now over 750M of ram. How is that possible??

2

Gopher Magic :grin:.

They've enabled some memory compression to allow the ZW-JS stack enough room to operate. When I saw it in Beta the first time, it definitely caught me be surprise.

3

Thanks! That’s crazy though. Over double the amount of memory for me. Breaths new life into my hub.

4

Yeah, I had to look twice, went and got another cup of coffee and then checked again to make sure I wasn't dreaming.

5

How much memory does this require?

6

If you use ZWave devices, then consider switching to ZWaveJS. The upgrade is amazing, especially on a C-5. The new stack permits adding S2-compatible devices, and in general makes zwave device management much more robust.

7

Couldn't say exactly how much, but do know that my C8 had issues with it before (sub 200MB), C7s were fine - different JVM stack, and now it's consistently showing 650MB+ free (want to say it was close to 800 before I told it to use ZW-JS this time).

8

So you bring up a good point. Despite everything I’ve read, I don’t really understand why I should switch to ZW Js when all of my 31 devices are working fine and stable.

I hesitate to fix what isn’t broken.

9

Generally a very good philosphy. If it's working and you don't need/want any of the enhanced capabilites, at this time, not something you need to do. Memory change makes it possible, but doesn't require it.

10

I'll give a slightly different answer than @thebearmay. You should consider switching for three reasons:

  1. While Z/IP gateway will never stop working, Silicon Labs is no longer supporting it - it isn't getting bug fixes (or potential security fixes).
  2. ZWaveJS remains under active development - as an opensource project it has huge community support, and makes it possibly to backup your entire Hubitat setup locally (including z-wave radio) and move it to a new hub, or possibly even a new platform.
  3. Hubitat has made it easy to switch back & forth between Z/IP gateway (Legacy) and ZWaveJS. While testing ZWaveJS over the last 2 years, I switched back and forth dozens of times. But for about the last 6 months, my hubs are exclusively on ZWaveJS.
11

I appreciate the info. You make a compelling argument. However, I don’t think it really applies at this point to my ecosystem.