I jumped on a Discord server and asked around there, it turns out the latest firmware on the DS01 kinda plugged a hole that allowed TuyaConvert to work. It logs an ssl error.
It looks like soldering is the only option for the newer ones. I bet this is the new norm for TuyaConvert....
2 Likes
I've taken your kind advice and upgraded the Tasmota firmware on the bulbs to your HE specific version - much better now. Also, here's the link to the new entry for the bulb on blackadder's template site : Lohas ZN033 9W 810lm RGBCCT Bulb Template for Tasmota
Thanks again for your help.
cheers
2 Likes
I haven't had much luck with scanning for devices, nor it auto detecting the child drivers, but once I add the custom configs they've worked great. Might just be the random things I have used. I actually couldn't find the correct configs for one of my devices but I found a similar one and tweaked them to the device and they are working great.
Just love the local control vs the annoying smart life app.
Thanks for this!
This device has been added to the device list, it will be available in the next release.
For this to work Hue emulation needs to be turned on, this is done if you use my firmware and run "reset 5" after installing my firmware (as outlined in the instruction).
This requires the correct template to be set, either by selecting the device type from the dropdown, or setting the template manually. There is no way of nowing what device you have without doing that. As you say, once you have that done, it is all detected automatically.
1 Like
I read about the hue mode but it doesn't seem to be an option on my version. I used the digiblur method to install tasmota. But honestly I'm reserving IP addresses for the devices anyway, so the manual connection is easy enough. I've just been setting up the configs manually, easy enough, had to build a few custom ones for a couple of my devices before there wasn't one out there, but easy enough, well when I don't make a typo and end up going back and forth with it for 30 minutes trying to figure out why it won't stay on my wifi before I find the typo, lol.
If you use my firmware, Hue mode is there, not running "reset 5" after flashing can leave you with all kinds of strange issues down the road. It is a required step in order to avoid configuration corruption.
For devices not on the list, that is required.
That is recommended in either case, auto-detection of IPs is a convenience thing, but as you say, not a requirement.
1 Like
I missed that section of set up. I read the wiki as use one of these methods to install tasmota, I just used digiblur and then moved into the next section. I'll go back and redo the devices with the couple extra steps, only did 4 devices so far so not too bad.
I removed one from hubitat, then updated the firmware, that's on me for missing that step. Auto discovered as stated. Don't expect this one too get auto configured, it's but even on the bladder page well yet, I'm going to send it to him to add, lol.
Next one I'm going to try and update the firmware keeping the connection... See if that works, because the other two devices I already hooked up in my kids room and created rules for it.. but nothing crazy complex so I'll rebuild from scratch if needed.
It's my fault for trying something new while being distracted by the kids and dogs, lol.
Thanks for following up on my comment, otherwise I would have missed that!
1 Like
Even though I was signed up for the beta before this was released, I have had higher priority things to work on than worrying about my seventeen SP10s that have been running flawlessly with your old driver.
I have two hubs now with hubconnect running and I have been transitioning all wifi/lan/cloud devices to the new hub and leaving all zwave/zigbee on the original hub.
My devices are still on 8.1 so I know I need to upgrade them, but I transitioned my first three devices to the new hub today and used your new app/drivers.
Just have to say wow. Your work is awesome.
I did try a discover but it didn’t find any devices. Possible since I still had the connected to the old hub.
I deleted one device from the old hub, manually added the ip and that was it. Crazy simple.
So I just had to say nice job and thank you. I know when you first came on board and released your app you got some pushback of being an unknown and questioned if you would be in it for the long haul. I hope by now that there are no longer disbelievers. Lol.
I do have one question. I have a four MagicHome RGB strip controllers and would like to swap them out for a sonoff version. Would you be able to recommend a model or supply a link that is supported by your driver?
1 Like
Thank you, always happy to hear when it is appreciated
No, either you have them on a separate VLAN or you don't have Hue emulation on. Under any other circumstances they would discoverable. The default in my version of the firmware is for Hue emulation to be turned on, but that requires you to have run "reset 5" after flashing my firmware.
Those should be easily flashable with Tasmota over TTL. I have flashed a few, but don't use any of them right now, they're in a drawer waiting for possible future use. With that said, I prefer to use these types of controllers:
The only issue is that there are many similar looking ones with the pins in a different order, so you might have to fiddle with the Template settings, but that should be rather easy to sort out.
lol Yeah, there was some of that in the beginning.
2 Likes
Help again,
You are correct - I have Hue emulation turn off on them all. And I did read one of your previous replies stating that your discovery used Hue emulation. I forgot. And I didn’t understand previously that it was the reason for the reset after flashing new FW. When I start the upgrades to 8.3 I will do that.
I am really only using three of the magichome controllers and I have one as my ‘debug’ strip. I didn’t know that it was possible to upgrade these to Tasmota. Cool. I will give it a whirl.
And thanks for the link 
Well updating my 4 devices went without hitch... Didn't remove the other 3 and no issues keeping everything running and working as expected (just had to refresh for the config to sync from HE).
Only thing I had an issue with and it might not be a problem with the firmware or driver... But might be the local device. My wifi decided it wanted to die last night.. and was off for about 3 hours before I got up and noticed it and rebooted my router. 2 of my devices didn't reconnect to my WiFi... Just have to power cycle then and they connect right back up... But just wanted to mention this not sure if there's something you could suggest that might make one device not reconnect while others do? The 2 that don't reconnect are the same manufacturer and the ones that did are the same which is why it might be a hardware issue. They all are using custom configs as not listed as available hardware.
It is not the only reason, without doing "reset 5" you might end up with "garbage" data in the area of the flash where the config is stored. Safest is to just always do this when flashing a new Tasmota firmware.
If you have these types of wifi issues, you should look at setting both SSIDs and wifi keys to the same settings and run "wificonfig 4". This should resolve any issues like this, and keep them all reconnecting as soon as the wifi is back. Those that didn't reconnect right away probably would have a few minutes later.
2 Likes
Any idea how what driver I can use for this switch?
I have installed Tasmota and the template I'm using is here:
https://www.klaverstyn.com.au/david/wiki/index.php?title=Jinvoo_Smart_Switch_SM-SW102_with_Tasmota
It's same model number so I expect it's the same template.
Thanks
Actually, maybe the issue is the template. It exposes each button as a new device instead of having 1 device with 3 buttons. Since it controls a curtain, it should be up, down and pause buttons/switches (instead of 3 separate switches).
Yes, this would need some creativity, there is a Curtain child driver for Tasmota, but that one is for another type of curtain controller which has a secondary MCU. You could probably use a virtual curtain device and map it to the three child devices using RM. The other alternative is to figure out a better template and then write rules on the Tasmota device which could then be coupled with a custom child device (which you would have to write).
Thanks! Are the templates actually customizable? I'm not sure how I can get all 3 relays on 1 device (instead of 3 separate devices showing up)...
What's also interesting is that I can't enable Shutter mode in Tasmota. I wonder if the firmware disabled shutter mode.
I've not used the Shutter Support, but isn't that a 8.3.x feature? Which firmware are you on?
The templates are customizable, which devices are created by the driver depends on what is reported from Tasmota, if Tasmota reports 3 switches, three children will be created. If Tasmota can now report a shutter as a single device instead of multiple switches, the driver could detect that and I could possibly add support for that. If you can configure Tasmota to handle your 3 relays as a Shutter, tell me the configuration you set and I will see what I can do to make a child device that handles it as well.
Unfortunately, I can't even configure it as a shutter. It has to be enabled in the firmware (and I expect it's enabled in 8.3.1) but it doesn't appear to be enabled in your firmware. I'll try a different firmware (likely the regular latest Tasmota firmware) shortly just to see if that works. If it doesn't, then something else if the problem.
My 8.3.1 build has the same features (in this regard) as the official build.
Weird. I just flashed the official 8.3.1 build and the shutter mode is now working.
