Jason Posted August 16 Share Posted August 16 Hi I am trying to upgrade my Shelly Pro EM-50 to the latest firmware, I understand that it needs to upgrade to version 1.3.3 firstly, however when I check the logs it looks as though it is trying to get 1.4.2 without the intermediate step first. I have checked the logs and downloaded files from URL and they are tagged 1.4.2, can I manually download 1.3.3 to get to this point and then try the auto update? LOG {"id":1,"act_power":0.0,"aprt_power":4.9,"current":0.020,"freq":50.0,"pf":0.00,"voltage":241.2} 11:46:24 shelly_http_client.:302 0x3ffe4b60: WSS shelly-115-eu.shelly.cloud:6022/jrpc (CA shelly_cloud.pem) 11:46:25 shos_rpc_inst.c:230 shelly.checkforupdate via WS_in 10.8.0.10:55875 11:46:26 shelly_update.cpp:173 Checking for updates (1.1.99-proem50prod1 20231113-130852/1.1.99-proem50prod1-g1290cf8 {"bl":263173,"ut":2214645174,"hf":118836,"hmf":108424,"fsf":188416}) 11:46:26 shelly_http_client.:302 0x3ffe52f4: HTTPS GET https://updates.shelly.cloud/update/ProEM (CA shelly_cloud.pem) 11:46:26 shelly_http_client.:606 0x3ffe4b60: Finished; bytes 0, code 0, redir 0/3, auth 0, status -10: Host not found 11:46:32 shelly_http_client.:606 0x3ffe52f4: Finished; bytes 0, code 0, redir 0/3, auth 0, status -10: Host not found 11:46:32 shelly_update.cpp:199 Check for updates received bad response: -10: Host not found Here is an extract from my log. Many Thanks Jason Quote Link to comment Share on other sites More sharing options...
tvbshelly Posted August 16 Share Posted August 16 "Host not found" looks like a DNS problem. It may help to restart the router and/or the shelly. Quote Link to comment Share on other sites More sharing options...
tvbshelly Posted August 16 Share Posted August 16 36 minutes ago, Jason said: can I manually download 1.3.3 to get to this point Please contact support for help with the manual update if the DNS problem persists. Quote Link to comment Share on other sites More sharing options...
Jason Posted August 16 Author Share Posted August 16 2 minutes ago, tvbshelly said: "Host not found" looks like a DNS problem. It may help to restart the router and/or the shelly. Thank you for your answer, I have tried that, however if I manually add "https://updates.shelly.cloud/update/ProEM" to browser on same network it downloads the 1.4.2 package fine, that's what I find strange it is bypassing 1.3.3. Not sure if that is relevant or not> Jason Quote Link to comment Share on other sites More sharing options...
tvbshelly Posted August 16 Share Posted August 16 I understand, then DNS should actually work Quote Link to comment Share on other sites More sharing options...
Jason Posted August 16 Author Share Posted August 16 2 minutes ago, tvbshelly said: Please contact support for help with the manual update if the DNS problem persists. Sorry for the obvious question, what is the best way to contact Customer Support? Thank you Jason Quote Link to comment Share on other sites More sharing options...
tvbshelly Posted August 16 Share Posted August 16 https://allterco.freshdesk.com/de/support/tickets/new?ticket_form=report_an_issue Quote Link to comment Share on other sites More sharing options...
tvbshelly Posted August 16 Share Posted August 16 Comment: 1.4.0 is current stable (1.4.2-beta1 is current beta version) for Gen2/3 Quote Link to comment Share on other sites More sharing options...
Jason Posted August 16 Author Share Posted August 16 Thank you for you excellent suport. Jason 1 1 Quote Link to comment Share on other sites More sharing options...
tvbshelly Posted August 16 Share Posted August 16 7 minutes ago, Jason said: Thank you for you excellent suport. Jason Thanks for your kudos 🤠 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.