I have 14 identical events that each issues HS4 command like this one. This is the only thing they do. Nothing else.
they control 7 Tasmota light dimmers. 7 commands are for "on" and 7 are for "off"
they go to 7 different IP addresses (.111 in the example above ) as each dimmer has it's own IP address.
13 out of 14 work reliably all the time. One only is stubborn and refuses to work no matter what. I checked the syntax many times for typos. I actually copied and pasted the command from a working one to make sure there are no typos. I deleted and re-created the event. I changed the name of the event. No luck, no matter what I try. The one not working is
only for address .120 and only for "on" command. The "off" command does work for the same address.
The dimmer itself is not to blame as it responds properly if the URL is entered manually in a browser http://192.168.1.120/cm?cmnd=Power%20on
It also works if I use Big5 plug-in to issue the HTTP GET command. The problem with Big5 though is that I need to create HTTP profile for each and every dimmer, which means 7 HTTP profiles. Not impossible but the native HS4 solution looked simpler to me. For now I have .120 dimmer on Big5 and the rest on HS4 commands but hate when weird things happen that can't be explained.
Code:
&nhs.GetURL("http://192.168.1.111/cm?" , "cmnd=Power%20on", True, 80)
they go to 7 different IP addresses (.111 in the example above ) as each dimmer has it's own IP address.
13 out of 14 work reliably all the time. One only is stubborn and refuses to work no matter what. I checked the syntax many times for typos. I actually copied and pasted the command from a working one to make sure there are no typos. I deleted and re-created the event. I changed the name of the event. No luck, no matter what I try. The one not working is
Code:
&nhs.GetURL("http://192.168.1.120/cm?" , "cmnd=Power%20on", True, 80)
The dimmer itself is not to blame as it responds properly if the URL is entered manually in a browser http://192.168.1.120/cm?cmnd=Power%20on
It also works if I use Big5 plug-in to issue the HTTP GET command. The problem with Big5 though is that I need to create HTTP profile for each and every dimmer, which means 7 HTTP profiles. Not impossible but the native HS4 solution looked simpler to me. For now I have .120 dimmer on Big5 and the rest on HS4 commands but hate when weird things happen that can't be explained.
Comment