Hi again Markus,
I've done it severall times with no positive result. I think it's also in the logs: ..._refresh(metaConfig=null)
Sorry, saw that now, on the Tasmota device page, can you control the device there?
I can see it, yes, it's the Parent driver page, but I can't see the child objects, on, off, etc.
I mean on the Tasmota device webpage, go to the IP of the Tasmota device in your browser.
Yes, I can control it there.
What is the output of "Status 0" in the Tasmota device console?
12:28:09 CMD: Status 0
12:28:09 RSL: STATUS = {"Status":{"Module":0,"DeviceName":"ventilador del salón del sótano ","FriendlyName":["ventilador"],"Topic":"sonoff_mini_4","ButtonTopic":"0","Power":0,"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}}
12:28:09 RSL: STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://thehackbox.org/tasmota/release/tasmota.bin","RestartReason":"Software/System restart","Uptime":"0T00:12:54","StartupUTC":"2020-06-09T10:15:15","Sleep":50,"CfgHolder":4617,"BootCount":55,"BCResetTime":"2020-06-09T09:06:11","SaveCount":35215,"SaveAddress":"F9000"}}
12:28:09 RSL: STATUS2 = {"StatusFWR":{"Version":"8.3.1(tasmota-he)","BuildDateTime":"2020-05-20T22:27:21","Boot":31,"Core":"2_7_1","SDK":"2.2.2-dev(38a443e)","Hardware":"ESP8285","CR":"416/699"}}
12:28:09 RSL: STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["janica",""],"TelePeriod":300,"Resolution":"55C180C0","SetOption":["00008001","280514000100060000005A00000000000000","00000000","80000000"]}}
12:28:09 RSL: STATUS4 = {"StatusMEM":{"ProgramSize":581,"Free":420,"Heap":26,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"144051","FlashMode":3,"Features":["00000809","8F8AE797","043683A1","000000CD","010013C0","C000F0A1","00000024"],"Drivers":"1,2,3,4,5,6,8,9,10,16,18,19,20,21,22,24,25,26,30,35,37,95","Sensors":"1,2,3,4,5,6"}}
12:28:10 RSL: STATUS5 = {"StatusNET":{"Hostname":"sonoff_mini_4-1149","IPAddress":"192.168.20.113","Gateway":"192.168.20.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.20.1","Mac":"D8:F1:5B:8C:64:7D","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
12:28:10 RSL: STATUS7 = {"StatusTIM":{"UTC":"2020-06-09T10:28:10","Local":"2020-06-09T12:28:10","StartDST":"2020-03-29T02:00:00","EndDST":"2020-10-25T03:00:00","Timezone":"+02:00","Sunrise":"05:47","Sunset":"21:51"}}
12:28:10 RSL: STATUS10 = {"StatusSNS":{"Time":"2020-06-09T12:28:10","Switch1":"ON"}}
12:28:10 RSL: STATUS11 = {"StatusSTS":{"Time":"2020-06-09T12:28:10","Uptime":"0T00:12:55","UptimeSec":775,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"POWER":"OFF","Wifi":{"AP":1,"SSId":"janica","BSSId":"60:45:CB:B2:14:79","Channel":2,"RSSI":100,"Signal":-31,"LinkCount":1,"Downtime":"0T00:00:03"}}}
I would need you to run Refresh with debug logging turned on in the parent device, you should get a child device created when it looks like this.
Well, believe me or not, I did nothing different this time than the other ones I tried (I tried lots of times). This is the "magic" of technology 
, but hey! it did work now. Why? You're the deloper, you should know. 
Anyway, thank yoy very much for this incredible quick answer. This is the best technical assistance service I ever saw in my life, haha. Really appreciate it Markus, thank you!
Oh! In case you need the logs, here they are:
dev:25772020-06-09 12:36:30.372 info'switch' set to 'off'
dev:25762020-06-09 12:36:30.334 infoDevice info found: [hasEnergy:false, numTemperature:0, numHumidity:0, numPressure:0, numDistance:0, numSensorGroups:0, sensorMap:[:], numSwitch:1, isDimmer:false, isAddressable:false, isRGB:false, hasCT:false, hasFanControl:false]
dev:25772020-06-09 12:36:29.256 info'switch' set to 'off'
dev:25762020-06-09 12:36:28.631 infoCreated child device 'ventilador (1)' using driver 'Generic Component Switch'...
dev:25762020-06-09 12:36:28.565 infogetDriverVersion() = v1.0.2.0521T
dev:25762020-06-09 12:36:28.553 infotasmota_refresh(metaConfig=null)
dev:25772020-06-09 12:36:28.475 infoInstalled...
dev:25762020-06-09 12:36:28.409 warn'Tasmota - Universal Plug/Outlet (Child)' driver can't be found! Trying another driver: Generic Component Switch...
dev:25762020-06-09 12:36:28.267 infoDevice info found: [hasEnergy:false, numTemperature:0, numHumidity:0, numPressure:0, numDistance:0, numSensorGroups:0, sensorMap:[:], numSwitch:1, isDimmer:false, isAddressable:false, isRGB:false, hasCT:false, hasFanControl:false]
dev:25762020-06-09 12:36:28.170 warnMissing a child device, run the Refresh command from the device page!
dev:25762020-06-09 12:36:28.142 warnchildParse() can't FIND the device null! (childId: 2576-POWER1) Did you delete something?
dev:25762020-06-09 12:36:27.485 infogetDriverVersion() = v1.0.2.0521T
dev:25762020-06-09 12:36:27.474 infotasmota_refresh(metaConfig=null)
1 Like
For some reason the POWER part of the status message wasn't parsed correctly and the driver didn't see that there was a switch. Without the debug logs it is hard to know more about why.
Great it is working! 
Excuse me Markus, I'm still receiving this error when I press on Tasmota Device manager -> Configure Devices -> Result page:
Error: Could not find which method resultPage() to invoke from this list: public java.util.Map user_app_tasmota_Tasmota_Device_Manager_688#resultPage(java.lang.Object, java.lang.Object, java.lang.Object) public java.util.Map user_app_tasmota_Tasmota_Device_Manager_688#resultPage(java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object) public java.util.Map user_app_tasmota_Tasmota_Device_Manager_688#resultPage(java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object) public java.util.Map user_app_tasmota_Tasmota_Device_Manager_688#resultPage(java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object, java.lang.Object)
Any idea why am I receiving it?
Thanks again.
Which version of the hub firmware are you using? I'm not seeing this, this should be hidden using CSS since it is just a placeholder, and it is not, obviously. It has no function, it was never meant to be used.
2.2.1.115 I just updated this morning. I have no idea what could be the reason either.
Thanks anyway.
It is a change in the numbering of elements, I have a fix for it, it will be in the next release. Thank you for reporting.
I have info logging disabled in both of the parent devices, but I am still seeing these check in messages.
Can you have a look at it?
I learned recently that the check-in messages come from the child devices. Try turning logging off on those ones. It worked for me...
I had over 25 Power Management devices and even reducing the check-in time to 1 hour filled my logs... Turning the logging off on the child device what what I needed to do.
1 Like
I looked in my child devices and it doesn't have a "enable info logging" or anything like it. The only thing it has is: Enable descriptionText logging, and it is turned OFF.
Device 1990 and 1988 are child devices, right? Then those are the ones you have to disable the logging on, if that is not possible with the built-in driver, switch to one of my child device drivers.
I presume this is still best practice for Tasmota installs? I flashed my first 3 devices yesterday with Tasmota (not OTA, serial; but now they are only connected by wifi). They are Tasmota 8.3.1 They are currently integrated into HE by your amazing app. Great job and thankyou very much.
But I'd like to put on the highly recommended Hubitat enabled firmware. So flash the lite version, then reboot, then flash the tasmota-hubitat-v8.3.1.bin.gz, then press reset 5 (whatever that is).
You're welcome
Once you're on 8.3.1 you can use the bin.gz file directly, this is a feature of the very latest versions of Tasmota, which is why it doesn't work from 8.1.0 for example. You do need to run reset 5 when switching to my firmware, otherwise you might end up with some strange issues due to configuration data not being found where it is expected.
1 Like
