Mode-selector / multistate device

[cherowley]

Hello again!

I think I've found another problem.

When using this command in a lua script, the device never goes off

commandArray['Kitchen TV']='Set Level 10 FOR 1' -- turn kitchen TV on

Level 10 is the tv on, level 0 or off is tv off...

Any ideas?

Only tried using that as i can't set the off delay value either

Ah well, i'l have to set all the other switches up again and remove the selector unless someone can help, booo!

[raym]

Hello.

I'm noticing a slight delay when using multistate switches compared to regular switches (I'm on the latest beta).

I am using a multi-state device to control a physical Z-Wave dimmer via JSON calls. JSON operates instantly when I call the commands directly in my browser. Through the switch though, there's a 0.5-1 sec delay between mode selections.

In the log, regardless of which button is pressed, I see multiple lines like this:

Code: Select all

2016-03-06 22:42:54.884 User: Admin initiated a switch command
2016-03-06 22:42:54.884 OpenZWave: Domoticz has send a Switch command!, Level: 99, NodeID: 3 (0x03)
2016-03-06 22:42:54.884 (Z-Wave Controller) Light/Switch (Office Light X)
2016-03-06 22:42:55.121 (Z-Wave Controller) Light/Switch (Office Light X)
2016-03-06 22:42:55.273 (Z-Wave Controller) Light/Switch (Office Light X)
2016-03-06 22:42:55.432 (Z-Wave Controller) Light/Switch (Office Light X)
2016-03-06 22:42:55.508 (Z-Wave Controller) Light/Switch (Office Light X)

Is it possible that this logging is causing unnecessary overhead and delay? Why is the Light/Switch called repeatedly like this for a single multistate button press?

Any help appreciated.

[panomi]

I am missing the selector levels when i want to create a scene with a selector. Is this in the scope of future updates?

Or is there an other way of inserting a selector into a scene. For the time being i created a virtual switch with the same action commands

dSceneMissingSelectorLevels.png

I second this.

I've used this json code to add it to the scene but it's not working.

Code: Select all

/json.htm?type=command&param=addscenedevice&idx=6&isscene=true&devidx=427&command=On&level=10

Would be nice to see this feature in an upcoming release.

[julianmclean]

Just found this thread and updated to latest beta (3.4834) to use selector switches, as these will be really useful in simplifying some of my logic for managing various things such as house "modes", presence of individuals (at home, nearby, far away), etc.

However, one thing I wanted to use it for was to have a single switch representing my 24h cycle states (e.g. day, evening, bedtime, asleep). Whilst these states can be forced manually (e.g. when button pressed to move to sleep state for an early night), in general they are timed events - e.g. move from day to evening at 7pm, then bedtime at 10pm, sleep at midnight, etc).

I have tried setting up Timers on a test switch to set the switch to one of the specific states at a given time, but it doesn't see to have any effect. I can make it work in a LUA time script, but it would be good to have in native UI. Has anyone got timers working with selector switches, or do I need to raise an ticket?

[Number8]

I have tried setting up Timers on a test switch to set the switch to one of the specific states at a given time, but it doesn't see to have any effect. I can make it work in a LUA time script, but it would be good to have in native UI. Has anyone got timers working with selector switches, or do I need to raise an ticket?

Pretty strange. I have several timed selector switches that are working smoothly. Currently running 3.5259 on Rasp PI