20 amp smart physical switch (to control Infratech heater) - preferable to be outdoor rated, but any
Hi all, I'm looking for a 20 amp (minimum) smart switch (physical, so as to either tap switch or remote/Alexa/HomeKit/etc) so that I can control several outdoor Infratech heaters (220V). If they're outdoor rated, even better. Thanks.
I have Wyze cameras and they’re mostly great but would like to find an IP camera that allows scrubbing on playback.
Any recommendations?
Welcome to our HE users! This new Q&A section is for you...
Hi.
I have a ton of different Ledvance bulbs, pluggs sensors and lights.
So far everything works fine.
Bot there is one thing I want too figure out.
I can link lights with the sensor so the light turns on when I enter the room.
But I want to put a timer on it.
Like 5 min without movement and the light turns of. I just can't figure out how..
I use LVD app.
Hello - I'm building a new home with zwave throughout. I want to install a flow detection shutoff, and flow meter for three different areas - a pool autofiller, irrigation system, and the home usage. I'd like to be able to detect any leaks in the system, as well as see the flow/usage by each area. What would you recommend?
hello
i am searching for a universal hub that takes my 433 remotes signals and repeats them 433mhz or converts them into bluetooth, wifi, IR, z-wave etc…basically into all the other signals. so my 433mhz remote becomes a universal remote.
it should have an app to configurate, maybe a learning function as well
i belive the homey pro can do that but it costs like 400$ …right?
so is there a cheap “china” product that works like that for at least 433 into IR, bluetooth, wifi
there are so many chinaproducts and i cant figure out which can do which trick !/ this for example https://de.trck.one/redir/clickGate.php?u=Ha2Rd3xX&m=1&p=9yUI69TI8b&t=kLf5673Z&st=&s=&url=https%3A%2F%2Fwww.techpunt.nl%2Fde%2Fhomey-bridge.html%3Fgclid%3DCj0KCQiA9YugBhCZARIsAACXxeJvViv59ieDen9zOXTP1jhc_OisKQxPlCZOJsPGX20nWo7UROROuJcaAix5EALw_wcB&r=https%3A%2F%2Fwww.hardwareluxx.de%2Fcommunity%2Fthreads%2Fbillige-chinaversion-von-homey-pro-gesucht.1333803%2F
i am working with 433mhz intertechno protokoll remotes .
please help
thanks, christoph
Looking for a simple solution that doesn't require running wire (replacing a switch receptacle is fine)
The problem: the only light switch in my garage is not near a door. So have to walk into the garage to turn the lights on.
Ideal Solution: physical remote I can stick on the wall next to the door to toggle a switch. Is there a product that is a toggle switch to replace the basic switch in the receptacle that I can also operate with a remote?
Is anyone actively developing anything on these IoT chips?
In particular, using NodeMCU for Lua programmability?
Just got a development board to play with myself...
After a fruitless search for WiFI pulse utility meter readers (can't believe I couldn't find anything suitable) and also having resolved a while ago not to include any homebrew hardware in my HA configuration, I've decided in the end to try this out, after all.
Having cut my teeth on Lua, thanks to Vera, it seems promising to use it for development, rather than Arduino programming, and the hardware is SO much cheaper, smaller, and neater than a RPi or the like.
Any experiences welcomed!
AK
Shelly i3 is an unbelievably cheap (9,99 EUR/USD) WiFi device that’s part of the fantastic Shelly family. It supports REST API, MQTT and much more.
https://shelly.cloud/knowledge-base/devices/shelly-i3/ 10
It’s just L,N and 3 inputs. No relays, so it’s a scene controller with bonus point to the fact that you can use your own buttons and keep the aesthetics of your house. Bonus points for WAF. It’s very small, so it will fit in your standard wall box easily.
While I built my own Scene Controller Virtual Device and I’m using MQTT for other devices of the family, Shelly can call your HTTP endpoints on button presses and in this case is more than enough.
The buttons support different actions (press, long press, double/triple press) and you can just call a service endpoint, or update a variable:
f3e509c0-f2a7-4f40-a099-af765e87c9fe-image.png
Go get it if you need a very cheap, very reliable scene controller for your home.
Finally, I’ve found an adequate replacement for my beloved MiniMote four-button remotes (I’ve had nine of them for the last 10 years or so!). I should have realised this earlier, but with four buttons and approximately the same form factor, the Philips Hue remotes are viable replacements…
…however, they are, of course, Zigbee and not Zwave, but this doesn’t matter in my HA environment, which has now completely ditched Zwave and Vera for all lighting and control functions, and replaced them with Hue and Shelly devices. These are all brought together with a Homebridge installation running under Docker on Synology NAS with the Apple Home app as the UI. This gives, of course, both secure remote access and voice control.
The MiniMote buttons I had configured as scene triggers to do whatever I needed, most usually toggling lights. The same functionality is easily achieved within the Home app by appropriate shortcuts.
I’m still using openLuup as a secondary hub which mimics all the various devices using MQTT and the ALTHUE plug-in and logs all device and sensor data using the built-in Historian and viewed through Grafana.
Works for me!
AK
After a long wait for an updated version of the rather crude and unfinished Z-Way integration to HASS, i'm now looking (reluctantly) in to replacing Z-Way with Z-wave JS..
Mind you this is a big existing network, not a new controller stick..
I threw up a docker for z-wave JS UI, and tried to connect it to the UZB stick.. It loads the whole network from the stick, but the driver keeps restarting?
Looking at the logs, I see a lot of Dropping message because the driver is not ready to handle it yet.
It seems like the stick just keeps talking like z-way was still listening? This ends up in the driver crashing repeatedly.. Any ideas to how I can get them talking?
In the code snippet below, you see the driver restarting with the graphic letters, seemingly while the stick is mid-sentence, or because of ACK timeout...
2022-10-02T19:19:59.664Z CNTRLR received additional controller information: Z-Wave API version: 6 (legacy) Z-Wave chip type: ZW050x node type Controller controller role: primary controller is the SIS: true controller supports timers: false nodes in the network: 1, 5, 6, 10, 11, 12, 13, 14, 17, 18, 21, 22, 23, 24, 25, 26, 27, 28, 29, 32, 33, 34, 36, 37, 38, 39, 41, 42, 43, 44, 45, 46, 4 7, 48, 52, 55, 69, 70, 71, 73, 74, 75, 77, 78, 79, 81, 82, 83 2022-10-02T19:19:59.765Z CNTRLR [Node 001] [Manufacturer Specific] manufacturerId: metadata updated 2022-10-02T19:19:59.766Z CNTRLR [Node 001] [Manufacturer Specific] productType: metadata updated 2022-10-02T19:19:59.767Z CNTRLR [Node 001] [Manufacturer Specific] productId: metadata updated 2022-10-02T19:19:59.768Z CNTRLR [Node 001] [+] [Manufacturer Specific] manufacturerId: 277 2022-10-02T19:19:59.769Z CNTRLR [Node 001] [+] [Manufacturer Specific] productType: 1024 2022-10-02T19:19:59.770Z CNTRLR [Node 001] [+] [Manufacturer Specific] productId: 1 2022-10-02T19:19:59.770Z CNTRLR [Node 001] [Version] firmwareVersions: metadata updated 2022-10-02T19:19:59.771Z CNTRLR [Node 001] [+] [Version] firmwareVersions: 5.39 2022-10-02T19:19:59.772Z CNTRLR [Node 001] [Version] sdkVersion: metadata updated 2022-10-02T19:19:59.772Z CNTRLR [Node 001] [+] [Version] sdkVersion: "6.9.0" 2022-10-02T19:19:59.772Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms 2022-10-02T19:19:59.792Z SERIAL » 0x01050006640f97 (7 bytes) 2022-10-02T19:19:59.792Z DRIVER » [REQ] [SetSerialApiTimeouts] payload: 0x640f 2022-10-02T19:19:59.815Z SERIAL « [ACK] (0x06) 2022-10-02T19:19:59.816Z SERIAL « 0x01050106640f96 (7 bytes) 2022-10-02T19:19:59.817Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.177Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2022-10-02T19:21:03.178Z DRIVER version 10.2.0 2022-10-02T19:21:03.179Z DRIVER 2022-10-02T19:21:03.179Z DRIVER starting driver... 2022-10-02T19:21:03.199Z DRIVER opening serial port /dev/zwave 2022-10-02T19:21:03.212Z DRIVER serial port opened 2022-10-02T19:21:03.213Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:03.229Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.232Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.233Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.234Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.234Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.234Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.261Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.268Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.268Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.268Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.271Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.271Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.271Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.273Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.274Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.274Z DRIVER loading configuration... 2022-10-02T19:21:03.298Z CONFIG Using external configuration dir /usr/src/app/store/.config-db 2022-10-02T19:21:03.298Z CONFIG version 10.2.0 2022-10-02T19:21:04.284Z DRIVER beginning interview... 2022-10-02T19:21:04.286Z DRIVER added request handler for AddNodeToNetwork (0x4a)... 1 registered 2022-10-02T19:21:04.286Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)... 1 registered 2022-10-02T19:21:04.286Z DRIVER added request handler for ReplaceFailedNode (0x63)... 1 registered 2022-10-02T19:21:04.287Z CNTRLR querying controller IDs... 2022-10-02T19:21:04.484Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:04.485Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:04.487Z SERIAL « 0x0123000400511a9f039900b834787d066515a4b79c45bb3af55ea7f6203006010 (37 bytes) 80120c84d 2022-10-02T19:21:04.489Z SERIAL « [DISCARDED] invalid data 0x9ef4 (2 bytes) 2022-10-02T19:21:04.490Z DRIVER Dropping message because it contains invalid data 2022-10-02T19:21:04.490Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:05.488Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i n 100 ms. 2022-10-02T19:21:05.591Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:05.592Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:06.596Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i n 1100 ms. 2022-10-02T19:21:07.698Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:07.699Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:08.717Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D river.ts:3980:23) at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/co ntroller/Controller.ts:713:33) at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js /src/lib/driver/Driver.ts:1207:26) at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive r/Driver.ts:1014:16) 2022-10-02T19:21:08.723Z DRIVER destroying driver instance... 2022-10-02T19:21:08.728Z DRIVER driver instance destroyed 2022-10-02T19:21:08.739Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2022-10-02T19:21:08.740Z DRIVER version 10.2.0 2022-10-02T19:21:08.740Z DRIVER 2022-10-02T19:21:08.740Z DRIVER starting driver... 2022-10-02T19:21:08.745Z DRIVER opening serial port /dev/zwave 2022-10-02T19:21:08.751Z DRIVER serial port opened 2022-10-02T19:21:08.752Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:08.754Z DRIVER loading configuration... 2022-10-02T19:21:08.755Z SERIAL « 0x01080120c84d9ef40138 (10 bytes) 2022-10-02T19:21:08.757Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:08.758Z DRIVER « [RES] [GetControllerId]Hi,
I have an old analog intercom (Golmar) that has this horrible buzz sound when someone rings my apartment from the buildings front gate. This becomes very annoying at night so I need to make this buzz silent from 10:00pm till 7:00am
I have a "Shelly Plus 1" connected to the intercom. (wire #0 and wire #3 are responsible for closing the circuit for the buzzer).
I have set Webhooks and Scenes, but my wiring does not work. Can anyone tell me what i have done wrong?
Cheers!
Wiring Shelly 1 plus v12.1.png Golmar intercom current wiring.png
Well with all that has been going on with Vera/eZlo, many people are abandoning the Vera hubs and moving on to other solutions, such as Hubitat (my case), HASS, HA, and many other controllers.
In the past, I had already been informed that when the migration was over, my Vera would go to the incinerator, or under the wheel of my car, and of course, I did not comply.
So I wanted to open a debate, for those who have not yet sold their Vera on eBay, are with the equipment idle, what destination could be given?
I see many saying that it has become a laboratory, I don't see much sense, since it is becoming obsolete and without a drive. But it can be a destiny. Has anyone thought about whether it is feasible to change the hub's SO so that it becomes a host for MSR, for example? Or even Home Assistance? I have no knowledge, but it seems to me that processor and memory have to do something like that, already has embedded wifi and network.
Does anyone have any idea if it is possible to give this equipment a destination other than a box?
I just started [uncloud] forum to gather in one central place all smart devices working without the cloud, since this is not information easily available on the Internet.
I thought this might interest some users of this forum and any feedback are welcome.
And let me know if you know more devices that I should add to the list!
- Marco
Good afternoon. Due to the new ezlo not being available in europe yet, I wanted to change the z-wave getway that works with the reactor to add to the home assistant. What advises?
Thanks
I didn't see an existing Topic for heating-ventilation-air conditioning, so here goes...
Is anyone successfully controlling a "mini split" (i.e. ductless) A/C or heat pump system at home? I will be adding such a system soon to new construction, and wondered if certain brands/models interface better via Z-Wave or WiFi than others in a HA setting.
I know a bunch of these "splits" come with handheld remotes, but having robust Home Automation control (preferably without a dedicated plug-in needed on the Vera side) would be idea.
Happy to hear suggestions. Thanks!
LibraI have a legacy Vera system that in my home and I need to add a few devices to a cottage on my property. The Vera zwave won't see devices that far away. Both the house and cottage are on the same LAN. Can I bridged an Ezlo Plus to my existing Vera plus and if so are there instructions?
Hey guys...
Is it just me or the GE/Jasco switch or very sensible to power outage ?
Almost each time we have a power outage, I need to replace at least 1 switch to replace.
Each time, same behaviour, the blue led is flashing rapidely and nothing works.
Last power outage, I got 3 switches. 95% of our switch and dimmer are GE/Jasco.
Shelly i3 as a cheap scene controller for Openluup
-
Shelly i3 is an unbelievably cheap (9,99 EUR/USD) WiFi device that’s part of the fantastic Shelly family. It supports REST API, MQTT and much more.
https://shelly.cloud/knowledge-base/devices/shelly-i3/ 10
It’s just L,N and 3 inputs. No relays, so it’s a scene controller with bonus point to the fact that you can use your own buttons and keep the aesthetics of your house. Bonus points for WAF. It’s very small, so it will fit in your standard wall box easily.
While I built my own Scene Controller Virtual Device and I’m using MQTT for other devices of the family, Shelly can call your HTTP endpoints on button presses and in this case is more than enough.
The buttons support different actions (press, long press, double/triple press) and you can just call a service endpoint, or update a variable:
Go get it if you need a very cheap, very reliable scene controller for your home.
-
I have two on my nightstands. I'm using them as scene controllers, with 3 buttons on the same aesthetics of the house.
button 1: 1 click to turn lights off, double click to turn ambient lights on
button 2: 1 click to close all roller shutters, double click to position them for lights, etcyour options are endless
I usually call vera's standard endpoint, to toggle device status, or run scenes (or functions). -
Oh, OK. Yes the browser interface is very nice and straight-forward.
I've set up a couple of URLs, and it all looks good, but nothing appears in the log when I press the swich.
There is, I suppose, the remote possibility that the switch is not wired correctly or otherwise faulty. The are momentary switched (and configured as such.)
This is what I see:
-
Revelation!! ...
...I've just noticed these words in the Settings above:
Works only when button is configured as Toggle
...but I have it on a momentary switch!!
If these things are reliable, then they really are extraordinary. My initial reaction is that WiFi is not appropriate for small HA devices with no bandwidth requirement, but easy browser-based UI is really nice (if you actually read what the words say!) I haven't measured the residual power usage yet, either, but I'm hoping it's low.
-
I’ve just ordered some more of these, and also a few of their dual relays.
Lighting strategy is now ZigBee for individual lights and LED strips, but WiFi for light clusters (chandeliers, etc.)
Looking now for a nice 4-button WiFi had-held scene controller (I did love my ZWave Aeotec MiniMotes!)
-
I've practically ordered any device they've shipped lately and I must confess it's the right tool for the job. I'll probably test their binary input device soon.
Best part is that I've completely integrated them thanks to my mqtt bridge + virtual devices plugin
I've also deployed 4-5 tasmota based devices in order to get sensors data and I must say zwave is dying behind those tiny wifi devices. I get the point of the mesh and I've invested into zwave, but I think for small setups these are a safer bet.
-
That's why I've created the http virtual devices plugin
I wanted to stay generic, and I'm considering an Ui to automatically configure devices based on their type. People on the other side usually updates them calling a luup url, or polling them via luup. I've considered the latter as a native option as well.
-
Hmm... problem with configuring my second i3 device. I updated the firmware, and it says it’s the latest, but the version is totally different from my other one! Also, now, neither device is picking up the current time. A bit worrying.
Current version: 20200827-070910/v1.8.3@4a8bc427
You have latest version of your device!The current Firmware version of your Shelly device is 20200421-183805/master@d834f204 No newer firmware available.
-
@therealdb said in Shelly i3 as a cheap scene controller for Openluup:
maybe open a ticket
Yup, done that already. Will be interesting to see the response.