As many UK/European users know, some years ago I wrote a Vera plug-in for the Heatmiser Wi-Fi range of thermostats. These models are no longer available from Heatmiser, having been replaced by the Neo and SmartStat ranges.
The SmartStat models do not support third party comms so there’s no way to connect them to Vera, but the Neo models do. Heatmiser have kindly agreed to supply a NeoStat and NeoHub to me for development purposes, so all being well I should be able to offer a plug-in for the Neo range in a few weeks’ time.
If anyone is interested in beta testing, or in having a copy of the plug-in when it’s ready, please let me know by PM, including your e-mail address. It would help if you could also let me know if you’re using UI7 or UI5.
Thanks Alan for all your work on this and speedy turn around. This has turned a great set of thermostats into a important piece of my home automation.
I now have 12 neo stats set up in vera which include normal stats, electric floor ones, ones running as time clocks for towel rails and hot water timer. I’m not sure any other system gives you all those options, nest definitely doesn’t. And now it’s all powered by vera.
I stayed up late and the kitchen motion sensor saw it and extended the temp for another hour.
Then when I set the alarm all stats were set back to normal program now.
Hi Simon - I’m pleased everything is working for you. Home automation can be frustrating at times but it’s also very satisfying when things go to plan.
Apparently, I already have an account here. Who knew!
NeoStats are slowly infecting my home but I don’t have any other home automation or Vera gear…yet. My issue with Neo is that I’m running different profiles on different days to get the system to do what I want but that involves a lot of manual switching (when I remember).
Is that something that the plugin would allow me to automate i.e. could I download a new profile to a NeoStat via the plugin assuming I’d coded up all the conditional stuff I wanted?
The plug-in doesn’t currently support uploading of profiles to the Neo because most users find it’s easier to dispense with profiles and implement the logic in Vera instead.
I have a lot on neostats that I use with this plugin and have ditched my profiles and recipes from the neo native app. For instance my normal working week and at home during week profile which allowed for heat during day on a weekday is now automatically done when motion sensors see movement between 8 and 5 mon-fri. At 5pm the normal profile takes over.
I also had a guest profile that turned on the loft bedroom heating but now that is controlled by a switch on the vera iPad app that also affects some of the other automation. .
My recipes for going to bed early or staying up late are controlled by motion sensors and setting the alarm at bed time.
So as Alan says you will drop profiles ad soon as you discover what vera and pleg can do. The aim here is automating as much as possible. My longer term goal is to make my guest mode be triggered from a Google calendar entry so there is no involvement at all with the heating.
Yes, the logic of getting Vera to do everything escaped me initially. I was too busy focussing on extending what I had rather than considering what I might do with a different set of equipment.
