[APP][Pro] TelemetryCollector - Setup and collect telemetry in minutes! (v1.0.3)

Apps
,
1

Setup and collect telemetry in minutes!

The TelemetryCollector App captures logs and monitoring data, processes them and forwards them via the agent to the relevant Homey applications and/or observability servers.

Big pictures

image
image802×450 19.7 KB

Good to know

The Homey-App establishes the connection to the app via the TelemetryCollector-Api, so the developer of the app must integrate this into his app. This means that you have to contact him, preferably via the app topic, with the request to integrate it (the effort is about 10 minutes).

The TelemetryCollector App only provides the infrastructure.

Notes

:small_blue_diamond: Community first: Diagnostic-Reports which are not requested by me will be deleted automatically.

:small_blue_diamond: Forum-Topic: Since I don’t have a crystal ball, please give me the following information so that I can analyze the problem more precisely.

  • App version:
  • Homey version:
  • Homey model:

ToDo

  • Integrate OpenTelemetry > Logger Adapter
  • Integrate OpenTelemetry > Monitoring Adapter

Thanks

Special thanks to all for the help in testing the new version.

Disclaimer

Use at your own risk. I accept no responsibility for any damages caused by using this app.

Copyright

Copyright 2025 cFlat-inc.org, Chris Gross

2
  1. For later use
3
  1. For later use
4
  1. For later use
5

v1.0.0 is on Test

  • Final version
6

To the user who crashed the SyslogAdapter, please send me the Advanced Settings. So that I can test it, because the error does not appear for me.

THX Chris

7

v1.0.2 is on Test

  • SyslogAdapter crash fixed
8

Hi @ChrisG

Just found your app. I’ve installed a Loki docker-instance. I already have a grafana, and I’ve connected Loki to the Grafana.

I made a simple process in Homey, where I push a message to the Telemetry app of yours.
I’ve also edited the settings in Homey for my device:

image
image572×404 11.2 KB

Do you have a guide how to check my Loki-instance for data and maybe how to visualize the Loki values in Grafana maybe?

image
image571×187 11 KB

Sorry, I’m such a noob.

9

No, unfortunately not, I’m not yet ready to publish anything with a clear conscience.

But as a little tip, use “Grafana Alloy” in your stack. I run all my tests through it and it works more or less flawlessly.

loki.alloy

loki.source.api "loki" {
    http {
        listen_address = "0.0.0.0"
        listen_port = 3100
    }
    labels = { job = "loki", }

    relabel_rules = discovery.relabel.loki.rules
    forward_to = [loki.process.loki.receiver]
}

discovery.relabel "loki" {
    targets = []
}

loki.process "loki" {
    forward_to    = [loki.write.loki.receiver]
}

loki.write "loki" {
    endpoint {
        url = json_path(local.file.endpoints.content, ".logs.url")[0]
        // basic_auth {
        //     username = json_path(local.file.endpoints.content, ".logs.basicAuth.username")[0]
        //     password = json_path(local.file.endpoints.content, ".logs.basicAuth.password")[0]
        // }
    }
}

But maybe we have a Grafana crack in the community who can help us further.

10

v1.0.2 is Live

Sorry for the delay, but I had a Homey emergency yesterday !:man_shrugging:!

11

For all those who are interested, I have set up a “Good to know” section in the TelemetryCollector-Api.

12

v1.0.3 is Live

  • Driver images replaced
13

Hello,

First, can I say the app is very useful and works brilliantly for the most part.

I am having a bit of a problem with log timestamps though, when it pertains to daylight savings not being recognised/honoured. And it looks like the timestamp format being sent from the app doesn’t include a timezone offset possibly?

Here’s what I’m seeing in my SysLog server, with a comparison between my network hardware (which includes the +01:00 daylight savings timezone offset) and the output from the Telemetry Collector app on Homey Pro:

2026-07-30_17-14-28
2026-07-30_17-14-28622×674 60.6 KB

Would it be possible to either change the timestamp format to include the offset, or include a timestamp format option in the device Aadvanced settings:

IMG_7277
IMG_72771290×2796 188 KB

Thank you for your time, consideration and work on this app. It is greatly appreciated.

14

Hi Andy,

This isn’t an app issue, because your SyslogServer displays the (internal) UTC time; however, you need to configure it so that the WebUI displays the local time—then it should work.

Chris

15

Unfortunately I don’t think there is an option for that in the QNAP SysLog server. Perhaps I’ll have to look in to setting up a separate SysLog server on one of my Raspberry Pi’s to accomplish that :man_facepalming:

All my other log sources show the +01:00 during DST and consequently display the correct time. It’s only entries from Homey that are an hour out.

16

I’ve done some research on this, I’m pretty sure I was correct with my request in the first place to be able to include the time zone. You see, I do not live in the UTC time zone, and my Homey Pro is not submitting logs from the UTC time zone. My Homey Pro and I are in the BST time zone, which is UTC +01:00. So for 6 months of the year we’re in GMT (= UTC) and the logs will show the correct time. But for the other 6 months of the year we’re in BST, which is 1 hour ahead, and all my logging from Homey (at least from the TC app, as Homey itself is fully aware of Daylight Savings Time, so automatically adjusts to the correct time) is 1 hour out. And my log analysis goes out the window.

Would it please be possible to include a setting to use Homey’s locale specific time zone, for those that prefer, instead of UTC. (I mean I would rather just abolish Daylight Savings Time altogether, as it’s stupid, outdated, and a repeated headache… but I can’t see the government agreeing to that ha ha.)

Additional: referring to my original screenshot, if you are only following ISO 8601 and refuse to add a client time zone, the ISO 8601 format does not allow spaces as is seen in my screenshot. The correct format would be:

ISO 8601 - yyyy-mm-ddThh:mm:ss.sssZ

2026-07-30T19:00:00.016Z

The space invalidates the Z and therefore isn’t UTC.

17

Sorry Andi, but I won’t do that, because UTC is a globally recognized time standard used by 99.99% of servers worldwide. Homey also uses UTC internally and automatically converts it to the respective time zone (including daylight saving time) when displaying the time. (By the way, my app also uses Homey’s time.)

see: tools.developer.homey.app/tools/system

image
image593×309 13.1 KB

If your app doesn’t do this, then that’s where the error lies.

By the way: You mentioned in your first post that you’re using a QNAP server—check the settings to make sure the correct time zone is specified.

18

Checking to confirm that my QNAP NAS and Homey both have the correct time zone and DST configuration was the first thing I did when I saw the problem.

19

Why don’t you ask on the QNAP forum? Maybe someone there will have an idea on how to solve the problem.