This sounds like you may have some DB corruption. Saving a backup and doing a SOFT reset, NOT a full reset, could resolve that.
No, this issue is inside HE, data not being passed between child and parent properly. I’ll have to think about what else to add as checks and I’ll update the code again.
I’m still using the deprecated drivers and older firmware. Are there any real benefits to updating?
If everything works and you have the features you want, then no. If something breaks when you update HE or you need support for something not supported in an old version, then yes.
thanks markus.
I have a couple of questions.
I’ve done a manual install for a new device and ended up with a parent and child and all is working fine except it’s showing as being not present (using the generic driver - the switch turns on and off just fine though). Does presence not work for some things? (I’m using the latest 8.5.1 with http hooks firmware).
even though I’ve got all the presence stuff ticked in the device preferences. Clicked configure/refresh, reinstalled the device but still the same.
EDIT: Sorry rookie mistake above - forgot to set the rules from my IOT vlan!
Now I’m installing a second device (same type). I can’t seem to install it under the first universal parent that was created. Is this correct? So every device will end up with both a parent and a child then?
PS - Also what does the status column mean in the Tasmota device manager app? My devices are both showing timeout even though they are working.
EDIT : Same rookie mistake as above.
Markus,
Error was still occuring, but I’ve changed it to only turn on/off 1 of 3 lights, and the errors have ceased. Food for thought?
Yes. For some devices multiple children.
did you try a soft reset of HE and restore from backup?
Yes, still getting errors.
Looking for some advice from the community - specifically regarding Tasmota Device Manager and its ability to monitor device presence.
I recently segregated my network into a various VLANs. My Hubitat Hub sits on one and my Tasmota devices sit on another. Controlling the devices work fine - from HE dashboard or by pinging them from the Hubitat VLAN. However none of the devices are showing as present.
Anyone got any advice which firewall ports need to be opened to allow for the presence to work within Tasmota Device Manager / Device pages?
Thanks (more than happy to take this discussion offline as its a very specific question)
I don’t have any clue what port it is, but if I had to troubleshot a firewall/VLAN issue I’d start with the blocked log. If you know the source and target IP the log should tell you which ports are being blocked. Slowly open them to allow the needed traffic in/out. Just a thought while we wait for someone with more Tasmota experience to chime in.
Port 39501.
Hi !
Have question while waiting on Hibutat delivery.
Can I use Tasmota 9.1.0 version with HE.
Or only way is Tasmota HttpHook modified version ?
Yes you can. Markus’ version of the tasmota firmware is the same as the official version with a few slight changes made to enable the He to us an auto detect feature with the devices.
As long as the device state is ONLY changed from HE it will work, but if you have for example a device with a physical button or it’s a temperature sensor, that would not work since the updates are not pushed to HE.
As @gadget mentioned, port 39501 on HE must be accessible from the Tasmota device to send traffic to HE when it is not just reply to a command sent from HE.
If I missed a question in this thread, please ask it again 
Just to update this group, and hopefully useful to someone else with a similar setup…I had opened all ports between my two VLANs to get things working and still didn’t get any device variables updating from device to HE. When initiated from HE to device the variables updated (except presence) but not the other way. I had checked that there weren’t any firewall rules blocking…what eventually resolved it was updating this setting in the parent device:
Hi @markus
Any chance you going to release Tasmota 9.1 or 9.2 for HE, any reasons to upgrade as I am currently on 8.5.1
Does this integration support water/gas valve controllers? I didn’t see a driver for one.
I should, just not had the time, yet.
Unless you need specific features in there and you have no issues as it is, then no. No need.
Provided the device runs Tasmota, these work by using the Universal Plug/Outlet child device driver. It could easily be modified to have the appropriate capabilities if that is needed, but in general that should not be needed.
