i’ll Wait for your report then, hopefully this new firmware isn’t too far away…
thanks,
eric
I was trying to find a dealer of this product in the Netherlands, but it seems hard to get one. Only UK webshops have the product, but those shops don’t deliver to the mainland.
So Mark, if you get it working, can you also tell me how you ordered your piece? Or are you living in the UK?
Hi there.
The Horstmann HRT4-ZW thermostat with ASR-ZW receiver should be available within a week or so from our web shop (www.atom-solutions.com)… shipping to any EU destination. We’ve been waiting for a long time for this… 8)
I was trying to find a dealer of this product in the Netherlands, but it seems hard to get one. Only UK webshops have the product, but those shops don't deliver to the mainland.
Marcel, http://www.heatingcontrolsonline.co.uk can ship the HRT4-ZW to The Netherlands, send them an email and they will send you information how to order.
Jack
[quote=“markbawden, post:20, topic:166748”]Not yet Eric, but i’ve had a reply from Micasaverde suggesting that it will/should work with the forthcoming firmware update - which is due in the “next few days”, the email also said that if it didn’t work after the upgrade to contact them.
SO, i’ve kept the thermostat, hopefully It will work eventually.
I’ve mentioned in all my correspondence with Micasaverde that its in their interest to get this working, as it’s presently the only available stat for europe and other countries on the same 868.42 mhz frequency.
i’ll be annoyed if they don’t, but on the upside it’s a great stat, really simple, well designed and responsive. (it is a very simple on off at set point operation, no timers etc, so perfect of a zwave system once it’s working).[/quote]
Mark,
Did you upgrade to 1183 and did it solve your issue’s with the HRT4-ZW?
Thanks,
Yes, i’ve installed 1183, it’s made no difference, but i haven’t had a good chance to play with it yet. Going to try and get it wotking this week, and if a no go, contact micasaverde - they said they’d help, so hopefully…
Incidentally, I’ve just seen the hrt4 -zw is for sale at zwave-products.co.uk priced at £299 glad i bought mine from www.heatingcontrolsonline.co.uk/for it’s rrp of £70.
Been playing with thermostat and latest firmware for a couple of hours. Still not working. BUT… I can pair both the switching unit and the thermostat itself.
The switching unit shows up as a thermostat in Vera’s UI, and reflects the current mode, (ie heating/off/auto, I can override these via vera, (as if i’d pressed the overide button on the switching unit. I can also set a setpoint, and get the message back that it’s been transmitted ok, (but it doesn’t actually change anything).
Unfortunately, I haven’t been able to associate the thermostat portion with the switching unit via vera. It shows up as a thermostat showing -3277 degrees, (makes no difference whether set to F or C). turning up the setpoint on the thermostat doesn’t turn on the switching unit.
I’ve ended up re-pairing the thermostat with the switching box, it now controls the boiler, and i can still use the override via vera or SQremote.
Micasaverde are you listening? It would be great to get the only available z wave thermostat outside the US working - especially as it’s now being sold beside vera in online shop in the UK.
Sorry to hear the 1183 did not solve the HRT4-ZW issue…
I am tired of waiting for an EU stat, will go ahead and order the stat at heatingonline…hoping the issue’s get resolved some day.
When I have installed my stat I will let you know what does and/or doesn’t work on my vera…
Guys , any news about this termostat?
I think a walkthrough document would be a great tool for the rest of us to follow!!
Work and kids have prevented me attempting to make progress on this - whenever I start playing around with my Vera, it always turns in to a three in the morning tearing my hair out exercise in frustration.
On a plus - the rest of my family loves the thermostat, zwave working or not, it’s neat and simple to understand, aging in laws can adjust it too!!
I did try pairing the relay box, and this works well, (you can see what state it’s in, and control it - although any changes you make are overridden by the thermostat after about 30 mins, so not really any use).
hey guys
any feedback on this ? did it work ?
I’m interested on this topic too, please let me known what works and what not works with HRT4-ZW and Vera2.
Best regards
I’ve not done anything further about getting this to work - I can’t afford the time at the moment. Troubleshooting Vera always seems to mean I’m still up at 3 in the morning. I’ve wrote to miciasaverde, when they get back to me i’ll post.
PS on a small note, battery level on the thermostat is reporting when low, (batterys ran low last week and I was suprised to see vera knew). so i’l still got high hopes for this particular stat.
Hey Mark,
Have you had any further luck with your Horstmann Hrt4 and Vera?
I currently have the Hrt4 paired with Vera and the ASR, Vera displays the current room temp along with the set point. If I change the set point physically Vera updates instantly and if calling for heat the ASR activates the boiler.
However I can only get Vera to change the heating set point after physically putting the HRT4 in to listen mode (LI) once I do this Vera can send the HRT4 a set point change and it updates on the HRT4’s display
I am having problems getting Vera to get the HRT4 to wake up and listen to the new set point automatically. I sent an Email to MCV just waiting for a response.
Hi Guys,
First of all apologies for spelling and grammar. Secondly, long post, probably makes no sense, but this is the results of my 2 weeks of labour, reading through manuals, talking to horstmann and MCV.
I have been following this for a while, and reading Marks reports. I decided to buy one of these, thought I would have ago, also it seemed very reasonable in price.
The stat is nice, wireless, user friendly, and ergonomic, at the TPI software (built into the stat to control how many cycles an hour for heating, different setting for different fuels) seem to work well for me, I am on a Oil fired burner out in the sticks and the boiler now seems to do a lot less stopping and starting.
Now on to the important stuff.
Just to re-cap, the thermostat is in 2 halves, a receiver to switch the load for the boiler (this is mains powered) and the battery operated Thermostat, which compares the room temp, with the set point (chosen by the dial on the front) and decides wether to fire a binary switch (turn on) command to the boiler receiver, after running it through it’s TPI s/w.
Zwave - The whole reason I bought the stat.
The Receiver.
The receiver (on the boiler) can be paired with vera, It appears as a thermostat in vera, but it’s not really, it is a binary switch, the only component on the thermostat widget in vera that works is off and heat, all the other components of the widget do nothing. So you can turn the heating on a off, but this is the equivalent of pressing the on and off override buttons on the receiver, so it completely ignores what the thermostat is set to, and so is pretty useless. Also worth noting is this, Horstmann build into this receiver a fail safe feature, if the receiver does not receive zwave communication for one hour, it will ‘fail safe’ and switches off. This is fine for when the thermostat is paired / controlling the receiver, as intended, as the thermostat, is designed to send binary on or binary off messages within the hour time slot, as keep-a-lives, so the receiver does no go into fail safe mode. This is probably a good idea, your thermostat runs out of juice, leaves the switch on, and your house turns into a furnace.
Vera, when turning on and off the Thermosat, does not resend the switch commands within the 1 hour time slot, and therefore the boiler switch, will essentially switch off, exactly one hour after it was told to switch on, although, you could write a script to solve this, it would be very dangerous, as stated this is like pressing the override button on the receiver, which ignores the thermostat.
So from this we can conclude, the binary switch receiver, should only really be controller by the thermostat as intentioned.
The Stat
The stat can be paired with the Vera unit. Once paired, you need to set some addition configuration to get the transmitting temperature to work, I also got the -3277 degrees, but then I realised that this is the dec equivalent of the hex 0x800 which is the register setting for don’t send temp. You need to send some configuration to the stat once you have paired it, config option 1 send a 1dec byte value of a 255 (any number over 128) will tell it to start transmitting temp) Option 2, you can change it to ferinheight option 3) gives the step levels for monitoring temp changes. This is all in the manual on Horstmann’s site.
The only way I can seem to get this paired is by using the L Learning setting, not the A associate setting as recommended by horstmann, Once you use the L setting, my stat forgets that it is paired with the the receiver (ASR) so then needs to be re-introducted with the ‘I’ Setting.
Once this is done, you end up with 2 thermostats in Vera, I believe this is because they both report to be Thermostat Control Class devices. One is the ASR on that panel only the heat on and off works, and the other is the Thermostat, where I can see the current temp, and set point.
Vera can transmit the setpoint to the stat whilst it is awake, this could mean you are manually turning the dial or it is manually set to L mode ‘Listen’ which is where the devce listens for 60 seconds, as it forces it to stay awake.
Also, I have changed the stat wake up intervals, and this works well, I can confirm the last seen unix time stamp in vera the timestamps increase at the intervals set.
The situation is:
I can turn on the asr for 1 hour time slots.
I can see the temp in the hall.
I can see the setpoint that someone has dialled it to, even though it is remotely unchangeable.
The 2 main problems I have is this.
-
Vera seems to delete the set point request that is queued for the devices wake up, before the device wakes up. (This might be something to do with beaming mode, I need to investigate more) where the device should wake up at a set interval and say ‘hey controller, got anything for me’, but when the stat does this, the vera does not have anything for the sat, as it had deleted the set point as it could not deliver instantly at the time it was set. Why does vera no queue this? - as it works for other modules I have.
-
After a while my stat and asr cease to be paired with each other and just talk to vera.
I tried to go to the wave 3 firm ware, but in this release they have ceased support for the handheld secondary controllers, which I believe the stat is. Once I paired the vera and the stat, when it was on this version, some of the menu items disappeared from the stat, namely the ‘I’ which meant that it could no longer be introduced to the ASR.
I would be happy not to be able to turn the asr on and off, I just want to turn the stat to 21 for heating on and turn it to 5 degrees (it’s lowest setting) for heating off, this would be fine for me.
Sorry for the long post, I just wanted to share as much as I can, so we don’t have to re-invent the wheel, and stand on the shoulders of giants… blah blah.
Oh and ofcourse, MCV are getting back to me… will let you know when.
hi, guys. Some great progress from jallopy. I’m looking fwd to getting the temperature reporting working when I get home tonight.
On a side note, i eventually intend to wall mount my stat and wire it up to a 3v transformer, then set the thermostat to wake up at much shorter intervals, say every 30 or 60 sec. Hopefully this will work well.
looking fwd to hearing more on everyone elses progress.
mark
Mark,
Like yourself, I thought, how can I get this to be awake, and what about the battery issue.
Well the shortest wake interval supported is 256 (another binary number) which is just over 4 minutes 10 seconds, but it still seems too short to catch the setpoint request from the Vera, before it deletes it. When the L is flashing in installer mode, it is constantly listening for 60 seconds, but as we know (vera transmits and stat receives), when it is in installer mode, we have a Flashing L rather than the temperature information.
If only there was a way to have it constantly listening / awake and be in normal operating mode, and ofcourse powered by a transformer. Then I would be a happy chappy.
However, I don’t think it should work like this. I have other units such as the 3 in 1 motion sensor (HSM100) and commands for them seem to queue fine for these devices until they wake up. The stat wakes up every 256 seconds, but vera hasn’t got anything waiting for it, because it doesn’t ‘queue’.
I have read how zwave devices in this class are suppose to work I think they are called beam devices of FLiR but don’t quote me on it. They wake up, send a beam “I will be awake for the next 0.5 seconds, have you got anything for me…” and which point the vera unit replies " yes I have this setpoint for you, I have been holding onto it for about 4 minutes now, glad you woke up" … The idea being that the queue time will always overlap the wakeup interval, and all should be well.
I think there is still hope for this. I think, that when vera learns about the stat through the Auto Configure, it somehow learns wrongly, that this device will be always listening, I am not sure how, this is just my working idea. It from that point onwards, does not treat the stat as a “queue set points and wake for beam wakeup”, but instead “I have tried to send this set point, it did not confirm receipt, it’s not responding, the Time To Live of this has expired, delete the job, as it was unsuccessful”
I have looked at the error codes in the vera debug, and the command ends up with a code which means failed / unsuccessful. HOWEVER there is a code type " Wait for wakeup. The fact that the command that have a destination of the stat, are not tagged with the code Wait for Wakeup, is the problem.
If only we can somehow tell vera, this is a wakeup device, queue your setpoints accordingly, if we could, I think the problem is solved. We have more chance of altering Vera’s behaviour that the Stats. I was even considering writing a Lua code module to do the job of the stat as we can read the current temp and set point, (because communication this way from stat—> vera works fine) and then turn the ASR on until Temp = SetPoint.
However, I have already wasted a lot of time on this, and it should just work 
MCV, can you let us know of anyway to tell vera to wait for wake up, before firing the set points?
Would you mind posting the ‘Settings’ → ‘Capabilities’ of your device?
Mine shows this:
Capabilities 18,150,0,1,8,0,B,|49,67,112,114,128,132:2,133,134,
Version 2,2,78,2,0
Manufacturer Horstmann Controls Limited
I don’t know if it is different to others…
Thanks for looking…