Bugs, or shortcoming, and I can't be sure where exactly they are, as my device is currently not accessible as a resulf of one of the issues.
Trying to get a 3EM up and working to monitor what's being used as a precursor to a possible solar panel install.
Initial set up didn't go well, as the Shelly cloud app on android kept crashing as it tried to transfer the AP to the WiFi. One of the annoyances is that it's not possible to paste the user ID and Password into the app, from something like a password manager, which is a complete PAIN at this stage.
Part of the problem was a very weak WIFI signal, so that got resolved by adding a repeater in the immediate area, but that still didn't resolve the app crash, but eventually, I managed to get into the device using the browser on the phone, and the web interface, but it wasn't easy;
That got the device going, and I was then able to connect it to the WiFi, so I could then see it from the windows Laptop, which made working with it a bit easier, in that at least I had a sensible size keyboard and screen to work with. A few minutes later, it threw up a pop up that there was a firmware update available, and did I want to install it, so I let it go at it.
Bad move, in that the device never came out of "updating", not at all, and in the end, I gave up waiting. The next morning it still wasn't working, and to add to the aggravation, the reset option from the front button was ignored, so at that stage, I knew that the firmware update had not completed correctly. Due to the way was wired in there was not an easy way to disconnect the power from the device, so I had to wait until I could pull the main power fuses and power the device down. The wiring has now been changed so that if something like this happens again, a plug and socket connection close to the device can be safely opened while live to power it down without affecting the rest of the system.
The power down recovered it, and I was able to get back in again to restart the changes I wanted to make, such as getting the date and time right, changing the sensor names, and putting in a password to protect my network.
That didn't go well. there are issues with the combination of the device web browser, WIndows 10 and Firefox on a laptop when using the web browser, and the shelly app on android didn't appear to have access to some of the things that I wanted to change. When I went to change the date and time., I couldn't complete that, as the mouse wasn't working, so it wasn't possible to scroll down far enough to be able to make the changes, and then tell the software to update, and I found that out by closing out of Firefox, and trying Chrome instead, which worked, and I also discovered a number of additional menu items that were not appearing at all on Firefox.
Among other things, I then changed the device password, and in theory, the browser should have saved the (complex) password that was generated, but for reasons that remain unknown, the browser locked up, and didn't save the password, but it had at that point updated the device, I wasn't worried as such, in that the password had been pasted from the keyboard buffer into the relevant field, so it should still have been available for another Ctrl V paste into a different app, but it wasn't, and the browser didn't offer the option to save the user ID and password either.
Big problem, as I can't remember 12 character complex passwords, that's why I use a password manager package, any other time I've done similar, which I do all the time, the browser provides an option to update my password manager, and once that's done, I have access to the password on the laptop and my android device. In this case, the password was lost, and to then compound the problem, a factory reset of the device does NOT remove a password from the memory, so that effectively means a bricked device. I've not had a device for a very long time where a factory reset doesn't clear this sort of data, along with things like the WiFi details, so the inability to get back into this device came as an unpleasant discovery, and it looks like the only fix is to return the device to Shelly, and let them do a serial flash of the memory using the manufacturing interface.
What's clear, and I've been around computers of one sort or another for over 50 years, the software on the Shelly devices is tender. It might well be out of Beta, but only just, and the rough edges are still showing in some areas, and that situation is not at all helped by Microsoft and Mozilla making a moveable feast of their respective packages, there's no such thing as a stable operating system or browser any more, they change from day to day, so while I'm not exactly impressed by what Shelly have put out, I can also understand that QA on the software is not easy any more, and what works today could very easily be broken by a patch or new version of a browser in literally hours.
I'm in no rush right now, in that my 3EM has to make a round trip from Ireland to Sofia and back, and it took 2 weeks to get here, so it's likely to be the the middle of June before I can pick this project up again, and who knows how many changes there will be in that time.
What's a significant change is that I'm going to have to treat this device with a lot more paranoia than I have for a very long time, and it's going to mean literally one step at a time, with backups of everything before even exiting from the routines, and additional copies in other places of every piece of data that goes into this device before it even goes into the device, and that's before I go near trying to make it work with Home Assistant, which is what I was hoping to be doing at the moment.
If I'd known it was going to be this stressful, I perhaps should have waited for the Electric network provider to install a new smart meter, which is going to happen at some stage, it certainly would have been easier., I wasn't aware of just how fragile these devices are at the moment. I am hoping to use other devices going forward, but the experience with this one and some of the comments here is giving me pause for thought.