Software

786 Topics 7.8k Posts

Subcategories


  • 17 Topics
    125 Posts

    Hi

    Bought a new ZB device, an EV charger.
    I was aware that there would one manufacturer specific cluster that wouldn't work out of the box, but several other clusters I hoped would work from start does not. Or at least there isn't any enteties for them.

    So I have tried to study how to write a local quirk, but it is a bit overwhelming for mt brain.
    Usually I can manage do get stuff moving with intense googling, finding guides or different solutions that I can start from, but here I find nothing that I can wrap my head around.
    My latest try was to chat with Gemini AI 😰 (programmers, rest assured that your job will be safe for the foreseeable future 😁 )

    I have gathered my device Diagnostic Info.
    I have manufacturers ZB documentation.
    A device support request is created on zigpy github (no response the last weeks)

    For now there is just two entities for my device, on/off switch and energy sensors.

    All non manufacture attributes and commands seems to be recognized in ZHA "Manage this Device"
    It would be great if I could get some entities out of them.
    For example the entity for manage charging power is expected to be presented as a dimmer slider.
    But why isn't there any entity created??

    The manufacture specific cluster is more of nice-to-have and could maybe be solved another day.

    Any help would be much appreciated. 🙏

  • 701 Topics
    7k Posts

    If I refresh that Tools-page, it'll go to Status-page

  • 40 Topics
    543 Posts

    That’s a really interesting read – thanks!

  • zwave-js-ui: minimote and MQTT topic

    1
    0 Votes
    1 Posts
    74 Views
    No one has replied
  • Any interest in a Subcategory for Homebridge?

    14
    0 Votes
    14 Posts
    446 Views

    Thank you for the post. I have been searching for the answer for the same question.
    Thank you so much

  • Light automation thoughts

    37
    0 Votes
    37 Posts
    1k Views

    @akbooer cool ta. Certainly there are many options!

    C

  • 0 Votes
    15 Posts
    636 Views

    I did not have the latest version 23011. Updated the controller.

    Unknown nodes are no longer showing up.

    FYI - The %(#77bb41)[WARN]ings for node 25-x came from the Aeotec Siren 6. I unpaired it and repaired it and there are still showing in the log. in case that helps you.

    Thanks

  • This topic is deleted!

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

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

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

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • DynamicGroupController Feedback

    15
    0 Votes
    15 Posts
    406 Views

    @Snowman said in DynamicGroupController Feedback:

    Forgot to mention it requires double quotes.

    Actually, it's a good idea to surround the entire expression in quotes, since expressions often contain special characters that YAML doesn't want to digest.

    In this case, that means you'd have quotes in quotes, which is fine, as long as they are different. In the expression itself, the expression language doesn't care if you use single quotes or double.

    filter_expression: "entity.attributes.x_hass.state == 'on'"

    But I really think @Pabla 's form is the best... that's a special feature of YAML that works really well for expressions, so if you want to avoid headaches, write all your expressions the way he showed.

    filter_expression: > entity.attributes.x_hass.state == 'on'

    In this case, everything idented under filter_expression is taken as part of the expression, so you can write multi-line expressions easily, too...

    filter_expression: > entity.attributes.leak_detector.state && entity.attributes.temperature_sensor.value < 35
  • Temperature set point changes un-expectedly

    6
    0 Votes
    6 Posts
    216 Views

    @toggledbits said in Temperature set point changes un-expectedly:

    but that log entry in openLuup's log doesn't look like an action to me, it looks like a response

    Exactly so.

    No evidence that anything in openLuup itself triggered that. Yhere's no HTTP request from an external source either. But anything could have changed the variable.

    Indeed odd.

  • Zigbee2MQTT

    5
    0 Votes
    5 Posts
    144 Views

    Yeah, I'm keen to try microwave ones

    C

  • Owntracks / Mosquitto String updates unexepectedly.

    Solved
    24
    0 Votes
    24 Posts
    756 Views

    @therealdb Dude you owe me nothing

    C

  • Mosquitto and Owntracks

    33
    0 Votes
    33 Posts
    1k Views

    Thanks. All of the checkers I tried on initial setup claimed it was OK. Still wouldn't work though.

    Whatever you chose is fine with me. Just another skill I need to understand 🙂

    C

  • Device that comes on on Openluup restart

    5
    0 Votes
    5 Posts
    143 Views

    @akbooer Isn't that a toggle request though, and the next line saying the Target is zero(i.e. off)

    C

  • Hypothetical file system monitoring question

    5
    0 Votes
    5 Posts
    124 Views

    Thanks. I'll start there!

    C

  • Any HomeSeer users here?

    2
    0 Votes
    2 Posts
    126 Views

    Yes, using both HS3 & HS4. Not an expert but then again it easy to use as it is without tweaking.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    62 Views
    No one has replied
  • Syncing of updates...

    1
    0 Votes
    1 Posts
    115 Views
    No one has replied
  • Strange MSR behaviours after NAS reboots

    8
    0 Votes
    8 Posts
    279 Views

    I think I have a real solution for this. As part of the work on ZWaveJSController, I had to make some changes (fairly significant) that I think would stabilize entities when controller initializations are slow as you are seeing here. Most Reactor restarts occur when the hub is already running, but as you've found out, when everything comes up at once, there are nearly infinite ways things can be out of sequence or temporarily missing. Since Z-Wave and its devices can be so much more unpredictable than a running hub, at startup and during normal operation, some changes were needed. The ZWaveJSController testing folks have been using a separate version of Reactor that contains these changes, which I myself have been using for months, and I haven't heard of any issues that could be related to those changes, so I think it's about time I can bless them and put them into the mainline code branch and releases. Perhaps within the next week or so.

    By the way... five minutes to restart Hass? Whiskey tango...

  • ezmqtt switch control questions/issues

    15
    0 Votes
    15 Posts
    422 Views

    Got it. Will fix that later today.

Recent Topics