Domoticz

dannybloe wrote: And, the question is: should events be triggered when you switch Master and Slave(s) are synced? I'd say yes. When a device changes, ALWAYS trigger scripts.

On top of that, the nValue isn't something you should be using in dzVents I guess as I hope all devices have more sane/readable attributes.

jvandenbroek wrote:Yes, danny described it thorough. Conclusion for now: Only switch master through slaves only, not directly or via scripting. The trick in this case would probably just adding a second slave and use that for the timer.

Milifax wrote: Ok, noted. But, out of curiosity, why is there a nValue available in Dzvents as mentioned on the wiki and why isn't it displaying the correct information, or equal information as in the db?
Wiki --> nValue: Number. Numerical representation of the state.

Milifax wrote:

jvandenbroek wrote:Yes, danny described it thorough. Conclusion for now: Only switch master through slaves only, not directly or via scripting. The trick in this case would probably just adding a second slave and use that for the timer.

Could you explain that a bit more?
Bot, master and slave, are devices which are triggered from a message to RFLink. How can I add an extra slave. If I want to do that Domoticz says it is already in use.

jvandenbroek wrote:

Milifax wrote:

jvandenbroek wrote:Yes, danny described it thorough. Conclusion for now: Only switch master through slaves only, not directly or via scripting. The trick in this case would probably just adding a second slave and use that for the timer.

Could you explain that a bit more?
Bot, master and slave, are devices which are triggered from a message to RFLink. How can I add an extra slave. If I want to do that Domoticz says it is already in use.

Isn't it possible to add a dummy slave next to the rflink slaves and use this one to switch on/off through scripting (dzVents)? Not tested, just an idea..

jvandenbroek wrote:Ah I understand what you mean. You should create a dummy device as master and add both RFLink devices as slaves to it. Now you should get the correct status on the dummy device..

Edit: Well I think I understand it, is it correct that you have 2 RFLink devices, one only triggers when door is open and the other when door is closed? And do they sent the correct On and Off status, or both the same (always On or Off)? If the latter is the case, you should use a script and not master/slave devices.

Milifax wrote:

jvandenbroek wrote:Ah I understand what you mean. You should create a dummy device as master and add both RFLink devices as slaves to it. Now you should get the correct status on the dummy device..

Edit: Well I think I understand it, is it correct that you have 2 RFLink devices, one only triggers when door is open and the other when door is closed? And do they sent the correct On and Off status, or both the same (always On or Off)? If the latter is the case, you should use a script and not master/slave devices.

Nope no luck unfortunately,

the master swithes on once and stays on.
The dummy devices are always open if I log the states.

return {
	active = true,
	on = {
		devices = {
			'Achterdeur_Open',
			'Achterdeur_Dicht'
		}
	},

	execute = function(domoticz, device)
		if (device.name == 'Achterdeur_Open') then
			domoticz.devices('Achterdeur').switchOn()
		else
			domoticz.devices('Achterdeur').switchOff()
		end
	end
}

jvandenbroek wrote: I guess your hardware send On or Off for both states, but as different devices.

Then you could do something like this:.....

Don't depend on the nvalue, this is somewhat an 'illegal' way of obtaining the correct status.. Sure it may work for now, but might not in the future.

jvandenbroek wrote:Yes the GUI gets it's info from DB directly, so no strange behaviour here and all as expected -

Well then I'm out of options then, because the script above should definitely work if you've got 2 separate RFlink devices sending the On status (or Off, doesn't matter). But to be clear: We're not talking about one RFLink device sending always On, but 2 separate ones? Otherwise it would be much simpler, you could just toggle the state...

2017-08-04 15:14:08.399 RFLink: 20;DD;EV1527;ID=03b2c0;SWITCH=0e;CMD=ON;
2017-08-04 15:14:08.401 (RFLink) Light/Switch (Achterdeur_Dicht)
2017-08-04 15:14:10.658 RFLink: 20;DE;EV1527;ID=03b2c0;SWITCH=0a;CMD=ON;
2017-08-04 15:14:10.659 (RFLink) Light/Switch (Achterdeur_Open)

Milifax wrote:

jvandenbroek wrote:Yes the GUI gets it's info from DB directly, so no strange behaviour here and all as expected -

So why not get the right data that way? If only I knew how

jvandenbroek wrote: And the script should just work, period Just make sure you've got 3 devices (1 dummy, 2 RFLink) and maybe to be sure, first add the 'Achterdeur' as On/Off switch, not a Door type. Also check for On and Off status instead of Open / Close while testing this...

Milifax wrote:

jvandenbroek wrote: And the script should just work, period Just make sure you've got 3 devices (1 dummy, 2 RFLink) and maybe to be sure, first add the 'Achterdeur' as On/Off switch, not a Door type. Also check for On and Off status instead of Open / Close while testing this...

Believe me, tried it, tried it, tried it....
The script doesn't work, period and I think the reason is because the device only sends an On. Never an Off.

commandArray = {}
if (devicechanged['Achterdeur_Open']) then
	commandArray['Achterdeur'] = 'On'
elseif (devicechanged['Achterdeur_Dicht']) then
	commandArray['Achterdeur'] = 'Off'
end
return commandArray

jvandenbroek wrote: Doesn't matter, it just checks for a device change, not whether it's On or Off... Well then it could potentially be a bug in dzvents... And this in Lua?: