So one new device, onOnly,

use case when you only want the DON signal, which is often used for motion sensors.

Mostly valuable in scenes where you only want it to turn the scene on and never off.

I am using it to turn on a light which is turned off by a timer, so it is triggered by a scene which

control comes from a door sensor. This filters out the closing of the door.

The rest of the updates are back office, part of the modernising of the code. Comments, tests,

refactoring. Should make the code easier to maintain by me or someone else if I get hit by the

Beer truck.

So far my device adds are selfishly those I use. I have been careful not to break those which I don't use.

These include the Temperature, Dimmer/Generic. Temperature seems pretty clunky in its present form,

I'm open for improvements or for splitting the functionality. For example I know its being used to check

upper / lower values. We could split that into a new device and add control limits which trigger DON / DOF,

or do some kind of average over time. Or if you are real fancy, send to csv file which can be plucked by the

ISY's web page. Just ideas, again, not in my current use case, just saying its not hard to make happen.

This is one of the rare plugins which is not just an interface to external hardware, its more about language

extension for the ISY.

Take a look at the docs please, I want some feedback if its clear with the "hat" of a new user:

README  &  CONFIG

Enjoy; try to break it, and let me know what you think!

VERSION = "3.1.25"

"""

3.1.25

DONE add onOnly device

DONE update generic project files

DONE Controller comments, refactor checkParams

DONE change hints for temperature devices

DONE testing added

2 minutes ago, sjenkins said:

This is one of the rare plugins which is not just an interface to external hardware, its more about language

extension for the ISY.

That's the appeal of this plugin for me. It also makes a case for allowing a "minimal" mode where only a trigger is provided, allowing our own program to then do whatever logic we want. Additional baked in functions are nice, as long as their use is optional. I like that.

Interesting that you came up with the onOnly function, literally 2 days ago I was reconfiguring a few Insteon motion sensors by adding jumper 4, to have them send On only signals. This is to allow retriggering the on timing in a program as long as there is movement. Having a virtual on only device will allow similar functionality with other types of triggers, nice.

So it will produce On control events? I'm asking because I did notice that in the case of virtual switches, they don't produce control events, only status. At least if I switch one from admin console.

Should be producing control events too. Test out with a scene or program, the button will trigger a program but not always a scene. Why you say? No idea.

Feel free to post here any anomaly on a device. I am using them except temp and know they work in the field but maybe there is an edge case.