Seeking Advice:

[PerH]

The system has been running well for a while now, and with the latest firmware and updates on Z-Way its looking good!
I also have 3 UI's in the shape of old pads/phones wearing 3d printed frames around the house, running Imperihome. (WAF just shot upwards exponentially!)

The vera on the other hand.. I've kept it on duty for geofencing and zigbee, and both of them are not working well.. ZiGate is in the mail, but geofencing is still an issue i'd like to sort out.
On another thread i got the tips IFTT and Automate, does anyone know of good set-up guides for this?
Any other geofencing suggestions? I'm running Iphone Locator for my wifes phone, but its restricted to home and away (right?)..

[rafale77]

On geofencing with iPhoneLocator, you can write anything you want with it using a variable watch on the distance... I trigger vacation mode, preheat/cool the house and all sorts of various scenes with this.

[PerH]

Looking at memory usage, i see that something is accumulating here..
last 7 days:

this is what i see with "free" after a restart:

The "used" is stable at around 800, it's the buff/cache thats accumulating. Should I be worried? Did a restart in case I should. how do i find out whats driving it up?

[akbooer]

With memory statistics, it's always confusing, since there are so many options for retrieving/displaying the information.

Remind us about this system:

• running on (RPi / virtual / ...),
• how much physical memory it has (is that 4GB on free?) (better use free -h)
• whether the units on your graph are, in fact, MB
• where the data for the plot actually comes from
• ...

I would say that a modest increase over time, to some asymptotic limit, is to be expected as the Data Historian fills its in-memory cache. This is, of course, configurable.

Here's a plot of memory used (MB) / cpu (%) / uptime (days) for one of my openLuup systems over the last year. You can see that memory use corresponds to uptime, to some extent. But this is not a memory leak. This is not Vera.

[PerH]

Its a chromebox 1, 4gig RAM. the graph unit says "Mil" for some reason, as in million bytes i guess. Its set by the system monitor plugin..

I don't care as long as it resets and doesn't cause trouble, but is coming that close to the border smart? suppose i don't need data historian to store with too much retention, as i'm using influxdb..

This is the whole time i've been storing, i thought the resets were when i rebooted, so i wasnt sure..

Now:

[PerH]

I've also been trying to get collectd up and running, but it doesn't seem to take my server port setting in collectd.conf seriously. looking with lsof, i see it setting up a UDP port at some arbitrary number that's changing on service restart..

[akbooer]

This may just be confusion about nomenclature – it may simply be that 'used' includes 'cached', which is actually instantly available on demand for new uses. This is not a problem.

@perh said in Another transition from Vera to OpenLuup - PerH:

I've also been trying to get collectd up and running,

What data are you interested in, and where do you want to send it?

[akbooer]

@perh said in Another transition from Vera to OpenLuup - PerH:

looking with lsof, i see it setting up a UDP port at some arbitrary number that's changing on service restart..

That's par for the course if the system is allocating a (high-numbered) anonymous port from which to send UDP datagrams.

[PerH]

Sounds good, i'll stop worrying then.

Collectd has som more options for system logging than (i know of from) openluup/veraflux, so i want to send that to the influxdb. Same host on both, the chromebox.
its supposed to send on the default collectd port, 25826? and its defined in collectd.conf..
Influx has that port up as LISTEN, that may be why? I don't see why it should need a port at all for localhost operations.

[akbooer]

Influx has a special configuration for UDP connections.
For me, the database is called "openLuup" (surprise!).
8089 appears to be the defined (default?) UDP port.

###
### Controls the listeners for InfluxDB line protocol data via UDP.
###

[[udp]]
enabled = true
bind-address = ":8089"
database = "openLuup"
retention-policy = ""

But I do note that collectd also has its own config:

###
### Controls one or many listeners for collectd data.
###

[[collectd]]
  # enabled = false
  # bind-address = ":25826"
  # database = "collectd"
  # retention-policy = ""

with 23826 as the default port.

There is quite a lot of configuration here, are you sure you have it all set up correctly?

Either way, it need a port to listen on, since the communication is done with UDP datagrams.

[PerH]

Not at all sure about that, no. It does however have a LISTEN on 25826, so by that i'm asuming that its waiting for input?

One disturbing thing is that influx will not start if i have the [[collectd]] header uncommented, not with one set of brackets either.

[PerH]

Really happy with the system, instant reactions and reliable, up until yesteraty evening. For some reason i lost the login of the Z-way bridge? On the z-way side, the connection is set to "No Expire", anything else i need to do?

[akbooer]

One of the problems of mixing issues in a single thread is that it makes it harder to find solutions.

However, have you searched and found this thread on your latest topic...

https://smarthome.community/topic/18/z-way-token-expiration

Does that help?

[PerH]

I see your point, will do better. didn't know it was called a "token", so i didnt find it.
I'll continue in that thread then.

[PerH]

After some hours of fiddling with my little breakdown, I finally got the Zigate plugin up and running. And its running well! the two aqara sensors i tried popped up and configured perfectly at first attempt.

I now have zigbee capability outside the vera, the last thing i need to power down the vera now is geofencing.

[PerH]

One new thing i discovered with the Zigate was that the Aqara temp sensors also report air pressure. A new Barometer definition followed the plugin.

MIOS doesn't have a device catergory for this, anyone here solve that issue? I can't make Imperihome show them without device categories..

Today AltUI gave a pop-up with the single word "Fail.", and my lisence isn't registered. I've recently changed to a new router, could that be related?

[therealdb]

@perh said in Another transition from Vera to OpenLuup - PerH:

MIOS doesn't have a device catergory for this, anyone here solve that issue? I can't make Imperihome show them without device categories..

Just use weather station. I have a couple of virtual devices and I’ll probably share them in the near future. Just a custom device Template with standard generic level sensor attached.

[rafale77]

@perh said in Another transition from Vera to OpenLuup - PerH:

MIOS doesn't have a device catergory for this, anyone here solve that issue? I can't make Imperihome show them without device categories..

I have long rolled my own pressure sensor/barometer category icon and type which vera doesn't support even at the command class level. Mine also is due to a zigbee device. Maybe I should push it to the ALTUI repo huh?

Today AltUI gave a pop-up with the single word "Fail.", and my lisence isn't registered. I've recently changed to a new router, could that be related?

It is possible. Unless you make it run on local cdn, ALTUI relies heavily on java libraries from the internet.

[PerH]

The lisence is ok again now, no idea why.

There was a barometer definition with the zigate plugin, mabye yours? Anyway it works well in altui. I'll try the weather station category.

[rafale77]

Definitely some weird stuff going on either on your network or in the web. When you get a chance to look at it, I would definitely recommend moving to local cdn. I pushed a bunch of updates to @amg0's repo on GitHub last week and he also updated their web version. You should see them on the next release.