Beiträge von Marmachine

see: thread/9284-issues-with-update-frequency-of-shelly-sensors-trying-to-use-auxiliary-sensors/#wcf22

I came accross the same issue with Shelly Motion.
My application for Shelly motion is to monitor LUX value, however, i get only hourly updates, so it's either light or dark before i get the reading.

I've raised a ticket (somewhere around april '21) and reminded them (somewhere around september '21) however the issue has not been fixed.
My current version: 20211004-105639/v2.0.2@7eba4128

If you look into the documentation, you will find this:

Since v1.4.3: on MQTT connect, Shellies will publish:

• an announce message on shellies/announce and, since v1.6.0, on shellies/<shellymodel>-<deviceid>/announce. The message is JSON-formatted and contains a list of attributes: id, mode (if applicable), model, mac, ip, new_fw (true when an update is available), fw_ver (contains the current firmware version);
• availability message on shellies/<shellymodel>-<deviceid>/online with payload true;
• complete current state. This is device specific and is described in detail for each device below.

Device state is reported periodically, every 30 seconds by default. This can be changed by setting a new period for updates: mqtt_update_period under /settings. A value of 0 will disable periodic updates.

So the design does allow to set a different update_period, however when i enter http://<ipaddress>/settings i see mqtt_update_period is set to 60.
You should be able to change the value (for example to 1) through an URL by entering http://<ipaddress>/settings?mqtt_update_period=1

But nothing changes in the settings, value remains at 60, i still receive updates hourly, so i suspect that in the system somewhere hardcoded is 3600 as update frequency.

So please raise a ticket if you come accross the same issue... this feature should work by design i think, so it's a BUG!

For me it simply disappeared. It is not happening anymore, no hardware changes, just software update and re-calibrate i think might have fixed it. I really don't know.

Zitat

http://192.168.xxx.xxx/light/0?dim=cycle

down/stop/up/stop

But I would recommend to switch this both actions.

That means cycle at short press and toggle at long press.

Should this work with i3 setting for long press as well? I succeed in turn=toggle action for short press, but long press doesn't seem to work, the double short press however does, but only when i repeat the double press for a second time.

pasted-from-clipboard.png

And? Are you now able to switch On/Off as well as change dimming?

Hi,

I recently installed several dimmers. I have 1st and with my last order i got the 2nd generation as well.

With one of the Dimmers (2nd gen) i am experiencing problems, getting "Error 1" when switching on.

When this occurs, the dimmer switches off. Next press on the button will switch on again, then no problem and lights stay on.

I've upgraded to last firmware, dimmer is connected to Neutral, connected lights are 4x 4W Philips CorePro Led spots. I also have 5 of these spots with a Shelly Dimmer (1st gen) as well, working without a problem. Calibrated, changed leading to trailing edge, calibrated over and over... problem remains.

It's not consistent, in other words, this doesn't happen all the time. It happens with the momentary switch but also through the UI.