Re-Write documentation

[marcus-j-davies]

@crxporter,

Meanwhile, is there anything I can do to give back to the project?

😁

The readme for this module, is fairly big: multiple usage modes, guidance on mode usage, Managed Command Class specifications/param requirements, Managed params object structures , a sizeable change log, User Interface guide, the possible events table etc etc.

How do you feel getting involved with re-doing that (maybe branch of to Wikis - with the read me being more of an introduction)

If you prefer to get more involved on the code side - please do.

if you want to take on re-doing the documentation, I am more than happy to giving you write access to the dev branch, and adding you as a contributor. 👍

If so - I suggest absorbing the read me(s) as they currently are to understand what needs to be documented.

Have a think.

Let me know if 3.4.0 works well for you - local tests were fine.

[crxporter]

Ah yes, docs. My specialty actually... play with everything then write about what it does.

I think I can help. I won't have much time this week, but I'll be thinking about it.

[marcus-j-davies]

No worries at all, not expecting this to be an overnight thing, if you do get involved let me know, and I'll add write permissions for you.

Let me know if you have any problems with 3.4.0. It should run well.

[crxporter]

I can do it with write permissions or just fork and make edits on my own branch.

I'll be testing the new version this weekend when I get home

[marcus-j-davies]

Hey, Nothing Major.

Bit if you do device to help with re-doing documentation (again no rush what so ever), Fork/push to the dev branch.
The dev branch is my WIP - so is usually updated with the latest documentation.

[crxporter]

So yeah it'll be really a while before I get back to this... yesterday a lightning strike took out my whole network and about half my zwave.

So - as you could guess - I'll be spending most of my free time for the next months dealing with that.

[marcus-j-davies]

Hey man, no sweat!
Its just a "will be nice to do at some point".

But the job is yours, if you should ever want to get involved - no rush.

Oh Dam!
hope not too much damage?

A friend in the states, where he lived next door to his parents - he routed coper cables between the 2 house (networking).
His parents house, got taken out by a strike, and due to the copper cabling - it took out his entire infrastructure.

[crxporter]

Damage seems to be mostly focused on Zwave and my extensive wired network.

Dead includes: Unifi dream machine, cams, switches, access points, one tv, all 3 Apple TV's, home theater receiver... insurance inspection is tomorrow. I hope they are generous.

[marcus-j-davies]

So,

If you're looking for some internal camera replacements, these are Apple Homekit Secure video enabled + Pan/Tilt wifi cameras at £48 GPB. - Just ordered 2 of them.

https://www.amazon.co.uk/Security-Assistant-Compatibility-Tracking-Required/dp/B086KZ8X6S

Watching/reading reviews seems that these are really really really good for the price point - given the extensive features.

They are capable of 2K Rez (1K for Secure Homekit - limitation on apples part).

Will be testing them tonight

EDIT:
They come 2nd on iMore
https://www.imore.com/best-homekit-cameras

[crxporter]

I'll probably just replace them for exactly what I had before - unifi cams. I like having the onsite storage and it's easy enough to get them in homekit using nodered!

I think the only change I want to make compared to what got destroyed is a different home theater receiver. Any favorites for 7.1 in the theater and stereo in a second zone? Bonus points if zone 2 works with airplay 2!

[crxporter]

Update from Texas: big stack of Zwave 700 toys just showed up! It'll be party time tomorrow.

[crxporter]

The 700 setup is alive and well. Only had to make 2 very small changes for my code to work with the new switches, which apparently are sending duration updates to the same command class as on/off or dimmer level...

No real noticeable changes so far. I'm at 50 devices including the controller so I don't know that I ever hit traffic levels where more speed is needed. Sure does have me itching for more 700 devices though 🤦‍♂️

[marcus-j-davies]

Hurray!

I bet its nice to have it all back up?

are you running the latest plugin version (3.7.1)
There has been a few fixes to the underlining Z-Wave driver - not sure if what was fixed, the 50 possible nodes were affected anyway - but you never know.

[marcus-j-davies]

which apparently are sending duration updates to the same command class as on/off

The BinarySwitch & MultiLevelSwitch zwave classes do support the Duration object.
But some devices, prefer having a set duration in a config param or something to that affect, instead of including it in the Set command its self, which means they may only support older versions of the classes

let MyDuration = {
  Duration: {
    value: 5,
    unit: "seconds" | "minutes",
  }
}

let Message = {
    payload: {
        node: 17,
        class: "MultiLevelSwitch",
        operation: "Set",
        endpoint: 1, // only needed for some multi switch devices (defaults to 0)
        params: [75, MyDuration]
    }
}
return Message

[crxporter]

Yes it's great to be back running.

I did update to 3.7.1 before the changeover, everything went smoothly. I just have to learn to use the new devices a bit.

Side note- this is the first time I've done 100% of the setup inside of nodered, my last stick was actually programmed originally using openzwave then ran in zwavejs2mqtt and finally nodered. I enjoyed doing it all fresh from the nodered interface.

And finally for duration, yes I send duration like that. For some reason though when controlled at the switch, my new dimmers are sending a duration message back to nodered. Not a problem, I just put a condition to ignore that message in my flows.

[marcus-j-davies]

I enjoyed doing it all fresh from the nodered interface.

nice to hear - though I cant take credit for that one, I am however, looking to tidy up the UI at some point, to.

• Cash in on some enhancements with the node i have made
• Introduce Association mapping.