Beiträge von -Teme-

Yes, you can specify NTP server in web interface of Shelly device.

Internet & Security -> SNTP

Or using rest API call

http://<shelly_ip>/settings?sntp_server=<ntp_server>

Forgot to add answer how to got this work. I had an incorrect string, but it did work for other models.

http://192.168.33.1/settings?mqtt_enable=1&mqtt_server=192.168.x.x:1883&mqtt_user=[mqtt-username]&mqtt_pass=[mqtt-password]&mqtt_id={shelly_device_name}

Zitat

-Teme- can you post your code? (I think that you use home assistant with mqtt integration)

You are right, I’m using HA and mqtt broker, but not HA automations. My automations are build with node-red and in that “filter” can be done with switch node, adding different outputs for each msg.payload value and finally blank where debug node is also good to set to see when those messages are coming

I had same issue and actually few other devices too. Everything leads to mqtt monitored button and to part of that automation.

Every now and then it send empty “” MQTT message and automation use that as an trigger to toggle lights on/off. Fix was to identify that “” command from button and give task to do nothing.

Since that I haven’t had any problems with dimmer.

Same thing could happen after wifi reconnect and MQTT receive discover message.

Sending MQTT service setup via http api

Device response to call 404 not found

Call tested with various number of different devices and it does work with them, but not with motion

http://192.168.33.1/settings/mqtt?mqtt_enable=1&mqtt_server=[srv-ip]:1883&mqtt_user=[mqtt-user]&mqtt_pass=[mqtt-pass]&mqtt_id={shelly_name}

No matter if device IP is set or firmware is updated to latest (tested with beta also)

Okay, found that missing part to get mqtt calls to operate too. Magic syntax was mqtt_enable

I have been able to proceed with this.

Device name http://192.168.33.1/settings?name=bedroomDimmer

Set Wi-Fi http://192.168.33.1/settings/sta?e…92.168.1.1&dns= 192.168.1.1

Update http://192.168.1.xx/ota?update=1

But then I hit to problem, how to set mqtt details? Same syntax format doesn’t work for that. How I should format MQTT part?

http://192.168.1.xx/settings/mqtt?enable=1& server=192.168.1.xx:1883&user=mqttusr&key=XxxxxxX&id=bedroomDimmer

It’s obvious to send command and check state via http/ mqtt calls, but I would like set system parameters with http call - is that possible?

I do have 50+ Shelly devices waiting for installation but using web up of device is painful when you need to repeat same steps number of times.

My approach would be to create a script what first set device name, add Wi-Fi ssid + pass and fixed up address details.

On second call when device is in my Wi-Fi, mqtt details would be added, update firmware and lat+lon coordinates

This kind of scripting I just need to update ip and device name per run

New Dimmer2 installed to test bench for preinstallation before final installation.

Everything worked well, except physical switch ports aren't work at all.

L, N are connected, O to 60w bulb, L shared with momentary wall switch.

Momentary switch been changed between SW1 & SW2 interfaces with changes to config

Also tried to use N instead of L but no success.

Monitoring actions from MQTT server can't see any movement in there neither.

Using MQTT or http commands work OK and can control dimmer

Latest fw updated. Inside there are no any mark of any burn parts

It looks a like it was dead on arrival. Pity thing is I have bought this 6 months ago and waiting for installation since then

Any tips how t get it work? or how RMA process goes?

Edit: shelly1 &1PM are operating well in same test bench, so all switches and wirings are OK

image1

Image2

Is there direct option to control Dimmer 2 with shelly button 1?

like short press to toggle Lights on/off, long press to dim up/down and double press to set 100%

I have Home Assistant can create those with that, but is there direct integration?