Recent Posts

Pages: [1] 2 3 ... 10
1
General / Re: Adding HA02 to Veraplus does not work
« Last post by John M. on Today at 05:38:12 am »
Hello Jim, am happy to see that you have this worked out.
Indeed sometimes, bringing it a little closer to gateway might do miracles. If you need any advice on the spot our tech team is at hand as well(see my signature)
2
Amazon Alexa / Re: Changing the Vera Modes with Alexa
« Last post by strojki on Today at 05:33:21 am »
Thank you guys, it helped. My problem was that I didn't know that House Modes Plugin exists, at all... This simplifies a lot of things.
3
Many thanks kwieto  :)

Cor
4
You can do several units in one scene. It can be done as you wrote, but I think more "elegant" way is to define all local variables at the beginning of the scene, individually for each thermostat, then use them throughout the scene.
The "Gosp_Target" and "Gosp_Current" are arbitrary taken names, you can replace them with whatever you like (i.e. Target_1, Target_2,... and Current_1, Current_2, ....)

You can omit all data preceded with "--" as it is a text information (comment), not used in the scene

the final code for two devices would be then something like following (devices ID's are 44 and 45, as from your example):

Code: [Select]
local Target_1 = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "SetpointTarget", 44)
local Current_1 = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint", 44)
local Target_2 = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "SetpointTarget", 45)
local Current_2 = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint", 45)

if Target_1 ~= Current_1 then
 luup.call_action( "urn:upnp-org:serviceId:TemperatureSetpoint1", "SetCurrentSetpoint", {NewCurrentSetpoint = Target_1}, 44)
end

if Target_2 ~= Current_2 then
 luup.call_action( "urn:upnp-org:serviceId:TemperatureSetpoint1", "SetCurrentSetpoint", {NewCurrentSetpoint = Target_2}, 45)
end

Remember that variable "Gosp_Target" was replaced by respective "Target_1" and "Target_2" also in the luup.call_action... part of the code ("NewCurrentSetpoint" part)
5
General / Re: My Modes, Does it Make sense?
« Last post by Nettuno on Today at 05:13:43 am »
#Eco
you are right, "My Modes" is a meaningless and invasive function, it is in no way customizable, as if the average life was remote control with 4 functions .. (then I would like to know who uses Vacation) ???
In my opinion, the intention was good, but they wanted to please someone who does not understand us ... and now they fall into the mistake instead of focusing on development.
Vera app does not offer any useful, interface has a huge face and shield and no set mother scene. Try using Imperihome app, it's definitely more complete and customizable  ;)

#Don Phillips
Hi, I have more or less your own functions, 8)
- Protection (when my family is at home, armed external sensors)
- Night (lowers temperature and, arming cameras)
- Arm
- Disarm
- Open Doors (Prepare "day or night" protection and open doors)

but thanks to the fact that I abandoned My Modes, I could better articulate a lot of automatisms.
As for the "Locator" function is a simple association, it would be enough to apply it to a "Favorite" scene
6
General / Re: Fibaro button vera support...?
« Last post by John M. on Today at 05:13:00 am »
@amg0 - I was checking this with the FAE team, and the problem is because when we did integration, we've done it using a certain revision sample of that device, which we got from Fibaro. In the meantime, there are newer revisions there, which also affected the z-wave command classes. Once we have the new samples on our hands (Fibaro regularly supplies us with them), additional functionality will be added.

Initial samples we developed on had full capabilities, with up to x5 presses.

@NenneJKG not sure what the problem might be, as your fw version should contain the wizard for this device. I would advise logging a ticket with our support team, see details in my signature.
7
OK, photos:

This is the dual nano switch that I'm having issues with.   Even though it's a dual nano, I'm only utilising one OUT as it's only controlling one light switch, however there is another switch up the stairs that controls the same light (I think they refer to that as a 3-way system).

https://imgur.com/a/KmEpr

I've also sent a support ticket to Aeon with the same photos.    Any help appreciated (electrician hasn't had time to come back yet).
8
@ Kwieto:

Initially I had 1A power units , but when the motor of the thermostat was turning , the thermostat display started flickering. With the 2A version it is stable. I think the flickering is mainly due to poor (Chinese) quality of the power unit.

Thanks for that LUE code , I made a scene as well for one of my thermostats ( ID 316) , and will check if it works with mine as well.

I assume I can use multiple of these codes in 1 scene, how would I do that , will this work?
Code: [Select]
-- check target and current setpoint values
local Gosp_Target = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "SetpointTarget", 316)
local Gosp_Current = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint", 316)

-- compare target with current and re-request temperature change if values are not equal
if Gosp_Target ~= Gosp_Current then
 luup.call_action( "urn:upnp-org:serviceId:TemperatureSetpoint1", "SetCurrentSetpoint", {NewCurrentSetpoint = Gosp_Target}, 316)

-- check target and current setpoint values
local Gosp_Target = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "SetpointTarget", 318)
local Gosp_Current = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint", 318)

-- compare target with current and re-request temperature change if values are not equal
if Gosp_Target ~= Gosp_Current then
 luup.call_action( "urn:upnp-org:serviceId:TemperatureSetpoint1", "SetCurrentSetpoint", {NewCurrentSetpoint = Gosp_Target}, 318)

-- check target and current setpoint values
local Gosp_Target = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "SetpointTarget", 44)
local Gosp_Current = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint", 44)

-- compare target with current and re-request temperature change if values are not equal
if Gosp_Target ~= Gosp_Current then
 luup.call_action( "urn:upnp-org:serviceId:TemperatureSetpoint1", "SetCurrentSetpoint", {NewCurrentSetpoint = Gosp_Target}, 44)

-- check target and current setpoint values
local Gosp_Target = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "SetpointTarget", 45)
local Gosp_Current = luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1", "CurrentSetpoint", 45)

-- compare target with current and re-request temperature change if values are not equal
if Gosp_Target ~= Gosp_Current then
 luup.call_action( "urn:upnp-org:serviceId:TemperatureSetpoint1", "SetCurrentSetpoint", {NewCurrentSetpoint = Gosp_Target}, 45)
end

Or will I have to use for every thermostat a new scene?

Thanks,
Cor

9
General / MOVED: Homekit and Synology Chroot
« Last post by John M. on Today at 04:38:03 am »
10
General / MOVED: Wunderground Weather Plugin
« Last post by John M. on Today at 04:37:11 am »
Pages: [1] 2 3 ... 10