Shelly Wave help

Don't know how to help you with SmartThings exactly the base idea for a thermostat is to switch on and off the heater according to a preset temperature (set-point). The above example was not for smartThings just a general script on how a WiFi device could be programmed. You should have a device that is measuring the water temperature and a relay that will open and close it according to the temperature reported by the device measuring the temperature. But there's may be a problem with that. Even do the SmartThings runs the automation locally if for any reason the gateway went off there's not gonna be the regulation anymore. You should make an automation that will turn on the relay (heater) when the temperature reported by the measuring devices reach certain point and another automation that will turn off the heater when another temperature is reached.

That's correct the power consumed less than 0,3 W when the relays are opened (off) the difference is the power that is needed to keep the relays closed (output On) that is about 200 mA on 12 V which will result in about 0,25 W more.

Hello, I think your request won't be possible to achieve, the short press is meant to open and close the shutter completely and the hold is the movement until the button is released. We try to keep it familiar to the users for that we use the same method as the windows in the car click to fully open or close and hold to open until you release the button.

Most probably the issue you're facing is due to the Z-Wave SDK used to compile the device firmware. Recently we discovered that the SDK we were using have a bug that may cause the traffic, we already report the bug to the SDK developers and they release a new SDK which we currently testing, when proved that the new SDK have no more this bug we will start to release new firmware for our devices on our support portal.

The association you seek is the following one 😉 Association Group 2

@xtech How can we be expected to "wash our hands" of this situation? The way SmartThings develops their core code so that the developers can write custom drivers from it is entirely within their control. All we can do is create drivers that adhere to their specifications. If there are issues in SmartThings' core code, how can we possibly address them when we don’t have access to it? As for the official drivers, our ability to intervene is even more limited. We provide them with sample devices, pay for the certification process, and then wait for them to integrate the devices. During testing, we remain in contact with their team and resolve any issues on our end if needed. Once everything is verified and fixed, SmartThings integrates the devices as per their own standards and requirements.

I did try that with the devices I have here but it didn't happen to me that's why I need more details. Can you reproduce the issue at any time or for example after the device is power cycled? If so what you may trigger is the reset of the device which can be done by pressing the button connected to the SW (1-4) 5 times within 3 seconds that command is possible only the first minute after the power cycle of the device. PS: It may be a very realistic scenario, just show a 4 year old kid where the light is turned on... the 4 clicks will be done an instant after 🤣

@chr13 Can you let us know more about the issue and how you - we can try to reproduce. Apart of that we would like know if you have devices that acts as repeaters, mostly if the 2 PM are the routing devices or they receive the commands trough a device or directly from the controller.

Unser Shelly Wave 1 ist mit dem SmartThings-Hub kompatibel. Wenn die Firmware des SmartThings-Hubs des Fernsehers dieselbe ist wie die des Standalone-Hubs, sollte es keine Probleme geben, ihn hinzuzufügen. Wie Sie im nächsten Link sehen können, haben wir verschiedene Geräte bereits von SmartThings zertifiziert Wenn Sie weitere Einstellungen für unsere Geräte benötigen, empfehlen wir Ihnen, die funktionalen Treiber für alle unsere derzeit verfügbaren Geräte unter der folgenden Adresse zu verwenden: https://bestow-regional.api.smartthings.com/invite/adMKvAPaArj9

Most probably as it was an issue that is related to the SDK in the part of the code we do not touch. The Silicon Labs fixed the issue and released the new SDK, were testing toughly the SDK, once we're sure that the issue is gone and there's no other issues we will proceed to do the updates of all the firmware of other devices.

No this firmware is exclusively for the Shelly Wave 2PM. Every device have its own firmware 😉

We have the firmware ready, we're currently testing it, the bug is fixed we're looking if everything else is ok. Anyone that needs it can download the attached file. After the update give some time to the device - gateway to read the device info again, in case the device becomes marked as dead just press a switch or button connected to it. If you will have any other issues please report it in reply to this post Have a nice weekend 😉 Wave_2PM_800_EU_20241119_1226_QNSW-002P14US_[13.00]_9DD2F96C.gbl

We get the new SDK and compile the new firmware, we have to test if everything is ok, before we release the new Firmware.

Before we release any more firmware we do have to toughly test the new SDK that should have the bug-fix for the issue that was found on the last Silicon Labs SDK. After we have this confirmed we will start with the firmware updates that will have the Detached mode added. Unfortunately I can't give you an estimated date of release of the firmware updates.

We did try the Wave i4 with the latest firmware and we didn't encounter a delay that you mentioned. Below the video of the test done, as you notice the command is sent out immediately when the button is released for the pressed 1 command. VID_20241107_134201.mp4