Thanks a bunch! That seems to have squashed them all.
1 Like
Glad to hear it! Let me know if something creeps back in. There may still be incorrect null values being sent from the child device to the parent, so if something doesn’t turn on/off as expected, do tell me and I’ll see about what to do from the child device. Something undocumented has changed in the platform.
New version uploaded. I’ve added even more checks, let’s see how this goes. I think there’s still issues on the child device side.
EDIT:
I’ve also made a change to the child device drivers for “Tasmota - Universal Bulb/Light (Child)”. Please update.
I’m not using the Bulb driver. I’m using the Universal Plug/Outlet.
Also, I noticed the Universal Parent was updated 29 minutes ago. Should I also update that?
I’ll update that one as well within a few minutes. updated!
yes
1 Like
Thanks, all good so far. 3 hours of no errors.
1 Like
Don’t be sorry, I do want to find the reason behind this, the change in the system is not one I’m 100% sure about yet, it affects many parts of the code since directly checking for null seems to be broken. A new version of the parent driver is available.
Still errors. No more descriptive than the previous error image.
I’m surprised no one else is experiencing these errors???
That is a very strange line to have issues on, it is literary a check to see if it’s an ok value:
if (getDeviceDataByName("port")) {
I’ll add a try catch to componentOn and componentOff, I avoid them since when they are used all Groovy optimizations are turned off for any code inside that section. I can’t upload anything at the moment, but I’ll try to do it later today.
@Mike please try the new version of the Universal Parent. There is now a try-catch around all code in componentOn and componentOff.
Thanks, I’ve updated and had no errors overnight.
I noticed (using the import feature in HE) that the version number for the Universal Parent didnt update last time, but I assumed the code itself did. This time (late last night) the version updated from 1212? to 1214Tb so maybe something got messed there. Shrug.
This is beyond weird, what version of hub do you have? C4? C5? Do you use any other devices with Component children?
C-5.
I have 7 tasmota devices in total, all with component children. None of the others seem to have errors, but they dont get turned on/off that often. This particular wall switch is one of the switches that doesnt have hue bulbs on the other end, so it does get turned on/off often. It’s a bathroom.
If it’s not too much work, would you mind trying to remove the parent and child devices for the bathroom switch and then install them in HE anew? Just want to rule out at least something before going further with this.
OK, I’ve done it, and I’ll keep an eye on any errors.
Edit: Strangely, I can not edit the name of #3 child device. It just wont save. It took a few saves to get some other child devices to stick.
Yes, still getting errors. Would it be worth it re-flashing Tasmota webhooks?
If so, which one?