sfromis

FTR, **never** use tasmota-minimal.bin as the first flash of Tasmota. It depends on config data from previous Tasmota install, and will only work as an intermediary step going from one...

You cannot use .gz binaries for first install of Tasmota. The expectation is that a successfully flashed Tasmota should detect that it needs to create a new configuration, basically a...

The numeric processing done in Tasmota rules is never "unsigned long", but always single precision floating point, indeed leading to loss of precision with 7 decimal digits.

#11329 has a little bit of discussion of the commands, including this point: > Most commands can only be issued when no periodic (low power or regular) measurement is being...

I really don't think that the AM2301 module has any 433 MHz radio, just a sensor chip an a MCU to transform the sensor protocol to 1-wire for hookup to...

Same issue using this subscribe example copied [from the docs](https://tasmota.github.io/docs/MQTT/#subscribeunsubscribe). `Subscribe DnTemp, stat/other-device-topic/SENSOR, DS18B20.Temperature` Obviously with a topic matching a device having a DS18B20. Event not fired, but getting the...

I can confirm that my recreation of the issue also was trying to pick a sensor value from a long payload, the JSON text being approx 360 chars. ESP8266 build...

[JSON5](https://maxim-ui.readthedocs.io/en/latest/node_modules/json5/README.html) exists as a proposed unofficial extension to JSON, including support for hex data. But it seems to be a fork without mainstream acceptance, and not great for compatibility.

There is no bug. No patch is *necessary*. You are just using invalid JSON, and I'd call it an error to break compatibility with standard JSON. Sure, extending the format...

Hmmmm.... There may be two questions here. One is the focus on hex data in JSON being a syntax error which *should* fail, meaning that run 2 is "ok, but...