Thanks, MQTT is rather universal and I have other personal code that publishes to MQTT which is picked up by the shellies.
The thing is ...before ... Shelly supported access between their app and shelly devices on the same Wifi without activating the cloud. That has been disabled which is a shame.
I don' know where Shelly store there cloud servers .. another app to delete from the phone.
Cheers
Shelly app used to work locally ... meaning with non-cloud enabled devices.
When will it be re-enabled ?
PS: I use MQTT which disables cloud
I have 10 shellies configured on one shelly account with cloud service enabled.
I understood that each shelly can only be assigned to one account which is fine as I want to transfer the shellies to a new account without going through the full factory reset.
Do I just select each device within the first account and delete them so I can register the devices to the new account? Will the shelly configuration be preserved ie IP address, actions etc.
Thanks for confirming
The lastest binaries are entitled tasmota.bin version 8.1.0. Once it's flashed the shelly will create a new wifi access point on ssid "shelly-xxxx", you'll need to connect to that wifi to configure your house wifi/password in tasmota of the shelly.
Personally, I flashed some initial shelly devices with tasmota (which is absolutely brilliant) but then stopped once shelly supported mqtt and provided continuous software updates with new interesting features (eg DDD actions). Through mqtt my shellies are made accessible to homebridge, so I benefit of both "worlds". Activating mqtt deactivates some shelly cloud features but I don't use it, I use the Apple home app for remote access to homebridge.
I don't think the flashing process is reversible ie replace tasmota by shelly binaries, which is another reason why I left shelly firmware.
