Dimitar

I will ask are Gen2 is affected, we expect 1.7 beta for all devices, you can test it.

Something special on them, mean scripts, HA integrations or anything else ?

We can reproduce the problems as you report now. We fix 99% of them, but will take 2 more days before release a beta where we hope 100% will be solved. In between you can use latest dev-verison which shouls work very stable compare with previews one. It's only for Shelly 2PM Gen3 at the moment which is most effected device because the ram limitations. https://repo.shelly.cloud/shelly_files/fw/rojer/S2PMG3-127513.zip

There is a firmware which include Range Extender issue fix. https://repo.shelly.cloud/shelly_files/fw/rojer/S2PMG3-127513.zip

Can update them to 1.7.99 and tell is are the problem is solved there. You can also update from that link which is newer version: https://repo.shelly.cloud/shelly_files/fw/rojer/S2PMG3-127513.zip

We made on more improvment tonigh, will try to release new testing version until end of the day and publish it here for test.

You did't need RPC enabled, it's only if you want to contol device over BLE, but not for scanning, you can disable. Can you confirm that HA script still increasing temperature on firmware 1.6.2 ? Because we have bug at 1.5.0, but after 1.6.0 should not affect CPU temperature like that.

Are the CPU increasing temperature with firmware before 1.5.0 ?

If you did't disable BLE proxy for this device from HA, script will be re-enabled automatically.

Ok, please check now are there is a still connectivity issues or not, especially when script are stopped.

Hello Taym, can you disable BLE related scripts temporally and tell us are the device responding to the ping and did't lose the connection ?

If you have Deye Inverter can read data from Deye Cloud and make automation using Shelly Gen3/4/Pro devices. To use this script you need to have firmware 1.6+ (beta will be released at 12.April.2025, stable before 1.May.2025) Project link: https://github.com/kmetabg/Deye-inverter-via-cloud/tree/main More details:

Until we publish it here: https://shelly-api-docs.shelly.cloud/ you can use this API. It's not warranty that not be changed and some endpoints and examples my not work, but you can test and play without waiting to update the official one. You can check also: Generic methods Media.GetStatus Params Response Media.GetConfig Params Response Media.List Params Response Media.Delete Params Response Error Media.MediaPlayer.Play Params Response Error Media.MediaPlayer.Next Params Media.MediaPlayer.Previous Params Media.MediaPlayer.Pause Params Response Media.MediaPlayer.PlayOrPause Params Response Media.MediaPlayer.Stop Params Response Audio/Video-specific methods Media.MediaPlayer.PlayAudioClip Params Response Notes Radio-specific Methods Media.Radio.ListFavourites Params Response Media.Radio.PlayFavourite Params Response Media.Radio.PlayNextFavourite Media.Radio.PlayPreviousFavourite Media.Radio.Stop Params Generic methods Media.GetStatus Show the current Media status Params {} Response { "total_size": 781482, "total_size_h": "763.166 kB", "item_counts": { "audio": 1, "photo": 1, "video": 0 }, "playback": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Hidden Track", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 9927, "position": 2850 } } } Media.GetConfig Returns the current configuration of the Media Library. Params {} Response { "rev": 2 } Media.List List all uploaded media. Params {} Response { "list": [ { "id": 2, "filename": "14_-_Hidden_Track.mp3", "preview": "http://192.168.7.51:8021/getMediaThumb?id=2&_t=14_-_Hidden_Track.mp3", "track": 13, "artist": "Nevermore", "album": "Dreaming Neon Black", "year": 1999, "duration": 9927, "title": "Hidden Track", "size": 722714, "index": 0, "type": "AUDIO", "valid": true }, { "id": 1, "filename": "wally_1.png", "preview": "http://192.168.7.51:8021/getMediaThumb?id=1&_t=wally_1.png", "width": 1440, "height": 720, "title": "wally_1.png", "size": 58768, "index": 0, "type": "PHOTO", "valid": true } ] } Media.Delete Deletes a media item identified by its id Params id: ID of the media item to delete (required); { "id": 2 } Response The deleted field in the response is the same as the id provided in params. { "restart_required": false, "deleted": 2 } Error { "code": -114, "message": "Method Media.Delete failed: Could not find media item to delete with id 2" } Media.MediaPlayer.Play Plays a media file by its id from position 0 and continue with the rest of the playlist. If no id is provided, the last played item will be played from the start. If the player was last playing a radio stream and no id is provided, the same radio stream will start playing. Params id: the ID of the media item (optional); volume: The volume at which to play the media item, from 0 (muted) to 10 (max volume) (optional); { "id": 2, "volume": 8 } Response { "playback": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Hidden Track", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 9927, "position": 0 } } } Error { "code": -109, "message": "Method Media.MediaPlayer.Play failed: Media Item to play must be of type AUDIO. This one is PHOTO" } Media.MediaPlayer.Next Plays the next playable item in the list, audio, video or radio, depending on what was last being played. If the last item in the list was last playing, it will be played again. Params volume: the volume at which to play (0~10) (optional) { "volume": 4 } Response { "playback": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Hidden Track", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 9927, "position": 0 } } } Media.MediaPlayer.Previous Plays the previous playable item in the list, audio, video or radio, depending on what was last being played. If the first item in the list was last playing, it will be played again. Params volume: the volume at which to play (0~10) (optional) { "volume": 4 } Response { "playback": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Forever", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 160026, "position": 0 } } } Media.MediaPlayer.Pause Pauses the current playback. If the playback is already paused, resumes the current playback from the position it was paused Params {} Response Playback was currently playing { "playback": { "enable": false, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Forever", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 160026, "position": 7651 } } } Playback was previously paused { "playback": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Forever", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 160026, "position": 7930 } } } Media.MediaPlayer.PlayOrPause Plays the selected playable item, or pauses it. If no playable item is currently selected, MediaPlay will select the first item in the list. If playback was previously paused it will resume from the position it was paused at. Params {} Response Playback was not previously running { "playback": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Forever", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 160026, "position": 24527 } } } Playback was previously running { "playback": { "enable": false, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Forever", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 160026, "position": 28119 } } } Media.MediaPlayer.Stop Stops current playback. All consequent calls to Play or PlayOrPause will start playback from position 0. Params {} Response { "playback": { "enable": false, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Forever", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 0, "position": 0 } } } Audio/Video-specific methods Currently only AUDIO files are supported Media.MediaPlayer.PlayAudioClip Plays a media file by its id. If a playback is currently running, it will be paused, the audio clip will be played with the specified volume and, when finished, the previous playback will be resumed from the paused position and the playback volume will be restored. Params id: the ID of the media item (required); volume: The volume at which to play the media item, from 0 (muted) to 10 (max volume) (optional); { "id": 2, "volume": 8 } Response { "audio_clip": { "enable": true, "buffering": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Hidden Track", "artist": "Nevermore", "album": "Dreaming Neon Black", "duration": 9927, "position": 0 } }, "resume": { "enable": false, "volume": 2, "media_type": "AUDIO", "media_meta": { "title": "Hidden Track", "artist": "Nevermore", "album": "Dreaming Neon Black", "position": 0 } } } Notes If the playback is stopped via Media.MediaPlayer.Stop while an audio clip is playing, no playback will be resumed when the audio clip finishes playing. Radio-specific Methods Media.Radio.ListFavourites Lists currently selected radio favourites Params {} Response { "list": [ { "id": 0, "name": "BadRock Hard & Heavy", "country_code": "BG", "icon": "https://www.badrockradio.net/wp-content/uploads/2024/06/960x0-100x100.webp" }, { "id": 1, "name": "MAGIC FM", "country_code": "BG", "icon": "http://www.liveonlineradio.net/wp-content/uploads/2016/11/Magic-FM-Bulgaria.jpg" }, { "id": 2, "name": "1 Rock Bulgaria", "country_code": "BG", "icon": "http://www.radio1rock.bg/theme_assets/radio1rock/images/favicon.png" } ] } Media.Radio.PlayFavourite Plays a previously selected favourite radio station Params id: the ID of the favourite radio station to play (required); volume: the volume at which to play (0~10) (optional); { "id": 0, "volume": 4 } Response { "playback": { "enable": false, "buffering": true, "volume": 3, "media_type": "RADIO", "media_meta": { "title": "BadRock Hard & Heavy", "thumb": "https://www.badrockradio.net/wp-content/uploads/2024/06/960x0-100x100.webp" } } } Media.Radio.Stop Alias of Media.MediaPlayer.Stop Params {}

Script Request Guidelines 1. Provide a Clear Description: • Clearly explain the functionality and purpose of the script you need. • Include the use case or scenario where the script will be applied. 2. Identify the Target Device(s): • Specify the Shelly device(s) for which the script is intended (e.g., Shelly 1PM, Shelly Pro 3EM, etc.). • Mention firmware versions if relevant. 3. Detail Required Inputs and Outputs: • List any input parameters the script will handle (e.g., temperature, power levels, sensor data). • Specify the expected outputs (e.g., actions, status updates, data logs). 4. 3rd-Party Protocols or APIs (If Applicable): • If your script involves integrating with a 3rd-party protocol or system, you must: • Upload the required protocol documentation or API reference. • Provide a direct link to the API documentation, if available. • Note: The Shelly team cannot assist without this information. 5. Specify Required Features: • Highlight specific features or actions you need, such as: • Scheduling • Communication with external systems • Security measures (e.g., encryption) 6. Mention Any Constraints or Limitations: • Indicate any known constraints (e.g., limited bandwidth, specific operating times). • Include device limitations, if applicable. 7. Provide Any Existing Code or Examples (Optional): • Share any existing scripts, examples, or references that could aid in understanding your requirements. 8. Acknowledge Terms: • By submitting a request, you acknowledge that: • The service is limited, and support may be discontinued at any time. • Response times are not guaranteed. • The Shelly team may prioritize other requests based on workload and feasibility. Request Submission Template 1. Script Description: [Clearly explain the script’s purpose and functionality.] 2. Target Device(s): [List the Shelly device(s) this script is for.] 3. Inputs and Outputs: • Inputs: [List inputs the script will handle.] • Outputs: [List expected results or actions.] 4. Third-Party Integration: • Required Protocol/API: [Yes/No] • Documentation or Link: [Attach/upload file or provide link.] 5. Additional Features: [List any additional features or requirements.] 6. Known Constraints: [Describe any constraints or limitations.] 7. Existing Code or Examples (Optional): [Attach/upload file or paste code snippet.] Important Notes: • Requests missing required documentation for 3rd-party integrations may be delayed or rejected. • Submissions should be as detailed as possible to avoid unnecessary delays.

Ok i am surprised, something wrong. Send me your account e-mail in a message to take a look.