I created a new device using V1.3.1. Clicked on Children create. I think that fixed my issue. All the plugs are now listed under Gym Power Bar. I am happy with the fix. One small thing you could consider is the friendly name of the switch from Tasmota is not pulled by your code. I can manually replace the device label. Another minor change you could add is instead of Dual, Quad, and Eight relay versions groovy, the user can just set the number of plugs before clicking the "Children create" button you might be able to create the child plugs as per the user configuration with just one version of groovy for compound switches. RuleMachine can now see all the plugs as well. Please let me know if you have another code for me to test. Please note if you click on the "Children create" button again you will get the below error.
"Didn't create child devices for some reason: java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI"
Change it to a dual, click the button and change it back. I think that should do it. It's not an issue for a new install just those pre-existing installs.
P.S. The error won't do any hard but I agree it's undesireable.
Could add a simple line to initialize function, that checks for the useChildDevices flag and if it isnt set, then it creates it? Agreed its probably annoying, even if totally harmless!
I guess I didnt consider single device changes (though in my defence I didnt submit the changes to the single switch device so never tested it! Only did dual/quad/eight, but thats annoying to maintain!)
I'm not checking for a null (setting does not exist), perhaps that is it. I'll experiment and figure it out. If it is the null that it causing it I'll add it to the initialize per your suggestion.
I just updated to the v.1.3.1 driver and experiencing some issues with my Tasmota-flashed Sonoff S31 plugs. I have several of them and before the driver update, all four were functioning as I would expect. After the driver update however, two power statuses show up in Hubitat, Power and Power1. When I use the hubitat interface to turn the switch on or off, the devices turn on and off properly, but the Power status remains in one state. Hubitat sees Power1 is updated to reflect the status, but Power status never seems to change. As a result I don't see an accurate status of the device in Homebridge or HomeKit. If I use the web interface on the Tasmota device to turn it on or off, the Power status as well as the Power1 status seem to be in sync and work just fine.
I'm a total newbie when it comes to Tasmota, so I apologize if I've missed something obvious. I've re-run the Tasmota Inject command, and followed the instructions. Is there something obvious I'm missing? I've checked the Tasmota documentation here to see if there were any options I could set on the S31 itself and noted SetOption26 to use indexes when only one relay is present (which it is in my case). But it is set to 0, which was the default.
Just bumping this in hopes that someone has an older version of the driver. I checked Gary's github, but can't seem to find a single relay version around revision 1.2.5. Does anyone happen to have a copy?
Yes, something is definitely broken.
I had lost ability to turn on & off my Tasmota plug.
I remembered that @FriedCheese2006 edited the driver for some energy readings.
I have updated to the single plug driver and I can confirm that that plug is working properly again, I can turn it on and off again
Hmm, not sure about all the different drivers but I thought this was the single relay with PM that I am also using; this is version 1.2.4 and latest version is 1.3.1?
Tasmota Sync N Port Relay\Switch\Plug Driver with PM v1.2.4
Thanks, I did look through the history on github, but there were changes around that time by other contributors so I wasn't sure which was the recommended one. I'll try 1.2.4 and see how it works.
I have a 2-way light switch. I use "https://raw.githubusercontent.com/GaryMilne/Hubitat-Tasmota/main/Dual_Relay_Switch_Plug.groovy" device code. When the device is turned on/off physically the status doesn't change on the tasmota device in habitat hub until I manually press the refresh button (see screen shot) to get the change. This issue is affecting the webcore trigger I wrote to update the virtual switch to control my weird tasmota 2-way switch. Am I doing it right? Is there an easier way? If so, then can you share how I can turn my 3-way switch on or off? I know you are busy. I'll wait for your reply.
