Beiträge von Nicola Marinelli

Hi,

I just had a deeper look at my Plus H&T in order to wire it to a 5V power supply without using the USB-C connector on the side (I want the wires to invisibly enter from the back cover and the wall, not to see a wire and a connector on the side) and I was assuming there is no other way than soldering two small wires on the microscopic pins of the USB-C receptacle, but I had a very nice surprise !

As you can see from the attached images, the small PCB hosting the USB receptacle and the wake-up button is connected to the rest of the device by means of a 3-pins header: simply removing the PCB makes it very easy to connect the 5V and GND wires and also enables a third wire to control from far away (even by a Shelly 1 ) the wake-up contact.

Most probably I will be able to fit a 5V power supply module (taken from a very cheap USB charger) inside the batteries compartment and so entering the H&T directy with the mains supply.

Let's see if this will cause too much electrical or thermal "noise" to the sensor: if that will be the case I will take the power supply in the "upstream" wall box).

Ciao, Nicola.

Hi,

since I've seen that the underlying issue has been discussed a few times here (in English, but I'm sure the same happened in German), let me propose, here as well, what I just proposed to Shelly, by means of the dedicated form on their website:

In order to partially overcome the big functional limitation resulting from the current very high (0.5C) lower bound for the temperature variation threshold, let me suggest to implement in FW the possibility to trigger a device wakeup and a status update/report when a programmable temperature (absolute, not variation) threshold is crossed, even better if two different absolute thresholds could be set (one for a rising temperature, one for a dropping temperature). This would support the implementation of a kind of "interrupt-driven" temperature control, rather than a "polling-based" one. No need to say that those thresholds should be programmable from the outside of the device through one of the existing APIs, in addition to the web GUI.

Ciao, Nicola.

Ciao,

if there is no solution, then this is a suggested feature for a possible future FW revision.

Ciao, Nicola.

Ciao,

i have a few Shelly 1s each connected to a local external switch, which is configured as "detached" from the local internal relay. I'm handling them through Home Assistant and everything is working fine but a small problem without practical impacts: the Shelly 1s are sending a "long press" event when the external swicth is switched to the on position and my Home Assistant registry is getting somehow "polluted" by those events that I don't handle ('casue they are not really informative, in the presence of an external real swicth, instead of a momentary button).

Is there a way to configure the Shelly 1 not to send the "long press" event at all ?

I tried setting the the "long push" time to 0ms in the Shelly 1s local configuration, but that value is not accepted by the UI.

Thank you and ciao, Nicola.

Hi,

writing here for the first time. My name is Nicola and I'm from Italy (Milan area).

I'm starting with home automation, for the time being with a very simple setup ( few external lamps switching on/off at sunset/sunrise).

Ciao, Nicola.