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

**URL:** <https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [February 25, 2025, 6:12am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546 "2025-02-25T06:12:26Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 6:12am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/1 "2025-02-25T06:12:26Z")

</div>

Setup and collect telemetry in minutes!

The [TelemetryCollector App](https://homey.app/de-ch/app/org.cflat-inc.telemetryCollector) 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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/8/68db75c3f142d460fc5b2d25b1f0bfb03e4e600c.png)

## Good to know

The Homey-App establishes the connection to the app via the [TelemetryCollector-Api](https://community.homey.app/t/131548), 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

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

#### 🔹 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](https://cFlat-inc.org), Chris Gross

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 6:12am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/2 "2025-02-25T06:12:47Z")

</div>

1. For later use

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 6:12am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/3 "2025-02-25T06:12:56Z")

</div>

1. For later use

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 6:13am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/4 "2025-02-25T06:13:04Z")

</div>

1. For later use

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 8:13am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/5 "2025-02-25T08:13:50Z")

</div>

### [v1.0.0 is on Test](https://homey.app/de-ch/app/org.cflat-inc.telemetryCollector/Telemetry-Collector/test/)

> - Final version

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 9:28am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/6 "2025-02-25T09:28:19Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 25, 2025, 9:43am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/7 "2025-02-25T09:43:39Z")

</div>

### [v1.0.2 is on Test](https://homey.app/de-ch/app/org.cflat-inc.telemetryCollector/Telemetry-Collector/test/)

> - SyslogAdapter crash fixed

---

<div class="post-metadata">

**Author:** ![Kim\_Kokholm](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kim_kokholm/32/91519_2.png) [@Kim\_Kokholm](https://community.homey.app/u/Kim_Kokholm)\
**Post date:** [February 28, 2025, 2:09pm UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/8 "2025-02-28T14:09:39Z")

</div>

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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/0/409830828f22c8c3b50429c42149c19518ccb52c.png)

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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/3/73ddeab8df0add9bef57466084dce3eb3f38652b.png)

Sorry, I’m such a noob.

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [February 28, 2025, 4:25pm UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/9 "2025-02-28T16:25:26Z")

</div>

> [@Kim\_Kokholm](#):
>
> Do you have a guide how to check my Loki-instance for data and maybe how to visualize the Loki values in Grafana maybe?

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

```auto
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.

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [March 1, 2025, 8:50am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/10 "2025-03-01T08:50:30Z")

</div>

### [v1.0.2 is Live](https://homey.app/de-ch/app/org.cflat-inc.telemetryCollector/Telemetry-Collector/)

> Sorry for the delay, but I had a Homey emergency yesterday !🤷‍♂️!

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [March 1, 2025, 9:38am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/11 "2025-03-01T09:38:53Z")

</div>

For all those who are interested, I have set up a [“Good to know”](https://community.homey.app/t/131548/2) section in the TelemetryCollector-Api.

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [March 3, 2025, 8:54am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/12 "2025-03-03T08:54:43Z")

</div>

### [v1.0.3 is Live](https://homey.app/de-ch/app/org.cflat-inc.telemetryCollector/Telemetry-Collector/)

> - Driver images replaced

---

<div class="post-metadata">

**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\
**Post date:** [July 30, 2026, 4:27pm UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/13 "2026-07-30T16:27:42Z")

</div>

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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/a/8a9eaebecedb17205a109e0c9d0e7a71f8cca346.png)

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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/b/4b8bbead8ca2db4ade5a6f0b1c376f4ca28f2445.png)

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

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [July 30, 2026, 5:52pm UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/14 "2026-07-30T17:52:20Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\
**Post date:** [July 30, 2026, 6:35pm UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/15 "2026-07-30T18:35:21Z")

</div>

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 🤦‍♂️

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.

---

<div class="post-metadata">

**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\
**Post date:** [July 31, 2026, 2:37am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/16 "2026-07-31T02:37:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [July 31, 2026, 6:41am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/17 "2026-07-31T06:41:23Z")

</div>

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](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/4/54e71796b607ed28357d67a58e9fe177667eefcf.png)

**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.

---

<div class="post-metadata">

**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\
**Post date:** [July 31, 2026, 8:53am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/18 "2026-07-31T08:53:37Z")

</div>

> [@Drako74](#):
>
> 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.

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.

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [July 31, 2026, 1:26pm UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/19 "2026-07-31T13:26:18Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Drako74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drako74/32/150506_2.png) [@Drako74](https://community.homey.app/u/Drako74)\
**Post date:** [August 4, 2026, 12:36am UTC](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546/20 "2026-08-04T00:36:07Z")

</div>

I have done some further testing and research, and I believe I have precisely located the problem. In the timestamp (which is correct format for date, hours, and minutes) there is a space after the “05” seconds, which should not be there. Then the seconds is repeated without the leading zero, which also should not be there.  
 ![2026-08-04_00-53-31](https://us1.discourse-cdn.com/flex025/uploads/athom/optimized/3X/8/9/89431d4b0fa55e502bf605a5f8171d946e3e587e_2_690x21.png)

I have checked this with the IETF web site for the timestamp format requirements for the SysLog protocol RFC 5424.

 ![2026-08-04_01-08-09](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/a/7affd28f83f0fb4c59e62c23eeceb0ed5fef7976.png)

Their examples clearly show no spaces allowed, and if fractions of a second are to be included, the whole seconds are not repeated, and the fractions of a second are to be contiguous with the preceding parts of the timestamp separated by a full stop.

 ![2026-08-04_00-54-49](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/c/bce1a7956cb89004fa74013d12e1398620ebbd73.png)

Referring back to your example from the Homey Dev Tools system timestamp, that also follows this same format of no spaces, and no repeating of the seconds to include fractions of a second:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/3/5371f63270f34f8f8f2e8ff0d544d523257453ca.png)

I also found another Homey App SysLog client, which I tested. That one got the timestamp correct, but had a bit of a wonky when it came to hostname, application, P.ID & M.ID… stuffing the time in to the hostname, and then stuffing everything else in to the log message.

![2026-08-04_00-56-30](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/c/4ca414b09873c2c50e74db84c5a791f0172de77a.png)

Another question regarding your app, about the log message field. What is all that additional data preceding the actual log message that was entered in to the Flow card? It sends the actual log entry way way off the edge of the viewable line, and is most frustrating when trying to automate log analysis.

[Next page](https://community.homey.app/t/app-pro-telemetrycollector-setup-and-collect-telemetry-in-minutes-v1-0-3/131546.md?page=2)