The issue turned out to be code that was incompatible with older versions of iOS16.2 (possibly iOS16.4 and below, but I don't have 16.4 here); relating to regex functions / patterns that only work with newer versions of iOS webkit.
Anyway ... the dev I was chatting with sent over a test firmware this morning which fixed the web UI issue on my setup. So hopefully the fix will appear in a future update.
For anyone running older iPhones / older iOS and reluctant to upgrade, just wait, the web UI will eventually work again!
Beiträge von disuye
-
-
I've been in touch with one of the Allterco / Shelly software engineers all afternoon today, and there is in fact an issue with the firmware which causes web UI problems in iOS 16.2 (< 16.4?) mobile browsers. Something to do with the scripting interface in the newer firmware?
Anyway, they are currently trying to determine the exact cause of the bug, and I'll report back once it gets figured out! -
Found a workaround in Home Assistant.
If a Shelly device is spamming out too much information (for whatever reason), it can clog up the HA History Graph and other UI elements.
So, in HA, you can add the a "refresh_interval" to the History Graph YAML, increasing the value to something larger than default (which seems to have been 1 second). I used 20 seconds, and no more UI issues.
Codetype: history-graph refresh_interval: 20 entities: - entity: sensor.shelly_switch_dog_blanket_power hours_to_show: 24 -
Could you update to IOS17 to get a double check?
I am reluctant to upgrade iOS simply for a webpage UI, because iOS upgrades usually bring along more problems! I just want to know what *magic technology* the current Shelly web UI is using, which cannot be rendered by a fairly new web browser. Security? JavaScript? Something else?
-
Yes, indeed.
OK. But in my case, I cannot view the Shelly Web UI using any iOS16 browser. Only a black screen appears.
-
At first, I have to amend my statement: The “black screen issue” is with iPadOS 15 - version 16 ist fine!
The issue results from some browser features, which are available from iPadOS 16 and upwards. All browsers are affected, cause the issue lies in the operating system. Due to the fact, my iPad Air couldn’t be updated to iPadOS 16, I had to buy a new one…
Sorry – now I am a confused – we should be able to view the current Shelly web UI using any iOS16 browser?
-
Why do I need iOS17 to view what is effectively a webpage? Not being sarcastic, just genuinely curious what has changed?
-
iOS 16.2 and also iOS 15.7 (on a backup device), both unable to view the Shelly web interface.
-
Title says it all. I used to be able to access the web interface of all my Shelly devices from my phone's browser (iOS Chrome / Firefox / Safari / whatever) – but now with the current firmware I can *only* access the web UI from a laptop.
Is this an intentional change or has something broken? Devices with older firmware (such as my RGBW dimmer) can still be accessed from a mobile browser. This is kind of a pain, keen to find out what's happened. Thanks!
EDIT: Solved...
RE: Unable to access web UI from mobile browser? -
Way back in an older firmware I seem to remember being able to define the interval of sensor measurement, i.e: check sensors every xx seconds.
I cannot seem to find this setting in the latest firmware?
I have an issue where two (of my 30+) devices are reporting data to Home Assistant 1x per second, which is far too fast. Any ideas how to reduce this interval? Tried the usual reset / reboot / update firmware. -
Are you unable to access the web interface from a computer and / or a mobile browser? I've had issues with mobile browsers, but no issue from a laptop.
-
Thanks for telling us, Dan! There must be some electromagnetic interference between the primary step-down converter and the powerLAN frequencies, which is fairly enough suppressed in a good Shelly. But there must be devices which do not fulfill the specs in total…
You’ll get an insight in the ‘guts’ of Shelly plus 2PM right here:
Thanks for the reply & info.
The original Shelly Plus 2PM I had installed was operating perfectly for over one year, but something happened in the last couple days to cause this failure.
As an aside, the Shelly was connected with devices on AC phase 1, my powerline was plugged into AC phase 2 (with a pump nearby running on AC phase 3). They all share common neutral / ground and only after isolating what I thought were the obvious leakage points (outdoor AC lighting ring, some old ACDC lighting transformers, maybe the pump was failing? etc. etc.) the root of powerline disconnection was sadly this Shelly.
I'm happy to send the Shelly back to the factory if you guys want to figure this out in more detail. It still operates as normal, only thanks to the powerline headache was I even made aware that a problem had appeared.
Cheers again,
Dan -
This is just an info dump which might help someone else:
I was recently struggling with a new / intermittent / eventually complete powerline ethernet/LAN failure in the pump room of my property. Long story short, after a day of isolation testing, for some reason my Shelly Plus 2PM was somehow the cause of the powerline instability. I swapped the unit out for a new one and the pump room powerline ethernet is now stable.
Not sure exactly what happened, I use several TPLink TL-PA7017P AV1000 powerline adapters around the property which I think use all three electrical cables (live, neutral, ground*)... and the way my Shelly was installed (& failed) there must have been some kind of 'leak' between live and neutral that caused the TPLink to immediately disconnect from the rest of the network.
Anyway, I'll investigate the faulty Plus 2PM unit this weekend – but in case anyone is searching this forum for 'powerline' related issues, try swapping out an otherwise perfectly functioning Shelly for another known good unit. Worked for me.
Cheers, Dan
p.s: *we have three phase AC power which also complicates powerline endpoint placement and fault tracing -
Indeed, a Shelly UNI may be powered with 26V DC. But the maximum current driven by each output of the UNI is 100mA. I assume the current needed by the solenoid will be higher. This must be objective of an investigation by measurement.
Many thanks for confirming! I'll investigate the solenoid further, the sticker on it says 12VAC and I think 15W, which I assume is the maximum rating.
My second option is installing the Uni inside the phone unit and use it to close the small momentary switch (bottom right in this photo). Triggering the switch would force the control module to provide the 12VAC necessary to activate the solenoid. -
Hi all – I'm looking to control a legacy gate solenoid hopefully with a Shelly Uni.
At the gate the existing control module has 26VDC power which I can tap into, and the existing control outputs a 12VAC signal to trigger the gate lock.
Will a Shelly Uni be able to output 12VAC, assuming it's being powered by 26VDC? Thanks!
-
Update for anyone reading this ... I installed a second microswitch into my gate motor housing which disengages when the gate is open, and connected that to the Shelly 1Plus switch input (and configured the switch input as 'detached') – so every time the gate is not 100% closed the Shelly input switch registers as 'open'.
Alternatively, there is an aux 220VAC output on my gate motor control PCB (for triggering a warning light whenever the gate is in motion), but this required some futzing around in Home Assistant with an incremental counter and some logic to determine if the gate was in the process of opening or closing; and it was not a 100% definite indicator of open or closed. Just moving or stationary
-
And for anyone else reading this thread, a typical Home Assistant entry in the configuration.yaml for parsing JSON / REST data would look like this:
Codesensor: - platform: rest resource: http://192.168.xxx.zzz/rpc/Shelly.GetStatus unit_of_measurement: "C" method: GET name: "Shelly Switch Device Temperature" value_template: "{{ value_json['switch:0']['temperature']['tC'] }}" force_update: true
And FWIW one way to make the JSON payload easier to read, paste everything here:
https://http//json.parser.online.fr/ -
Duh, I'm an idiot ... found it ... can grab a JSON of all data from here:
http://192.168.33.1/rpc/Shelly.GetStatus -
Hi everyone – I'd like to be able to monitor the Device Temp of my Shelly +1PM in Home Assistant.
I know the 'Shelly Scanner' app can get device temp info, and I'm looking at the API documentation (https://shelly-api-docs.shelly.cloud/gen2/Devices/ShellyPlus1PM) but the only reference I can see regarding Device Temp requires an MQTT connection (something I'd prefer to avoid using, for the time being).
So! How can I get realtime Device Temp info? Is it available as an RPC url? Thanks! -
Oh, that’s not really a bargain. Had the cheap Polish/Chinese contactors in mind while giving my guess…
lol such is life here in Portugal! Even the taxes here are taxed