templogger | power Micropython MQTT temperature logger

by aequitas Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | templogger Summary

templogger is a Python library typically used in Internet of Things (IoT), Arduino applications. templogger has no bugs, it has no vulnerabilities and it has low support. However templogger build file is not available. You can download it from GitHub.

Low-power Micropython MQTT temperature logger for DS18B20 and ESP8266 (Banggood ESP12E) running on 18650 Lipo.

Support

Quality

Security

License

Reuse

Support

templogger has a low active ecosystem.

It has 6 star(s) with 1 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

templogger has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of templogger is current.

Quality

templogger has 0 bugs and 0 code smells.

Security

templogger has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

templogger code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

templogger does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

templogger releases are not available. You will need to build from source code and install.

templogger has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

It has 101 lines of code, 7 functions and 3 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed templogger and discovered the below as its top functions. This is intended to give you an instant insight into templogger implemented functionality, and help decide if they suit your requirements.

Print sensor temperatures in MQTT format
Send values to broker
Wait for the WLAN to connect
Return a dictionary of all romors
Sleep the machine
Reads the voltage
Convert rom to hex

Get all kandi verified functions for this library.

templogger Key Features

No Key Features are available at this moment for templogger.

templogger Examples and Code Snippets

No Code Snippets are available at this moment for templogger.

Community Discussions

Trending Discussions on templogger

Why procduces my two identical systemctl timers different amount of outputs?

Connection test and loop in case of lost connection to prevent end of script

QUESTION

Why procduces my two identical systemctl timers different amount of outputs?

Asked 2021-Sep-22 at 23:45

I have two raspberry pi with almost identical setup. On both I have a systemctl service and a timer which run every 15 seconds. The job calls a go script, which reads out the system temperature and creates a log entry in my mariadb database. The database is running on one of the raspberries. Therefore the only difference in the two go scripts are the hostname of the database and an identifier variable so I can see in the database from which the database entry is coming from. The rest is identical.

The problem is that raspberry1 produces more database entries than raspberry2. When I start with a fresh database with zero entries. Then 1 have about 120 entries from raspberry1 and about 70 entries from raspberrie two. The error continues. After more time I get for example 1000 entries and 700 entries.

Does anyone know where the differences could coming from? Maybe when both jobs want to create a new entry in the mariadb at the same time? But I'm almost sure that this is handled somehow by mariadb.

Here are the details:

FanLog.service

...

ANSWER

Answered 2021-Sep-22 at 23:45

I have found the solution:

One of these two options made it work:

Source https://stackoverflow.com/questions/69249216

QUESTION

Connection test and loop in case of lost connection to prevent end of script

Asked 2020-Oct-15 at 22:34

I have this script that runs continuously on a raspbery Zero to capture the temperatures and send them to grafana the problem is that when the grafana server is stopped for backup or something, the script falls in error and does not automatically resume so I’m looking for a way to create a connection test loop prealable to sending data and if the grafana server is off-service the continuous script worked until the grafana server was up and running and therefore resumed sending the temperature data to the grafana server.

Because current I end up with the script in error with in the message requests.exceptions.ConnectionError: HTTPConnectionPool

To use script python templogger.py -db=influx_db_temperature -sn=temperature -rn=RUN

My script :

...

ANSWER

Answered 2020-Oct-15 at 22:34

Thank you @AbhinavMathur for forcing me to stay on adding a try-except because in the end it’s just that I wasn’t positioning correctly in the script

This is the modif allowing the script to not crash with a connection error.

Source https://stackoverflow.com/questions/64379849

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install templogger

Clone this repository using --recursive or update submodules git submodule update --init.
Micropython installed (tested with 1.8.6) https://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/intro.html#intro
Is configured for Wifi https://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/network_basics.html#configuration-of-the-wifi
Has Webrepl enabled https://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi
Has ADC switched to battery input (see below)

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: