I just bought my first zwave devices; Micasaverde, Everspring St814 and one wall plug switch. I have to say, this not a plug and play system. I have been fighting with them few days. The problem is to get humidity and temperature values from st814. Vera doesnt seem to poll. I will get the values after wake up time, if I press “poll now” button.
I got it work, when I did a scene with timer and with luup code “luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},16)”. Okey, its good to have it working, but the way to do it cant be right, What I am doing wrong? Why Vera isnt polling? I have the latest version 1.1.1362. The polling frequency should be 60 sec and wake up time of St814 is 600 sec.
There is few discussions about similar topics, but maybe bacause of my lack of language skills I didnt find any answer.
Generally, battery-operated sensors cannot be polled as they are asleep most of the time. Vera will skip polling such devices. Also, you cannot control the actual polling interval; you can only set a maximum poll frequency (i.e. don’t poll more often than once every X seconds).
I don’t have this particular device, but from memory, I think it has the ability to auto-report (when a predefined change occurs in temperature or humidity) and will wake up periodically so current readings can be communicated. I think people have found that only the latter, i.e. the wake-up mechanism, works. So you should be getting an update automatically every 10 minutes?
I’m another Vera newbie that has been struggling with the exact same problem for a couple of days. Hope you more experienced guys could point me in the right direction, as there is a lot about Vera I don’t understand yet.
I have read various posts about challenges with the Everspring ST814 and especially in combination with Vera. I haven’t seen anyone proposing a solution yet, but I am sure there is one.
My understanding of the problem so far:
Vera will never poll the battery operated ST814. I can’t understand why Vera should decide not to, if I absolutely want it to poll the thing? Sounds like a bug to me. Is there any way to force Vera to poll it at given intervals?
Vera never receives an auto report from ST814. I configured ST814 to send reports every 10 minutes, to send report if humidity changes by 5%, and if temperature changes by 1 degree. No reports ever reaches Vera, even if all three events should have triggered an auto report.
ST814 is supposed to emit these reports to the nodes of grouping 1. Isn’t Vera defined as a node of grouping 1? (What is “Grouping 1” anyway?)
The only way I have found to have Vera and ST814 communicate is to do a configuration change on the device in Vera. Then everything is OK, and all status of the ST814 is updated in Vera. So if this is the solution, can I force Vera to automatically do a configuration update at set intervals?
Obviously, this is a major challenge when I use Vera to control electrical heaters based on temperature input. It will trigger the scene when configuring the ST814, in other words turn heat on or off. Then it will never do anything else, so it will become either be very cold, or very hot…
I think you can do the same thing, i did. Make a new scene just to poll. Write the code “luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},16)” in the luup -tab. Chance the number 16 with the number of your device id. I set the timer of the scene to poll every 2 minutes, and it works fine.
This forces vera to poll the device and you will get the values when the device will wake up.
Seems like that works fine here as well, thanks a lot!
What wake up interval did you set the ST814 at? Guess it has to be pretty frequent (as polling seldom succeeds every time), which probably will eat batteries. Any experience on battery life?
I would really like to have it the other way around, to have ST814 send reports to Vera at given intervals and/or temp/humidity events. It should be more reliable, and consume less power. Any experience with this approach?
I found something strange when looking into the “Grouping” things. Don’t know what I’m talking about, but I guess the ST814 needs devices grouped in Association group #1 and #2. Nodes in Group 1 will receive reports (max one node), nodes in Group 2 will receive basic on/off commands (max three nodes).
So I created two groups with ID 1 and 2 under “Device Options” “Associations”.
I then associated the ZWave device to Group 1, and the Appliance switch device to group 2.
After configuring the ST814, the strange happens; It insists that the device _Scene Controller is in group 1, and not the ZWave device! I have not succeeded in changing this.
Does this mean it sends reports to the _Scene Controller device? How can it be retrieved from here, as it seems Vera don’t get them. And what is this “_Scene controller” device anyway?
The wake up interval of st814 is 600 sec. I am a neabie as well, and still wondering how these suppose to work. I think the intervals should be longer, but i didnt test it yet. If the wake up interval is 30 min, and polling interval 10 min, is it possible that they dont see each other. How long Vera tries to poll and how long st814 is staying awake?
The grouping doesnt say anything to me. Let me know if you find something new.
All Z-Wave devices are children of the _Scene Controller. The _Scene Controller is its own parent and is invisible on the GUI. You could use ADD or install LSI to make the _Scene Controller and its parameters visible.
Thanks Ap15e!
Installed LSI, gives a lot uf useful info.
In my Vera, LSI reports the _Scene controller as ID 2, with ID 1 (ZWave) as parent.
My ST814 still insists that ID 2 is in group 1, even though I keep configuring it with ID 1.
What can I use the _Scene controller for? Will it ever receive the reports that ST814 is supposed to send to the Group 1 nodes, and can I use the data in a scene?
Sorry, but totaly confused right now… ???
For Z-Wave devices, the [tt]altid[/tt] contains the [tt]Z-Wave Node ID[/tt]. AFAIK the [tt]altid[/tt] for Z-Wave devices should be in the range 1…232. The [tt]ID[/tt] is a unique ID created by MiOS that is completely independent of the [tt]Z-Wave node ID[/tt] (=[tt]altid[/tt]).
But it doesn’t help me in solving the problem. The ST814 clearly uses the Association Command, which refers to the Vera/MiOS ID’s. I verified this by putting a couple of appliance switches in group 2, using their Vera ID’s. They then received correct control messages from the ST814.
Hey guys the code suggested in this thread “luup.call_action(“urn:micasaverde-com:serviceId:HaDevice1”,“Poll”,{},16)” was working for me on VERA2 but no longer working on VERA3. Any ideas? Has there been a change in Luup on VERA3?
Thanks for the reply. that doc shows the correct syntax, but seems like my vera is not reacting to the luup code. Is there any on/off switch for the Luup engine? or at least a lupp log i can access to see what is going on?
