Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.

Global Moderators

Forum wide moderators

Private

Posts


  • Time series documentation
    toggledbitsT toggledbits

    @tunnus Not entirely. I need to spend some time on that. As the post suggested, comment out or remove your retention configuration value. It will be computed from interval and depth.

    Simple moving average:

            -
              id: temp_sma
              name: "Outdoor Temperature Average"
              capabilities:
                value_sensor:
                  attributes:
                    value:
                      model: time series
                      entity: "weather>home"
                      attribute: "wx.temperature"
                      aggregate: sma
                      interval: 60  # minutes
                      depth: 5
                      precision: 2
              primary_attribute: value_sensor.value
              type: ValueSensor
    

    Rate:

            -
              id: garage_humidity_rate
              name: "Garage Humidity Change Rate"
              capabilities:
                value_sensor:
                  attributes:
                    value:
                      model: time series
                      entity: "mqtt>garage_handt"
                      attribute: "humidity_sensor.value"
                      aggregate: rate
                      interval: 30  # minutes
                      depth: 3  # last three samples, t-0, t-30, t-60
                      precision: 2
                    units: "%/min"
              primary_attribute: value_sensor.value
              type: ValueSensor
    
    Multi-System Reactor

  • Zigbee2mqtt installed! sytemctl not happy :(
    CatmanV2C CatmanV2

    FFS!

    User=pi
    

    Looks like it's fixed

    C

    Zigbee

  • Zigbee2mqtt installed! sytemctl not happy :(
    CatmanV2C CatmanV2

    Good call. Syslog:

    Dec 16 12:30:09 openluup systemd[1]: Stopped zigbee2mqtt.
    Dec 16 12:30:09 openluup systemd[1]: Starting zigbee2mqtt...
    Dec 16 12:30:09 openluup systemd[2984]: zigbee2mqtt.service: Failed to determine user credentials: No such process
    Dec 16 12:30:09 openluup systemd[2984]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
    Dec 16 12:30:09 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
    Dec 16 12:30:09 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
    Dec 16 12:30:09 openluup systemd[1]: Failed to start zigbee2mqtt.
    

    Same message in all of them 😞

    zigbee2mqtt doesn't even log when started from systemctl

    C

    Zigbee

  • Zigbee2mqtt installed! sytemctl not happy :(
    toggledbitsT toggledbits

    Have you looked in the logs in /var/log for other messages? Usually there's a good bit more chatter there that can be helpful.

    Zigbee

  • Any thoughts on which is better
    CatmanV2C CatmanV2

    Further testing, I need a router decvice as by the time I move the sensor two floors down it stops responding, but I was pretty much expecting that. I can probably do something with the positioning of the dongle on its extension as well.

    C

    Zigbee

  • Any thoughts on which is better
    CatmanV2C CatmanV2

    Much awesomeness. My test sensor is paired and showing in HA and MSR.

    Ta all

    C

    Zigbee

  • Zigbee2mqtt installed! sytemctl not happy :(
    CatmanV2C CatmanV2

    Hello oh great ones.

    After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi

    Can connect to the front end and everything 🙂

    Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:

    [Unit]
    Description=zigbee2mqtt
    After=network.target
    
    [Service]
    Environment=NODE_ENV=production
    Type=notify
    ExecStart=/usr/local/bin/node index.js
    WorkingDirectory=/opt/zigbee2mqtt
    StandardOutput=inherit
    # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
    StandardError=inherit
    WatchdogSec=10s
    Restart=always
    RestartSec=10s
    User=pi
    
    [Install]
    WantedBy=multi-user.target
    

    Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.

    Running manually pnpm start

    in /opt/zigbee2mqtt works fine

    However:

    catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
    Job for zigbee2mqtt.service failed because the control process exited with error code.
    See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
    

    Which I have

    catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
    ● zigbee2mqtt.service - zigbee2mqtt
       Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
       Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
      Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
     Main PID: 3093 (code=exited, status=217/USER)
    

    and

    -- A start job for unit zigbee2mqtt.service has begun execution.
    -- 
    -- The job identifier is 17477.
    Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
    Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
    -- Subject: Process /usr/local/bin/node could not be executed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    -- 
    -- The process /usr/local/bin/node could not be executed and failed.
    -- 
    -- The error number returned by this process is ERRNO.
    Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
    -- Subject: Unit process exited
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    -- 
    -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
    -- 
    -- The process' exit code is 'exited' and its exit status is 217.
    Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
    -- Subject: Unit failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    -- 
    -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
    Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
    -- Subject: A start job for unit zigbee2mqtt.service has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    -- 
    -- A start job for unit zigbee2mqtt.service has finished with a failure.
    

    Which strikes me as very odd.

    Any blindingly obvious things I'm missing?

    TIA!

    C

    Zigbee

  • Single protocol?
    toggledbitsT toggledbits

    @Pabla said in Single protocol?:

    When you make the switch give the new ZWA-2 Z wave antenna a try, it will fix a lot of any lingering problems.

    That is exactly where I am headed. Most of the "complicated" devices in my mesh that were on Vera (scene controllers, notably, but also multi-sensors and some devices that were causing issues there) have been moved to a 500-series Z-stick controlled by Z-WaveJS, and I will migrate everything to the ZWA-2 when I get it (on my Christmas wish list, so if it's not under the tree, I'll just gift it to myself after). I have to confess, despite its issues and the horrible ending that Ezlo has given the product (and the tremendous face-in the-dirt failure that their supposed replacement products have been), I remain sentimental. So much wasted potential. Alas, we move on.

    Edit: just now, to illustrate:

    6b950965-5658-45f5-aa89-50ef098cf2ea-image.png

    General Discussion

  • Single protocol?
    therealdbT therealdb

    As you may already know, I'm heavily invested in Zwave (70+ devices at the main house, 40 in the beach one), curious towards Shelly Wifi (4-5 devices added when using Vera, that I'll eventually ditch for Zwave) and slowly starting interest in ZigBee.

    I find Zwave life after Vera to be definitely better and the mesh still more stable than Zigbee or WiFi.

    I've started a new journey to learn more about Matter and I've recently started working on a matterbridge plugin to call HTTP endpoints as in the old ha-bridge days. Problem is, while Matter may seems a standard, vendors have their own preferences over implementation, with the result that support is not complete and you'll see ridiculous constraints, such as no more than 20 matter devices supported on your Alexa network.

    We'll see, I avoided tuya because of cloud links and the only cloud-only things I have are my Nest thermostats, bought when I was thinking that it will eventually become less important, because they were the only thermostats that were good to show. Today, I'll not buy them.

    All that said, my older Zwave devices are 10 years old and apart 2-3 I had to replace because of relay that stops working, all is good and mesh is stable as it has never been, thanks to ZWA-2.

    General Discussion

  • Single protocol?
    toggledbitsT toggledbits

    I'm also in the Z-Wave camp, with about 100 devices in my mesh. I still have some on Vera, so I actually have two Z-Wave networks active in my home. There's no question that Vera was a big contributor to problems with early Z-Wave experience. Even my oldest devices run well under Z-WaveJS. Multi-sensors that needed battery changes monthly on the Vera run for months without a change on Z-WaveJS (I suspect Vera's frequent restarts and "configuration" of each device each time are to blame). With the rapidly-declining stability of Ezlo's Vera cloud infrastructure, especially Alexa issues of late, I'm planning on being entirely off before March 1.

    I've definitely had a few Z-Wave devices give up the ghost (or the radio); mostly older devices from lesser manufacturers of the time. The largest single group of switches and dimmers I have are all Leviton and around 11 years old, and I've only had one fail (radio died, otherwise functional). GE/Jasco seems to have held up second best among the high-age devices. Many of the other brands didn't make it two years, and those brands no longer exist, too. Everything I've bought in the last 4-5 years is holding on well. I think Zooz gets the award for most-improved. I didn't think much of them a few years ago (and told them so), but their more recent offerings have been stable and well-supported.

    Part of the recent stability may be due to a campaign I went on several years ago (bored during Covid), where I found and fixed a number of small electrical problems in my house resulting in a variety of neutral issues (that is, issues with excessive current on the neutral wire). One of the most egregious was that our clothes dryer had been installed by the delivery guys to our four-wire connection with the neutral and ground bonded inside the dryer -- the bonding wire should have been removed for the four-wire service. This resulted in some fairly high circulating neutral and ground currents throughout the house, and in combination with other problems found (loose neutral or ground wires at receptacles, for example) was potentially hazardous and may have led to the failure of those less-robust devices. As I said, the last few years, I don't recall replacing any devices, so I've either eliminated a source of induced failure, culled out all of the weak, or both. I also have whole-house surge protection on my main panels. When my Internet was cable-carried (it no longer is), I had surge/lighting protection at the entrance.

    I'm not enthusiastic about WiFi as an HA protocol for a few reasons: power demand, crowded bands, and user knowledge/security. While I love the simplicity of the Shelly WiFi-based devices and use them without reservation, they do not compare in battery life to even the oldest of my Z-Wave devices (well, those no longer on the Vera). The powered devices are fine. Powering many WiFi devices also seems to be "unevolved" -- Shelly gives you terminal connections for line voltage when powered; most others are USB micro or C at 5V with a wall wart, which truly sucks, and finding small UL-listed power supplies that can (and must be) safely installed in a US single-gang box or other enclosure is a nuisance and would make an insurance adjuster throw down his clipboard and walk out. WiFi generally is in increasingly crowded bands. In my neighborhood, the list of WiFi networks I see anywhere in my home that are at -60db or higher (i.e. strong) is long. While it used to be that unsophisticated users would simply crowd onto whatever preconfigured channel their router used by default and I could avoid them by changing channels, newer APs and firmware seek out the less-crowded channels automatically and spread out, so now every channel has a dozen competing networks at 2.4Ghz (relatively few I've found can do 5Ghz). Z-Wave's band has actually become less crowded over time (my neighbors finally abandoned their 20-year old cordless phones, I guess). Configuration and security also becomes an issue: rare is the home user that understands that IoT devices should be isolated from the rest of the network. Their eyes glaze over when you talk about VLANs, firewalls, and DMZs. They don't understand IP addressing, and will use the default /24 subnet their router offers and the small dynamic DHCP pool until the day they add that last Shelly device and now the wife's phone can't get an IP address when she comes home, etc. They will run their vendor-supplied AP at 100% with half-a-dozen 4K WiFi camera streams and wonder why their "Internet" is always slow (they don't even understand the difference between their Internet access and their WiFi network). There's a learning curve to building a solid, secure IP network with WiFi that most users have been shielded from forever and (were told) needed to know nothing about, but if you're going to start putting dozens of IP/WiFi devices on your home network, you'd better learn it and know it and do the work it takes to do it right at scale, or it will bite you hard from the inside or worse, the outside, soon and often.

    I've got some BLE in my network as well, and it works well for its purpose (mostly presence sensing). I remain curious, even intrigued, but...

    The biggest issue I find, and what I would guess-timate is the biggest barrier to finding a "one protocol to rule them all" today, is that there are no manufacturers that cover the full spectrum of required devices on a single protocol. Nobody makes everything you want, regardless of protocol. So we're left to find the best of breed in each category. I don't see that changing any time soon, or really, ever. The manufacturers follow the money. Smaller manufacturers like Zooz will make a good business out of filling holes that the big guys don't want to address (looking at the ZEN-32 for example). The big manufacturers will always make what they can sell the most, like switches and dimmers.

    Matter, HomeBridge, and the like... they are effectively controlled by large corporations that are explicitly disinterested in working with small developers. Claiming open source while you maintain a closed, expensive, and opaque certification process doesn't fly for me. Z-Wave, admittedly, shares some of these ills in its proprietary history, but has been evolving to increasingly open over the last five years, with multiple vendors now producing silicon and that competition driving lower cost to implement. Z-Wave is also pretty much a single-interest ecosystem, where Google, Apple, Amazon, Samsung, and others involved in the likes of Matter and HomeBridge have many areas of research and development, and have been shown to quickly and suddenly divest themselves of technology they decide isn't worth continued effort. The players here have been bad actors in the past; I have no reason to believe they will behave differently in future.

    Like others have said, beware the cloud. Eschew the cloud. It's sometimes a necessary, unavoidable evil, but you'd best minimize it.

    General Discussion

Member List

CatmanV2C CatmanV2
therealdbT therealdb
toggledbitsT toggledbits
akbooerA akbooer
DesTD DesT
rafale77R rafale77
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved