It is only a switch, no usable as dimmer. There is also a one relais version available.
-
WIFI Switch to integrate in wall
-
@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-forumpimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@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