Many thanks @denz1968
It sounds like the ModeMCU is still require to communicate between the two systems but that you are replacing that with a Raspberry Pi. Is there any specific reason for that? I had the impression that the Mode MCU supplied by @cjcharles had all the relevant firmware installed. Do you want the flexibility to write your own or use other software OpenHAB?? to replace the ModeMCU Firmware?
Re the neo stats that’s one of the features I like. Our village hall has a system designed by HeatingSave which has similar if not better functionality. It learns how long the system takes to get up to temperature and can allow for that by turning it on earlier. This also reduces overshoot and saves energy where it gets too hot and then has to cool off to reach its target temperature.
Unfortunately I dont have Apple Homekit as I’ve already invested in Amazon Echo and prefer Alexa voice control.
Thanks Again
Fozzie
I have been long been waiting a heatmiser c2c solution , its been requested on there dev request page for years, I don’t think it will ever happen though
As others have said the HM app is terrible with no ext temp compensation and slow response times
It was the only stat I could find that fitted my needs, so I keep checking the device manufacture page ever hopeful Heatmiser appears
Many thanks @Tim99 You are spot on with your description of UFH. A bit like the tortoise and the hare!! The tortoise eventually gets there but uses less energy in the process. However its difficult to educate others not to turn up the temperature and expect an instant response!! One UFH installer recommended leaving the system running 24x7 365 as he said the thermostats will not be calling for heat when the external temperature rises and its better for the system and building fabric to be kept at a constant low temp. I couldn’t work out how he figured it would save energy though.
I have a bungalow with concrete floors so no radiators apart from three towel rails that run off the HWC supply so are on when the HW is heating.
Sorry I don’t have any algorithms and wouldn’t know where to start:-) I just know that somehow the system needs to take account of outside temperatures. @cjcharles has mentioned in his post below that its something he wanted to explore. hopefully he will find some time amongst other workload pressures.
Fozzie
Hi @fido Ive just requested a quote amd materials list from Heatmiser to replace my existing Uponor system and said my choice of Heatmiser was partly dependant on future integration with SmartThings. The technical rep who replied pointed me to the same feature request list that you posted elsewhere and said it is being considered. (However I note the status is Under Consideration rather than Planned
Fozzie
Thanks @cjcharles
The responses I am getting from this forum and the work that you have undertaken and continue to update and develop have pretty much convinced me to move to SmartThings and Heatmiser. My only concern hinges on the responsibility of you as a single developer supporting the integration. If for personal reasons you had to give this up where would it leave integration when either Heatmiser or SmartThings make changes which break the link?
However the icing on the cake would be external temperature compensation as I am convinced this would transform my UFH efficiency and save energy.
Thanks again for all your hard work
Fozzie
The way I see it is that Heatmiser does provide a good thermostat platform, that can be integrated with a good number of external platforms (either through this integration, or the equivalent I built for Hubitat, or a huge number of others that have been built by other people). Selecting Heatmiser is a decision that can mostly be done independently of SmartHome, and I do strongly believe it is a good platform. The only risk to this is that they remove their local (LAN) API (which every single integration is based on), but I think that would cause uproar from many thousands of customers.
Im not planning to replace my Heatmiser thermostats any time soon as I hugely value the flexibility and reliability of the platform as the basis for integration. Extra intelligence can then sit on top, even if Heatmiser don’t add it themselves. (e.g. creating a rule from Webcore(or similar rule based tool) that says “if external temp below X and (next target temp-current temp) above Y then set current target to Z”). Yes there is some extra complexity to manage, but I think its quite powerful. Just like my rules that say “if heating is on and nobody is home then set target to 13 degrees”, this provides a very easy way to make the system more efficient.
The link to ST is based on the local API mentioned above, but because ST isnt able to send custom web packets the NodeMCU is needed to translate to something ST understands. The NodeMCU bridge is part of the code I have written, although quite basic compared to other stuff. The majority of the stuff which could be improved (extra intelligence) is the two ST device handlers (groovy based) and this is entirely open source, so it isnt too complex to update/improve by anybody. Likewise if ST explodes in a few months time due to all the changes they are making, you still have plenty of options for smarthome platforms that integrate with Heatmiser.
Yeah, its been under consideration for years, my needs are the most basic of all, a little known option of a neo stat is it can be configured to be a basic non timer thermostat for rad systems that has app control, I didn’t need extra timers, it had to replace a 3 wire basic dial honeywell stat and had to look decent
Thats why I chose Heatmiser, to be able to add it to ST and leverage other Zwave zigbee devices would be great, I don’t use apple anything, have no time or desire to add a node so official c2c integration would be nice
I have just gone through the setup and everything seems to have gone OK until step 8. I assume that the NodeMCU dashboard referred to is the webpage hosted by the NodeMCU? If so I don’t have a Configure Child Devices button on there. I have attached a screenshot
I think your device must have escaped without a firmware upgrade to the new version. On my GitHub page you will find a firmware file, which you can upgrade at ip_of_nodemcu/update
Thanks for that Chris. Device firmware upgraded but no thermostat visible in ST - just the hub still. Do I need to go back to repeat one of the earlier steps?
Correction - just repeated the add child step and it worked! Thanks muchly!
With Heatmiser now officially not looking to integrate with ST I’m going to try and use your way Chris, when I get home I will start to study, having never run a node anything before I’m going on a learning curve
Hi Chris, i am getting a network error when trying to set any points using the child device thermostat
here is my live log of the bridge 7b578d31-8425-4ef2-9237-4a09851123f1 19:46:41: error groovy.json.JsonException: expecting ‘}’ or ‘,’ but got current char ‘r’ with an int value of 114
The current character read is ‘r’ with an int value of 114
expecting ‘}’ or ‘,’ but got current char ‘r’ with an int value of 114
line number 2
index number 36
“relaydevice”: “neostatLiving-Room”,
.^ @line 385 (parse)
7b578d31-8425-4ef2-9237-4a09851123f1 19:44:25: error groovy.json.JsonException: expecting a ‘,’ or a ‘]’, but got
the current character of ‘r’ with an int value of 114 on array index of 2
The current character read is ‘r’ with an int value of 114
expecting a ‘,’ or a ‘]’, but got
the current character of ‘r’ with an int value of 114 on array index of 2
line number 2
index number 44
“relaydevice”: “neostatLiving-Room”,
.^ @line 385 (parse)
Can I ask you to remove spaces in your Neostat names (I thought I had made it one of the setup instructions but sorry if not) since they get messed up while passed in a URL. You need to do this in the Heatmiser app, and once they have been removed you can then remove children from ST and attempt to re-create them.
Also just to be sure, in the first post of this thread is my Github link, on there you will find the latest firmware. Can you do an upgrade, just to make sure that isn’t adding extra confusion.
Hmm, renamed my one single zone as ‘Heating’
Removed child with node method
Recreated child using node
child creation tool
Thermostat appears in ST but still shows network error when trying to operate and no temp displayed
Fw updated as well with bin from Github
If you could update or add the latest screen caps to the original post Chris it would be really helpful, I just noticed the screen cap you have of the hub has information but that was for ST classic, does the current ST app and subsequent neo bridge device page have information ? Mine just says connected
Sorry, slightly off topic of SmartThings although I’m still considering using it with your Node MCU, but after several years of using Heatmiser Neostats locally, I finally got out the NeoHub and fired it up. Revelation. The latest NeoApp now seems reasonably OK unlike the initial incarnations (from what I read) but it is a bit laggy, so I am intrigued by what you say in your project description that the NeoHub can be offline but still receive instructions from the NodeMCU. If this is the case, why can’t the NeoApp communicate directly with the NeoHub when it’s on the same local network instead of the laggy response of always issuing instructions to the hub via the Heatmiser web servers? They told me this is not possible. Do you agree?
It’s removing this lag that’s got me interested in your project, but if Heatmiser can eventually do it natively in the app then in truth I’d probably stick with it.
Try connecting Heatmiser to Google Home or Alexa apps and controlling through there. There’s almost no lag with Google Home and the interface is much nicer than the heatmiser trash app.
If you do that do you still need to “tell heatmiser to set the thermostat X to 20 degrees” or have they now optimised that process on Google home? That was a big advantage of this integration for me as the speech recognition was much more likely to get a short phrase correct, compared to the whole phrase above.
The integration with heatmiser is using their LAN based protocols, but now that Samsung have pushed everything to the cloud themselves it sadly does require internet access. Luckily I do find it very responsive.
