you should use circuit breakers (fuses) before shelly
ESP MCU's aren't good to roam from AP to AP (or wifi extender) so I have a bit doubt of that it's roam to extender, but especially when you have fixed IP in device you should be able to reach it if 3EM is connected to extender because then it's still in wifi and when router is back too everything work as should.
you can test it removing extender and then reboot wifi AP to see if 3em operates as now
Reason why 3EM loses it's connectivity is Wifi router changes wifi channel, If possible set fixed wifi channel to your wifi router
Option in to reboot 3EM by switching off circuit breakers
Please check HACS integration called ShellyForHass it does support cloud connectivity
I haven’t use it by my self
Hello Terry and welcome to forum
You can create a webhook command to shelly button1 actions (I presume you mean to have Shelly Button1?) with following syntax:
http://[Shelly1PM_IP]/relay/0?turn=toggle
replace [Shelly1PM_IP] with relay IP address (10.20.30.20)
That will toggle relay on/off with each press
Thank you Seven of Nine I have removed that source each time
Interestingly you can add what ever as source, but it's changes and that misleads me to remove it - now I feel dumb
I've used mqtt explorer to send some commands for gen1 devices
Now when using gen2 devices I can't figure out how that mqtt topic & syntax is going for those devices
topic for devices is shellies/test-pro4pm/rpc
one of json variants what I have used:
{
"id": 1,
"method":"Switch.Set",
"params":{
"id": 1,
"on": true
}
}Appreciate help to know even one working json syntax
I couldn't find an option to make scene based of Adc input level. Only option is below/above of Vdc and trigger then action
My approach is to use UNI as input from 1-10V dimmer and send command to Shelly Dimmer2. For each 0.5Vdc change send command http://[shelly_ip]/light/0?dim=down&step=5 or dim=up&step=5
Is that even possible with shelly firmware?
Hello Tjb88
How are you finding the Wifi range with this firmware I had four dimmer 2 devices that would drop connect with this firmware release, it affected every device in the course of about five weeks until I reverted back to the stable firmware.
With the device behind a plaster wall and light switch, the quickest way to get them connected was to power cycle from the main breaker.
Matt
Do you mean to see wifi rssi value?
{"wifi_sta":{"connected":true,"ssid":"xxx","ip":"192.168.xxx.xxx","rssi":-60},if LAN settings are correctly entered, you should able to login to plug web interface using device ip address using another LAN device
http://192.168.x.0/ where 198.168.x.x refer your device local lan IP
If device is not reachable, then LAn settings are incorrect
--------
With (iPhone) App process goes
1. plug shelly to network
2. open shelly app, top right corner hamburger menu "add device", Add your wifi credentials, Add via = Wi-Fi & Select device to add or scroll down and select any, approve request to join shelly wi-fi
3. Add Device option update details , Device Name, room & image
4. wait a monent while device is booting and then it should appear to menu as Online
Correct, that's a one way to do it
Hi and welcome to forum,
Shelly1 temporary add-on support Dallas DS18B20 type temperature sensor.
Pool 2-wire temporary sensors are typically resistance thermometer sensors (PT100, PT1000) and are not compatible with temperature add-on
Hi and welcome to forum
please assign device to your local Wi-Fi network. 192.168.33.1 is device own hotspot IP and you can't access it without connecting to same wifi
https://shelly.cloud/documents/user_guide/shelly_plug_s_app.pdf
Problem solved, device went to RMA
Fixed using HA automation
By_minute values state power consumption for the last three minutes
Energy consumption by minute (in Milliwatt-hours) for the last three minutes (the lower the index of the element in the array, the closer to the current moment the minute)
what model your Unifi AP's are? If those are Unifi 6 -family, then problem most probably are in Unifi end
Some reason some esp-based devices drop from Unifi 6 AP and go offline. After esp device reboot it stays connected for a while, but then drop again.
There is no known fix for that Unifi problem.
It didn't change anything. The value is in seconds, right?
here's the output I got after running the API call
Code"mqtt": { "enable": false, "server": "192.168.33.3:1883", "user": "", "id": "shellyht-6B53E5", "reconnect_timeout_max": 60.000000, "reconnect_timeout_min": 2.000000, "clean_session": true, "keep_alive": 60, "max_qos": 0, "retain": false, "update_period": 65 },
I dont know if this is anymore valid, but mqtt is not enabled?
When H&T is running with battery it woke and send update only when temperature is changing more than 1C (dont remember F value) or humidity is changing more than 5% units or periodically in every 12hours.
Using external power source device will update temp & humidity in every 10 minutes or when temp/humidity changes 0.5C / 1%
You can see from mqtt topic: shellies/[device_name]/sensor/act_reasons "periodic" or "sensor" depending which one was reason for update
I do not recommend to select external power option if running with battery, using that battery will run dry in less than 2 week
You can use switch node, connect input from what ever mqtt device - I have a shelly button1 giving commands
Button1 can give 4(5) type of commands - those are S, SS, SSS and L which are single, double, triple and long push. Fifth type of command is blank and that's the one what we want to filter
Create a switch node with 5 output, one for each command. Then wire output in a way how you like
Entire flow is over complicated to perform simple tasks. I'm trying to keep my flows tidy:
Button1 send command.
Short push toggle lights.
Double push toggle between 20% and 70% dimming
Triple push reboot shelly (just in case) loop to toggle light after 10sec
Long push set 100% brightness
Empty message is not connected
MQTT is used to read and send commands. node-red-contrib-shelly palette is used to read dimmer current status and function node to parse status and toggle command depending of current state
full flow json is available from pastebin
you need to modify device names & IP's
Switch node:
[
{
"id": "632f6fe805837237",
"type": "switch",
"z": "ef25cf265c7ab0f7",
"name": "msg",
"property": "payload.event",
"propertyType": "msg",
"rules": [
{
"t": "eq",
"v": "S",
"vt": "str"
},
{
"t": "eq",
"v": "SS",
"vt": "str"
},
{
"t": "eq",
"v": "SSS",
"vt": "str"
},
{
"t": "eq",
"v": "L",
"vt": "str"
},
{
"t": "eq",
"v": "",
"vt": "str"
}
],
"checkall": "false",
"repair": false,
"outputs": 5,
"x": 310,
"y": 240,
"wires": [
[
"89c6775b087c8abf"
],
[
"77bd7dcb155c0615"
],
[
"9fba0aad21971c9e"
],
[
"61ca88fca7d9a1f0"
],
[]
]
}
]Hum i tried with the w32tm windows service and my Shelly didn't like it...
No one has ever tried to setup a local ntp server ?
I do have, running in a docker cturra/ntp - No experience of running NTP server in windows
What temperature & Humidity threshold values you have?
Please remember, when running H&T with batteries updates does happen only when threshold values are exceeded
Threshold values can be managed in Sensor Settings