* Add files via upload
* Add files via upload
* Add files via upload
* Add files via upload
* Update en_GB.h
* Update xsns_100_ina3221.ino
* Add files via upload
* Add files via upload
I hope I have all details now changed ;-))
* Add files via upload
I still found a little detail to beutify ;-)
* Add support for pipsolar inverter
* Fix CI-Warnings
* Remove unneeded define
* Pipsolar: Fix dat result
* Add support for the rules engine
---------
Co-authored-by: Peter Rustler <peter@rustlerit.de>
* Multilingual fixes
Some fixes for a better user experience matching every language.
* Revert frag mem
Solved problem with regional decimal conversion in language file.
As the label of the upload button is concatenated at runtime, this does not match in all languages. To solve this, there is now a full label text for `Start upgrade` and `Start restore`.
* Restart MAX17043 from the scratch
* revert change
* Changed battery capacity in charge (capacity is the Ah value of the battery, this degrades over time when battery ages)
* merge
* Changing xsns_109 to 110
* fix nr
* removed old xsns109
* Update I2CDEVICES.md
* clean-up usage of Interface
* Added support for Dingtian Relay Board v3.6.10
* Output OE was never initialized
* Removed white spaces trying to fix language builds
* Fix for https://github.com/arendst/Tasmota/pull/18535#pullrequestreview-1406978097
* Fixed language builds
---------
Co-authored-by: JeroenSt <nospam@nospam.org>
* WIP Tuya MCU Bridge driver alternative to the TuyaMCU driver
The main difference is this driver does not try and wire MCU data points
(Dps) into the tasmota power/light/etc controls. Instead each Dp ends up
being relayed directly to MQTT and the rules subsystem. If you want to
change the state of something wired up to the MCU, you send tuyamcu
specific commands to manipulate the Dp.
Each Dp gets a type and id specific topic that is sent to MQTT. eg, Dp
id 1 type bool looks like tele/%topic%/TUYAMCUBOOL1. To change state you
send a TuyaMCUBool1 command (ie, the command index value is used as the
DpId, which is nice and symmetrical) with the new value.
Currently Rules operate on TuyaMCU#TypeDpid things, eg, "rule1 on
TuyaMCU#Bool1 do power %value% endon" toggle the power on the tasmota
device when the state of the thing on the MCU changes too.
The most obviously missing stuff at the moment is:
- better relaying of the wifi/mqtt status to the MCU
- handling wifi reset requests from the MCU
- low power stuff?
- support for sending status updates and device info queries.
- restarting the tuya mcu state machine?
- restarting the rx state machine when no bytes are rxed for a period of
time
- time sync
* shorten the log prefix to TYB (3 chars).
requested by arendst
* use the local definition for the SET_DP command.
reaching back to the existing tuyamcu code isnt reliable.
pointed out by arendst
* put the todo list in the code so it can be tracked
* check the wifi/mqtt state every second and update the mcu if it changes.
* fix rule processing when Dp state is changed from a cmnd.
rule processing was done as part of publishing the state, but publishing
the state when it was updated by a command only happened if So59 was
set. split rule processing out of publish and call them separately as
needed.
publish is now called from teleperiod, status updates from the MCU,
and from cmnds if so59 is set. rules are called from status updates from
the MCU and from cmnds.
Co-authored-by: David Gwynne <dlg@defeat.lan.animata.net>
Theo Arends
Barbudor
s-hadinger
fb-pilot
Jason2866
SteWers
chefpro
nusse
Vincent de Groot
Jeroen
Szewcson
Anton ACE
Fabrizio Amodio
David Gwynne