Cover image

Lately I've been writing so much about GPT4All, synthetic monitoring and ProxySQL that this blog has drifted away from its original scope quite a bit. Let's return to roots for a while -- at least for this post, and see what's new on my home monitoring front. Or, not necessarily new, but details I have not shared with you earlier.

Remember the baby monitor

Our toddler sleeps her daily nap on our outside terrace in her comfy stroller if we are at home. It's a win-win situation -- she can sleep there without anyone disrupting her, she gets fresh air, and we can live our daily lives here at home without accidentally waking her up.

But, it's best not to forget the baby monitor so we hear when she wakes up. 

For that, the good old door sensors and about a predictable nap schedule does help.

Remember the baby monitor

The alert trigger itself is simple. I don't want the door to alert every time it's opened, but between the likely time window when the toddler falls asleep, yes. If there's a change in door status and time is between 11.40am-12.15pm, then remind us.

change(/Zabbix server/doorsensor.housekeepingroom.lastchange)<>0 and time()>=114000 and time()<=121500

Notice accidentally turned off outdoor lights

We have several Philips Hue lights lighting our terrace. As they are Philips Hue smart lights, our Cozify can control them based on our needs; but, if we flip the wall switch, then Cozify cannot control the lights anymore as the lights are then physically powered off. 

One light being unreachable could be just a broken light (has not happened yet), or a light that's dropped off from Zigbee network. However, if all the lights are reporting that they are offline, somethings wrong. For that, I have this alert.

Cozify: Outdoors lights power button off or fire probably tripped

 

max(/Zabbix server/reachability.sideterraceoutdoorlight1,30m)=0 and max(/Zabbix server/reachability.sideterraceoutdoorlight2,30m)=0 and max(/Zabbix server/reachability.sideterraceoutdoorlight3,30m)=0 and max(/Zabbix server/reachability.frontdooroutdoorlight1,30m)=0 and max(/Zabbix server/reachability.frontdooroutdoorlight2,30m)=0 and max(/Zabbix server/reachability.frontdooroutdoorlight3,30m)=0

In other words, alert if all the lights have been unreachable for 30 minutes or more.

Monitor my facial cream usage monitoring

Remember how I monitor my facial cream usage

Imagine the P1 bridgeworthy situation where the box door sensor would not work and an alert would get through for no reason. NOOOOOOOO! 

For that, Zabbix monitors the door sensor battery level and if remains low for more than one day (these things can report values in weird ways), time to react before it's too late.

Facial cream box sensor battery getting low

 

For that, my alert trigger is very simple.

max(/Zabbix server/battery.facialcreambox.voltage,1d)<=2.5

... though all kidding aside, my facial cream SLA % is outright terrible. See it for yourself, this is from the beginning for this year.

Facial cream monitoring SLA

 

 

 




Add new comment

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
Submitted by whatsuphome on