Make Sub/Slave/Unused devices accessable in scripts

Use this forum to discuss possible implementation of a new feature before opening a ticket.
A developer shall edit the topic title with "[xxx]" where xxx is the id of the accompanying tracker id.
Duplicate posts about the same id. +1 posts are not allowed.

Moderators: leecollings, remb0

Post Reply
yfands
Posts: 67
Joined: Monday 04 July 2016 10:16
Target OS: Raspberry Pi / ODroid
Domoticz version: latest B
Location: Netherlands
Contact:

Make Sub/Slave/Unused devices accessable in scripts

Post by yfands »

Hello I posted my question on Monday 04 July 2016

The Question was: I'm trying to get the state of a Sub/Slave device in a lua script, but it seems that Sub/Slave devices can't be accessed?
am I doing something wrong ?
Regards,
Frank

So no replies where in order, and I am (still) not able to use the Sub/Slave/Unused devices in a script, so hereby I want to make the suggestion to make all devices used/unused/sub and slaves accessible in scripts..

Why?

The SI1145 Sensor returns 3 values: UV, Visible, IR (luminosity)
The UV value is no problem, in combination with MySensors Domoticz can 'recognize' the sensor and act accordingly.
The Visible and IR values have no suffix, the are a 'counted' value (0...65535).

And because Domoticz cant handle the MySensors S_CUSTOM and V_VALX values. I was searching for a alternative.
So I made a S_INFO with V_TEXT sensor. But this is a list only with values, no historic graph can be made.
With DUMMY Sensor created a Custom Sensor and with a lua script I copy the V_TEXT value In the Custom Sensor Value.
But, The Info sensor has to be 'in use' and shows up on the utility tab, next to the Custom Sensor :-(. The Info Sensor is , in this case, a helper and should not be visible. But doing a set_unset Info Sensor makes the 'device' invisible for the scripts.

Regards
Frank
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest