TriLife

Hi, you're close!
Replace "POWER" with "POWER1", ..2 ..3 .. 4. For each switch you're trying to control...
In case you need to controll ALL on/off, create a 5th device and use "POWER0".
I'm away from my computer right now. You might want to follow the instructions on lower/upper case for POWER... Tasmota doesn't care, but the MQTT plug-in might.

Good morning @TJF1960,
Couldn't keep @sjenkins away from his keyboard! THANKS!
There is a for STATUS on the Beta Store MQTT plug-in. Now V39. your PG3 should notify you. just update...
It also is on the Production Store, but since we didn't bump the rev, you might not get an update notice.
Please let us know how it goes.
 

Hi @EWhite,
In the meantime, I think I fixed the bug that requires a certain order. I tested it with "switch" front and back.
I just pushed the update to the beta store and installed it on my box from there. Still V0.0.31)
Can you please confirm?

SOLVED!
@xKing got back to me.
Once I migrated to PG3x on eISY and tried to look at it again, ANALOG showed up as a parameter on that device.
One thing to pay attention to: Tasmota only sends an ANALOG reading update via MQTT every so often (300seconds). It does however give real-time update on its WebUI.
Thanks @Geddy and @xKing
Cheers

Good news,
I'm up and running!
I had to update the Bios first, using SSH
@Michel Kohanimhad to remote in twice, first to fix a pointer to a shared folder, then again to restart UDX.
I was able to update my location with LAT/LONG to get an accurate sunrise/set.
PG3x and eISY worked waaay easier to get MQTT node server up and running. I just had to do the configuration within the node server and all is working. Google home gives voice commands, the Z-wave sensors provide information.
When I migrated the Z-wave devices from Zwave dongle 500 to eisy/Zmatter, most of them reconnected. I only had to sync/update-w-interview a couple of them to help them along.
With the MQTT PG3x Node Server even the analog readings of my Wemos D1 Mini started showing up. That was a problem on PG2.
The only thing I'm still struggling with is the Keypad of the ELK NS. Will get to the bottom of that too, I'm sure.
And, it seems that when using Admin Console/File/Set UserID/PW, it ONLY sets the userid of IoX and PG3x. The SSH credentials remain untouched. Maybe I understood that wrong. I'll have to set those within SSH, I'm guessing.
Thanks again to @Geddy and @Michel Kohanim for your help and patience, even on Memorial day weekend.
MUCH APPRECIATED.
 
Cheers
 

Update:
I contacted Homecontrols.com, from where I had bought the ELK M1. Through them, ELK did some trouble shooting and determined that the RS232 connection of the M1 was busted. Warranty.
I finally got the replacement yesterday, installed it and it worked!
Case closed! No need for DSC for now.