From 03e35b5d211342ecdfc7b0e63ecb22bd6221e557 Mon Sep 17 00:00:00 2001
From: s-hadinger <49731213+s-hadinger@users.noreply.github.com>
Date: Sun, 21 Nov 2021 21:11:47 +0100
Subject: [PATCH] read_sensors
---
docs/Berry.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/Berry.md b/docs/Berry.md
index 02b2856e98..ca9d4be8a9 100644
--- a/docs/Berry.md
+++ b/docs/Berry.md
@@ -370,6 +370,7 @@ tasmota.get\_option|`(index:int) ->
tasmota.wire\_scan|`(addr:int [, index:int]) -> wire instance or nil`
Scan both I^2^C buses for a device of address addr, optionally taking into account disabled devices via `I2CDevice`. Returns a `wire` object corresponding to the bus where the device is, or `nil` if device is not connected or disabled.
tasmota.i2c\_enabled|`(index:int) -> bool`
Returns true if the I^2^C module is enabled, see I^2^C page.
tasmota.arch|`() -> string`
Returns the name of the architecture. Currently can be `esp32`, `esp32s2`, `esp32s3`, `esp32c3`
+tasmota.read\_sensors|`([show_sensor:bool]) -> string`
Returns the value of sensors as a JSON string similar to the teleperiod. The response is a string, not a JSON object. The reason is that some sensors might produce invalid JSON. It's your code's responsibility to try parsing as JSON.
An optional boolean parameter (false by default) can be set to trigger a display of the new values (i.e. sends a FUNC_SHOW_SENSOR` event to drivers).
#### Functions to create custom Tasmota command