WIFI Switch to integrate in wall

---

@xCite86 said:

Hi there!

I am very impressed with Jan’s PCB, so here`s my short tutorial how to add his esp8266-wifi-relay into Pimatic.

The Firmware was written in lua, so i assume that it is known how to upload *.lua’s with ESPlorer.

blah bla blah…

since my modem allows only dhcp (and the adress-reservation are very buggy in my modem) it wass nessesary for me to get a new ip on my ESP every reconnect. It happens not often, but when i have to unmount my wallswitches, reset the esp… this was annoying forme.

so i´m playing around with ESPEasy combinated with MQTT (big thanks @wutu) and that works very well. With internal rules-feature (and i hope R95 was stable and reconnects (if errors or
Power-failures or whatever ^^) well with a new ip in my wlan.

Infos and a little workaround found here:
https://forum.pimatic.org/topic/1367/espeasy-with-pimatic-over-mqtt/1
https://forum.pimatic.org/topic/1577/espeasy-add-a-relay/39

Hi @xCite86
It would be on the DHCP server (modem) extend the lease time?
ESPEasy uses SSDP (Advanced> Tools), after launch is seen in the Neighborhood.

@wutu
the lease-time was on 86400 seconds, thats 60 days ^^
but i will try to play with ssdp and see what happens

86400 sec = 24 hours

hm… i know that my math was not the best… but when my girlfriend screams “food is ready” my brain was run in a general runtime error

edit: but btw… i think 24 hours are quite okay?

but anyway - it is no longer relevant for me… works well with mqtt and with the proverb “never touch a running system”…

@xCite86 said:

edit: but btw… i think 24 hours are quite okay?

I think it’s not enough. I have setup 365 days and the their hostname is automatically added to the home domain. I sometimes manually released.

Just to go sure:
(1) Can I replace my simple wall-switch (which is a dimmer right now) with this esp device?
And afterwards, am I able to connect my dimmer (2) or need to take a common switch?) with this device, (3) or has it a (manual) switch onboard?
(4) Which kind of cables do I have to pull from the device to the switch?
(5) I only got one brown cable and two blacks, of which one I am not using at all, so will this work with that device, too?

And why has it two relais, I cannot imagine some example where one would replace a wall-switch and then having two more switches, lol.

Thank you for your help.

It is only a switch, no usable as dimmer. There is also a one relais version available.

@xCite86
Your code has a bug: the After hours try & error the following code is working:

-- pimatic-edition 02.02.2016
version = "0.3.2.pimatic"
verriegelung = 0 -- 0 = inaktiv 1=aktiv

-- zusatz aus originaler config openhab
ctimer = 0 -- 0= inaktiv 1=aktiv
r1_timer = 10 -- zeit in Sek fuer relay 1
r2_timer = 10 -- zeit in Sek fuer relay 2
-- zusatz ende aus originaler config openhab

sid1 = "ESP_1_Relais_1"
sid2 = "ESP_1_Relais_2"
PimaticServer = "172.16.0.2"
BaseLoginPimatic = "encoded-pw"
contentLength = 0

-- zusatz aus originaler config openhab
tmr.stop(5)
tmr.stop(6)
-- zusatz ende aus originaler config openhab
-----------------------------------------------
function send_to_visu(sid, cmd)
platform = "Pimatic"

if (platform == "Pimatic") then
if (cmd == 1) then switch="true" elseif (cmd == 0) then switch="false" end
port = 80
link = "/api/device/"..sid.."/changeStateTo?state="..switch..""
end

if (platform == "Openhab") then
if (cmd == 1) then switch="ON" elseif (cmd == 0) then switch="OFF" end
port = 8080
link = "/CMD?" ..sid.."=" ..switch
end

print(link)

    conn=net.createConnection(net.TCP, 0) 
    --conn:on("receive", function(sck, c) print(c) end )
    conn:on("receive", function(sck, c) end )
    conn:connect(port,PimaticServer)
    conn:on("connection", function(sck, c)
     --- Wait for connection before sending.
      sck:send("GET "..link.." HTTP/1.1\r\nHost: "..PimaticServer.."\r\nAuthorization: Basic "..BaseLoginPimatic.."\r\nConnection: keep-alive\r\nAccept: */*\r\n\r\n") 
     end)
     
    conn:on("disconnection", function(sck)
     print("Got Disconnection\n")
    end)

end
-----------------------------------------------

@fennsen
could you please do us a favor and edit your post according to this guideline, thx!
https://forum.pimatic.org/topic/1179/how-to-post-code-on-the-forum

@leader21 Thanks for the hint. done

Guys?

Is it automatically actualizing the state for you?

If I send tcp commands or click on my switch, it stays on “on” though it is being sad that “getStateCommand”: “echo false” is not needed because the switch would automatically tell its state pimatic. Have I done something wrong?

@tehebil Hi, this topic is quite old, but neverthelesse maybe helpful:
This board can also be flashed with TASMOTA (sonoff firmware).

I tested this with tasmota Version 6.2.1
In the setup you’ve to choose type ‘18 generic’ and then adjust the GPIOs (for Relay1, Relay2 and both switches.

The major advantage: you can use then and integrate to pimatic via MQTT (mqttswitch) and get rid of this shell execute nonsens via tcp port. Also you get a reliable automatic feedback&status on this way.

Works like a charm!

Check out if you finde ESPurna with Alexa support…

@swen Thanks for the hint. But I avoid native Alexa support on the devices.
I’ve a more holistic concept to provide Alexa support for all (supported) devices: every device is centrally included in pimatic and then provisioned via the ECHO plugin
There I can choose which devices should be controlable via Alexa and which not.

Native Alexa support is only realized on top via ioBroker (iobroker-pimatic adapter but optional from operational perspective) e.g. for Spotify

Hello
Where can i buy this?

Thanks

@joaquim-lopes a alternative would be the shelly devices.
https://forum.pimatic.org/topic/4222/shelly-devices