Skip to content

Instantly share code, notes, and snippets.

View Lineflyer's full-sized avatar

Lineflyer Lineflyer

18 followers · 1 following
  • Duesseldorf, Germany
View GitHub Profile
@Lineflyer
Lineflyer / cgeodb.sh
Created March 20, 2017 09:30 — forked from pstorch/cgeodb.sh
Get sqlite file from android app via adb (non root), example for cgeo app
#!/bin/sh
adb -d shell "run-as cgeo.geocaching cp /data/data/cgeo.geocaching/databases/data /sdcard/cgeo.sqlite"
adb pull /sdcard/cgeo.sqlite
@Lineflyer
Lineflyer / searchresult_premium.htm
Created June 28, 2017 19:53
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js lt-ie10 lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
<!--[if IE 7]> <html class="no-js lt-ie10 lt-ie9 lt-ie8"> <![endif]-->
<!--[if IE 8]> <html class="no-js lt-ie10 lt-ie9"> <![endif]-->
<!--[if IE 9]> <html class="no-js lt-ie10"> <![endif]-->
<!--[if gt IE 9]><!-->
<html class="no-js">
<!--<![endif]-->
<head>
@Lineflyer
Lineflyer / cgeo_wip_explanation.txt
Last active February 17, 2019 11:57
Dear c:geo users,
you are now using a version of c:geo, which we had to release although some work is still in progress and some known bugs are not yet solved.
Let us explain why we had to do this:
In October 2018 Google changed their requirements for all apps on Google Play. Starting at that time all apps need to target a more recent version of Android, which shall
improve security and compatability. While this is a good thing in principle, it required quite some effort on our side to implement these changes and get c:geo basically working again.
That is also the reason, why you did not see any version updates since last October.
At this moment our small volunteer developer team is still in the progress of cleaning up the code and fixing regressions caused by this forced changes.
@Lineflyer
Lineflyer / tibber_API_pulse_verify.md
Last active August 22, 2023 13:43
Nutzung des Tibber API Explorer um korrekte Datenübertragung des Pulse-Gerätes zu prüfen

Prüfung Pulse-Funktionalität mittels Tibber API-Explorer

Einleitung

Diese kurze Anleitung beschreibt, wie man ohne Nutzung der Tibber-App prüfen kann, ob und welche Daten des Stromzählers der Tibber Pulse (Auslesegerät für den digitale Stromzähler) an die Tibber-Server übermittelt.

Dies kann aus mehreren Gründen vorteilhaft sein:

  • Die Tibber-App hat zeitweise Probleme in der Darstellung der Echtzeitdaten. Somit lässt in solchen Fällen nicht erkennen, ob das Problem in der App oder am heimischen Zähler bzw. Pulse liegt.
  • Während einer eventuell erforderlichen Feinjustierung des Pulse sieht man über die Echtzeitdaten im API schneller die Wirkung der Justierung.
  • Da über das API alle von Tibber unterstützten Werte abgerufen werden, kann man sehen ob und welche Daten vom jeweiligen Zähler unterstützt werden (z.b. Strom/Spannung pro Phase nicht bei jedem Zähler).
@Lineflyer
Lineflyer / nodered_tronity_example.md
Last active August 6, 2023 21:15
Node Red Flows for Tronity API

This is an example flow, which can be imported into Node Red. It utilizes an example of

  • Authorization towards the Tronity API
  • Request latest vehicle data
  • Request list of all charging session

Based on the documentation on https://app.tronity.tech/ and some unnamed examples of authentication flows found on the internet. It has been tested and is working (as of 06.08.2023).

Pleas note:

@Lineflyer
Lineflyer / flows.json
Last active November 19, 2023 11:13
NodeRed HiSense API
[
{
"id": "10f3a88c8dbdee8a",
"type": "http request",
"z": "66a999a67a9a1aec",
"name": "Get list of appliances",
"method": "GET",
"ret": "obj",
"paytoqs": "ignore",
"url": "https://api.connectlife.io/api/v1/appliance",