Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
(i believe this is a bug; there is no mention of needing to re-create rules due to format/parse change in release notes... that i can see. If this is not a bug and should be in the discussion/support form, let me know and i'll close / re-post there)
Note: while drafting this, I was able to resovle the issue by downgrading to 9.4.0. If this is not a regression, let me know...
I recently upgraded the two devices in question to Tasmota 9.5.0. About a day later, I noticed that the two devices are listed in HA as unavailable. After quickly checking that the scheduled "announce yourself, please" message was being broadcast to all tasmotas over MQTT, I started looking at the rules on the device to see what's wrong.
Below is a snip from the console of one device. The same No valid JSON error is present on both devices in question.
That payload is valid JSON... and was accepted by an earlier version of Tasmota... so i think there has been a regression. In crafting the origional payload, I was very careful to not leave any quotes or similar that would need to be escaped when fed in as rule2.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
09:42:59.937 CMD: Grp 0, Cmnd 'STATUS', Idx 0, Len 0, Data ''
09:42:59.994 MQT: stat/my_ceiling_fan/STATUS0 = {"Status":{"Module":54,"DeviceName":"My Ceiling Fan","FriendlyName":["Fan","Light"],"Topic":"my_ceiling_fan","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0},"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Exception","Uptime":"0T00:42:59","StartupUTC":"2021-07-18T16:00:00","Sleep":50,"CfgHolder":4617,"BootCount":175,"BCResetTime":"2021-02-10T03:41:55","SaveCount":586,"SaveAddress":"F7000"},"StatusFWR":{"Version":"9.5.0(tasmota)","BuildDateTime":"2021-06-17T08:26:35","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"482/699"},"StatusLOG":{"SerialLog":0,"WebLog":4,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["MyWiFiNameHere",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00028009","2805C8000100060000005A0A000000000000","00000288","0000E000","00000000"]},"StatusMEM":{"ProgramSize":607,"Free":396,"Heap":24,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540C8","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","00000020"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45","Sensors":"1,2,3,4,5,6"},"StatusNET":{"Hostname":"my_ceiling_fan-3274","IPAddress":"192.168.133.191","Gateway":"192.168.133.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.133.2","Mac":"DE:AD:BE:EF:BA:BE","Webserver":2,"WifiConfig":4,"WifiPower":17.0},"StatusMQT":{"MqttHost":"mqtt.lan","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_EFBABE","MqttUser":"tasmota","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4},"StatusTIM":{"UTC":"2021-07-18T16:42:59","Local":"2021-07-18T09:42:59","StartDST":"2021-04-11T02:00:00","EndDST":"2021-11-06T02:00:00","Timezone":99,"Sunrise":"21:06","Sunset":"12:45"},"StatusSNS":{"Time":"2021-07-18T09:42:59"},"StatusSTS":{"Time":"2021-07-18T09:42:59","Uptime":"0T00:42:59","UptimeSec":2579,"Heap":23,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"ON","POWER2":"OFF","Dimmer":100,"Fade":"OFF","Speed":1,"LedTable":"OFF","Wifi":{"AP":1,"SSId":"MyWiFiNameHere","BSSId":"AA:BB:CC:DD:EE:FF","Channel":6,"Mode":"11n","RSSI":100,"Signal":-48,"LinkCount":1,"Downtime":"0T00:00:04"}},"StatusSTK":{"Exception":28,"Reason":"Exception","EPC":["4024f5d6","00000000","00000000"],"EXCVADDR":"00000078","DEPC":"00000000","CallChain":["40250789","4024fd62","40250699","40250197","402507c4","4024fd62","4028e9e1","4024fd62","4028e9e1","4024f501","4024fd62","4024ff4c","4024f501","4024f544","40101baa","4024f5c8","4024578a","40282884","40245add","40100a50","4024f5b8","40282884","40245b9c","40207eac","40202ef3","40101b73","401018eb","40282884","4022d765","40245b35","40282a55"]}}
- [X] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
See above in problem description
TO REPRODUCE
Steps to reproduce the behavior:
Flash a TreatLife DS03 to the tasmota release 9.4.0
Configure the DS03 according to procedure outlined here
confirm expected behavior by issuing so19 0 command to trigger the rule; observe the tasmota device publishing a JSON payload to the topic / Home Assitant automatically configures the device.
update device to Tasmota 9.5.0
observe that the rule to publish the autoconfig payload is nolonger firing because of the No valid JSON message.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I would expect behavior to be the same was it was on earlier releases; the auto configuration payload fires off / there is no error about the rule not having valid JSON:
Note: I obtained the above console output by downgrading one of the affected devices to 9.4.0 after I had started drafting this post; I believe the is a confirmed regression, then!
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
PROBLEM DESCRIPTION
(i believe this is a bug; there is no mention of needing to re-create rules due to format/parse change in release notes... that i can see. If this is not a bug and should be in the discussion/support form, let me know and i'll close / re-post there)
Note: while drafting this, I was able to resovle the issue by downgrading to 9.4.0. If this is not a regression, let me know...
I rely on rules to fill in some of the gaps in Home Assistant Discovery.
I recently upgraded the two devices in question to Tasmota 9.5.0. About a day later, I noticed that the two devices are listed in HA as
unavailable
. After quickly checking that the scheduled "announce yourself, please" message was being broadcast to all tasmotas over MQTT, I started looking at the rules on the device to see what's wrong.Below is a snip from the console of one device. The same
No valid JSON
error is present on both devices in question.The original value for
rule2
:where
json_here
is a compact version of:That payload is valid JSON... and was accepted by an earlier version of Tasmota... so i think there has been a regression. In crafting the origional payload, I was very careful to not leave any quotes or similar that would need to be escaped when fed in as
rule2
.REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
tasmotizer.py
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
Steps to reproduce the behavior:
Flash a TreatLife DS03 to the tasmota release 9.4.0
Configure the DS03 according to procedure outlined here
confirm expected behavior by issuing
so19 0
command to trigger the rule; observe the tasmota device publishing a JSON payload to the topic / Home Assitant automatically configures the device.update device to Tasmota 9.5.0
observe that the rule to publish the autoconfig payload is nolonger firing because of the
No valid JSON
message.EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I would expect behavior to be the same was it was on earlier releases; the auto configuration payload fires off / there is no error about the rule not having valid JSON:
Note: I obtained the above console output by downgrading one of the affected devices to 9.4.0 after I had started drafting this post; I believe the is a confirmed regression, then!
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)