Skip to content

Hardware

Hardware related - Small board computer to IP Camera and technologies like Zigbee or Zwave!

183 Topics 2.0k Posts

Subcategories


  • Camera integration into your home automation

    9 Topics
    122 Posts
    R

    BTW I found out that the Google also a new API for their cameras. Has anyone tried to integrate the Nest Doorbell (or another Nest cam) in openluup?

  • Single board computer, like raspberry pi, pine64. The heart of your system!

    11 Topics
    64 Posts
    toggledbitsT

    Going OT here a bit... I just posted benchmarks for RPi 4 maker board and Compute Module

  • 1 Topics
    6 Posts
    LibraSunL

    Only took me 7 months (plus one productive morning!) to fix. Turned out not to be a Sonos problem, but will leave here under Hardware > Sonos just in case others find themselves similarly afflicted.

  • Discuss your vera problems and findings here

    58 Topics
    858 Posts
    A

    The code in your link was messed up when they updated that forum some years ago. I've rehashed it to give it a chance of working but I suspect you may still have trouble getting it to work. Running it in the Lua test window would be your starting point after reading the
    push over api doco.

    Another alternative is to use Telegram with the Telegram plugin.

    -- Refer to pushover documentation: -- https://pushover.net/api local pushToken = "YourPushOverTokenHere" local pushUser = "YourPushOverUserCodeHere" local pushTitle = "MessageTitle" local pushMessage = "MessageContent" local snapshotFile = "/tmp/camera_snapshot.jpg" local pushPriority = "1" -- Sound could be: pushover bike bugle, cash register, classical, cosmic, falling, -- gamelan, intermission, magic, mechanical, pianobar, siren, spacealarm, tugboat, -- alien, climb, persistent, echo, updown, none local pushSound = "gamelan" -- Link to the BlueIris videostream of that camera local pushUrl = "http://xxx.xxx.xxx.xxx/mjpg/ShortCamName&user=XXX&pw=XXX" local pushUrlTitle = "Camera Name" -- This points to one of my BlueIris managed cameras local camera = "http://xxx.xxx.xxx.xxx/image/ShortCamName?q=50&s=80&user=XXX&pw=XXX" -- Get the snapshot from the camera local out = assert(io.open(snapshotFile, "wb")) local _,data = luup.inet.wget(camera) out:write(data) assert(out:close()) --Send PushOver request local curlCommandTab = {} table.insert (curlCommandTab, 'curl -s') table.insert (curlCommandTab, '-F "token=' ..pushToken ..'"') table.insert (curlCommandTab, '-F "user=' ..pushUser ..'"') table.insert (curlCommandTab, '-F "title=' ..pushTitle ..'"') table.insert (curlCommandTab, '-F "message=' ..pushMessage ..'"') table.insert (curlCommandTab, '-F attachment=@' ..snapshotFile ..'"') table.insert (curlCommandTab, '-F "sound=' ..pushSound ..'"') table.insert (curlCommandTab, '-F "priority=' ..pushPriority ..'"') table.insert (curlCommandTab, '-F "url=' ..pushUrl ..'"') table.insert (curlCommandTab, '-F "url_title=' ..pushUrlTitle ..'"') -- The .json suffix requests that the response be in JSON format table.insert (curlCommandTab, 'https://api.pushover.net/1/messages.json') local curlCommand = table.concat (curlCommandTab, ' ') print(curlCommand) local handle = io.popen(curlCommand) local result = handle:read("*a") handle:close() print (result) -- Delete temporary snapshot os.remove (snapshotFile)
  • Discuss device integration and use

    9 Topics
    34 Posts
    G

    To manage high temperatures (600°C) with Zigbee and Sonoff iHost, you can use a high-temperature thermocouple (like a K-type) with a MAX31855 or MAX6675 converter. Then, connect it to an ESP8266/ESP32 microcontroller with a Zigbee module (like Sonoff Zigbee). This way, you can read the temperature and integrate it into your automation stack via MQTT or HTTP.

  • The alternative zwave controller

    38 Topics
    456 Posts
    H

    I'll answer my own question for others benefit. I was able to successfully upgrade UZB from firmware 5.34 to 5.39 using Z-Way server and the all token to first downgrade and then upgrade following this path.

    5.34 → 5.33 → 5.27 → 5.36 → 5.39

    My bootloader version is 40196 and I did not upgrade the bootloader along the way, I started and ended with the same bootloader.

    I did a ResetAPI followed by a ControllerReset after each firmware downgrade/upgrade to ensure that I had a clean start. I also disabled all zwave device (unplugged/removed batteries) to ensure that any stray packets didn't interfere with the process. Be sure to backup your configuration/network before updating the firmware.

    After upgrading to 5.39 I'm now able to use the promiscuous mode in Z-Way zniffer to capture packets on the network (although it misses some packets)

    I did get a note from support, so those with firmware under 5.24 may want to pay heed to this.

    there is a batch of sticks with "dead-end" firmware and a slightly modified board topology. But given the fact that such sticks are usually impossible to upgrade above version 5.24, then you most likely have a good stick for which this operation will be possible.

  • Z-Uno is the first and only easy to use developer board that allows you to create your own Z-Wave device without deep knowledge of Z-Wave protocol or programming. Z-Uno is a mix of Z-Wave home automation radio protocol power and Arduino simplicity.

    1 Topics
    3 Posts
    I

    These are great not just for sensors, but also to ZWave-ify existing equipment in cases where a simple dry relay ZWave switch won't cut it. I had a few motorized transom windows with IR remotes, that can also be controlled through some weird industrial serial protocol. I build controllers for them using ZUNO boards, so I can now control the windows through OpenLuup.

  • DIY HomeKey locks via Reactor

    3
    3 Votes
    3 Posts
    334 Views
    therealdbT

    Yep, thanks to @toggledbits for adding the tag capability in a very short time frame!

  • Scene Controllers -- What are you using?

    6
    0 Votes
    6 Posts
    486 Views
    CrilleC

    I have a Sonoff NSPanel connected to HASS via NSPanel_HA_Blueprint in the hallway where the physical buttons are remapped from the relays to just publish MQTT messages to left or right garage door, appreciated by the whole family. Weather and QR code for guest WiFi also used by some but the rest is just for fun and as @toggledbits said, more of a dashboard rather than a scene controller but it was mentioned 🙂

    We have Xiaomi Aqara Mini Switches in each bathroom/toilet for manual override of the extraction fan if needed.

    My only Shelly i3 is connected to a cheap dumb twilight switch so Reactor can control which lights to turn on/off rather than the actual relay.

    We have some IKEA Tradfri wireless dimmers, I had an idea to use one for manual start/stop of our Wallbox charger but it never happened as we found ourself use Siri for that when needed.

  • 0 Votes
    4 Posts
    151 Views
    A

    May be better to get a DIN rail high powered contactor and use a Shelly to flip that on & off.

  • WiFi camera with scrub playback

    1
    0 Votes
    1 Posts
    89 Views
    No one has replied
  • Hubitat Elevation C-Series Controllers

    1
    0 Votes
    1 Posts
    147 Views
    No one has replied
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • LEDVANCE

    1
    0 Votes
    1 Posts
    150 Views
    No one has replied
  • Water Flow Meter & Shutoff

    1
    0 Votes
    1 Posts
    123 Views
    No one has replied
  • chine version of homeypro to convert 433 to IR,wifi,Bluetooth,866,..?/

    1
    0 Votes
    1 Posts
    178 Views
    No one has replied
  • Remote light switch

    2
    0 Votes
    2 Posts
    159 Views
    PablaP

    @swankgd you can use something like zooz remote switch and put a smart switch at the existing switch location. From there set an automation to toggle the state of the “real” switch whenever the button on the remote switch is pressed.

  • ESP32 / ESP8266

    12
    0 Votes
    12 Posts
    689 Views
    wmarcolinW

    @akbooer

    Third-party code, using Arduino I uploaded the code to program the WiFi on the board, and then installed the drives on Hubitat, very simple and fast.

    The part that was a little more complicated was the tuning of the valve, I used another digital meter for the initial reading and then adjusted in a simple way the conversion from pulses to liters that appears in Hubitat.

    (https://www.amazon.com/dp/B007NHS9M4?psc=1&ref=ppx_yo2ov_dt_b_product_details)

    Finally, I generated the device for the MSR, and then the world of play started, all exported to influxDb and Graphana.

  • Shelly i3 as a cheap scene controller for Openluup

    44
    0 Votes
    44 Posts
    4k Views
    akbooerA

    @akbooer said in Shelly i3 as a cheap scene controller for Openluup:

    I just so much wish that they produced a four button handheld controller.

    …and now, they do (well, not quite, it’s not handheld, but mains powered)…The (relatively) new Shelly Plus i4.

    Just received and installed one… the latest (beta) firmware is vastly different from the old i3s, but I configured it in the end. However, the MQTT function doesn’t broadcast to the generic Shellies/ topic, so isn’t recognised by openLuup at this time.

    Anyone else have experience of these devices? I missed the old Zwave Fibaro 4-channel input device, but this seems like an excellent replacement.

  • Hue dimmer as replacement for MiniMote remote

    5
    3 Votes
    5 Posts
    327 Views
    akbooerA

    Triggers in AltUI under openLuup are implemented as devices variable watches. The native Vera trigger route was never implemented under openLuup (because I believe that their implementation was hopelessly flawed.)

    There is now, in fact, a native openLuup implementation for triggers that doesn’t depend on AltUI at all, but can be set up and displayed under AltUI, and works somewhat differently from the Vera method, but they are basically variable watches. I could supply details of how to do this, if pressed, but unless you’re planning on configuring an openLuup system which doesn’t run AltUI (which is certainly a feasible thing to do) then I wouldn’t bother.

  • UZB Stick - Moving from Z-Way to Z-Wave JS

    2
    0 Votes
    2 Posts
    563 Views
    PerHP

    Github discussion for future reference.

  • Intercom Buzzer wiring with Shelly Plus 1

    3
    0 Votes
    3 Posts
    2k Views
    M

    Thank you.

  • Any decent destination for a Vera Plus?

    34
    0 Votes
    34 Posts
    2k Views
    CrilleC

    @parkerc The old unmaintained one from damianxd is in fact working fine with openLuup but it's not very efficient as it polls very frequently. I'd go the MQTT path as well with Mqttthing.
    The only downside I see is that openLuup must be set to publish every variable update which for me causes a lot of unnecessary traffic.

  • List of smart devices with no cloud requirement

    1
    0 Votes
    1 Posts
    246 Views
    No one has replied
  • Z-wave serie 700 Europe/ Reactor/ Home Assistant

    10
    0 Votes
    10 Posts
    533 Views
    S

    I must says, having homeassistant solely with 80 devices in zwavejs connected to an aeotec gen5+ has been rocksolid for very long! I even started with the former openzwave (beta) integration in homeassistant and had to rename all entities 1 time after migrating. Since then rocksolid and combined with node red a pleasure to automate...

  • HVAC Control

    8
    0 Votes
    8 Posts
    506 Views
    A

    I have a setup that works quite nicely for controlling my "mini split" HVAC.
    It is a quite old unit that is more or less totally stupid, it has a remote and that's it.

    Some time ago I put together a Tasmota IR device that can control quite a few different HVAC units including mine. Pretty cheap, not too difficult to build and with a nice case it looks ok.

    One nice aspect of the Tasmota solution is that both receives and sends IR so I mounted the IR Transciever close to the HVAC so that it also recieves commands from the IR remote. Another upside with the Tasmota route is that it is independent of what hub one uses since it is Wifi and Mqtt.

    The next question was how to control it. With the help from @therealdb and his excellent VirtualDevices plugin together with the Mqtt capability of OpenLuup I managed to get a working solution in place.There is some information in the Mqtt Bridge thread on this.

    Since I use Homewave the next logical step was to be able to control it from inside Homewave. A few dimmers with fixed steps and a Reactor with some logic and I got something working in place to control on/off, temperature and mode.
    Not the prettiest solution but it does the job. The limitations in the old Vera gui and device types do show.
    42532144-7ce0-44b3-a315-7144ff4a13e9-bild.png

    After recently having started playing around with Home Assistant I found a really nice integration for Tasmota IR HVAC control. It was really easy to get in place, it looks quite nice and can control most/all of the functions on the HVAC.

    a73a0416-93a1-4e7d-b72d-3b31dd954791-bild.png

  • Can a Ezlo Plus be bridged to a Vera Plus

    2
    0 Votes
    2 Posts
    222 Views
    therealdbT

    MSR is the best route at the moment. You could easily use it to map your Ezlo devices to virtual ones in Vera. If you need virtual devices, try the ones in my signature. Despite its name, you could use them as Virtual Devices with no HTTP actions attached and ge the change in status in MSR. Not trivial, but your simplest route at the moment.

Recent Topics