It’s odd because with my limited knowledge it looks like the Neostat Bridge can pull all the required info (it mentions the current temperatures which are correct and the other settings are correct too). I don’t understand why that can’t be pulled through to the app??!
Obviously it is a lot more complicated than I can understand 
Nic
Interesting, exactly the same problem and firmware as the other Nick.
Yes it seems it can connect and can request information, the problem is that it doesn’t seem to process any subsequent packets of data and only receives the first one.
I’m going to have a play with the network settings on the device and see if I can get another version to you both which maybe has better luck with your hub. Curious that it only seems to affect rebranded heatmiser hubs and it’s only a recent change that has caused this.
Thank you so much for looking into this for me (and Nick!)
Nic
For anybody else having issues where you can send commands to the thermostats but dont get any information back. It seems Heatmiser have changed something about the network packet size and hence need a firmware update to process them properly.
You can download an updated firmware from my Github (look for the .bin file about 323kb). After you have downloaded it you can go to the webpage of your NodeMCU and click the link to update firmware at the bottom of the list of links.
Hi Cjcharles, I have just tried to buy one of your boards to link my Neo to smart things - but it didn’t seem to go through. What is the best way to get my hands on one? Cheers. David
Hi @David_and_Joanna_Bil - I assume you got setup in the end as I did send out your order, though havent checked tracking information yet.
For everybody else, ive just updated the device handler slightly so it fixes a heatmiser bug where certain thermostats would sometimes change to ‘Timer’ mode (hence On/Off rather than setting the temperature). If you update the code of the device handler it should be more reliable for preventing this problem!
Hi @cjcharles. I can’t thank you enough for your work on this, and with help from other contributors to this thread I’ve successfully added 13x Neostat devices to SmartThings 
I’ve been able to set up automations based on thermostat temperatures - so I’m very happy.
I notice the icon (and device type?) appears to be a ‘switch’ rather than ‘thermostat’ in the new SmartThings iOS App. I’m not sure if this impacts functionality (when viewing the device details I can set temperature etc.) - but it would be nice for the device to be represented as a thermostat on the Dashboard screen so the temperature is shown rather than an ‘on’ or ‘off’ state.
I’m happy to take a look at this to update (and/or test) if you could point me in the right direction? I presume some code needs adding to the device handler?
Glad to hear it! Thanks for the appreciation! 
Thats annoying! It displays as a thermometer in the old app, Im not sure what has changed as Ive resisted switching to the new version for as long as possible given so many features are not available. It would indeed be a small change to the thermostat device handler code to change the icon, and likely in the top section of the code where it defines the tiles.
I’ll try and have a look at this in the next few weeks but Ive got a few other projects/improvements at the moment so cosmetic things will have to wait a bit.
@soxley Im afraid I have investigated and genuinely have no idea how to control the icon in the new ST app, it seems Im missing something but without some external advice Im going to have to leave this for another time. One thing though, the actual icons are set to be customisable anyway so you should be able to choose your own. If you go to the settings menu does the option for ‘update this icon’ (or similar) not appear?
Cheers
Hello @cjcharles, I’m using your integration over the year and very happy.
However I have an question as that is require for create proper condition in house.
Does it possible change property “Differential” on heatmiser thermostats? I mean delta of C which thermostat is waiting till start heat.
Yes the switching differential is customisable in the device setup menu (the same menu that you navigate to in order to pair with the NeoHub). I think the default is 1 degree but on my electric underfloor one I set it to 2 degrees to reduce the amount it flicks on and off.
Im not aware of the differential being customisable through their API, but it might be possible if you needed this for some reason?
Hi everybody,
In line with the holiday season (and to help make everybody a bit mroe energy efficient) I have released the holiday function to this Heatmiser integration…
There are a few new information fields added into the Thermostat devices, but additionally the Bridge device has some new fields which will allow you to configure a custom holiday period on your thermostats. Basically you can choose a custom finish time by adding hours and days, and after pressing set then all thermostats will stay in away mode until this date.
Unfortunately the Heatmiser API is a bit buggy (or not documented despite me trying loads of options) so you cannot configure a holiday mode for some devices, you have to set holiday modes for all devices simultaneously. On the plus side holiday mode will not override standby mode, hence if something is in standby/frost mode when you go on holiday, it will remain in standby/frost mode when your holiday period ends.
To upgrade you just need to copy over the new device handler code (for neohub and thermostat) and it will start working. Super quick upgrade with no requirement to mess with children devices.
Hope it is useful given the cold weather to be able to set your thermostats to holiday mode while you are away from home.
One more small bug fix to get the thermostats working with Google Home control again (seems Google changed from sending an integer to a float and it broke this device handler). Now working again
Hi Chris,
Im really struggling with this
I had managed to get it connected to the wifi yesterday then for some reason I decided to delete it from the router thinking it would appear again - It did not.
I have tried to program the nodeMCU, but I am getting the below error. Ive tripled checked its on the right COM port- Any ideas?
Also when I created the two device handlers but I try create a device I cannot select anything from the drop down boxes (Location, hub, group)
This is my first time working with smartthings so please bare with me
Yikes, take a step back! None of this should be needed, and certainly not flashing it. You should just need to find the device IP again, as deleting from the router shouldn’t stop it trying to connect to the WiFi network.
If you have a Windows PC then do you see it appearing inside Windows device manager? Thats the easiest way to find it, as it should send some information that helps windows find it.
It’s still in device manager and I’ve found the IP and it’s still there, loading the dashboard
Thankfully that’s one issue out the way
I think I’ve now got most of it set up correctly now.
Getting the following errors when trying to add thermostats or refresh IPs though
17:40:15: debug uri /neorelay?device=hubzonesetup&command={“GET_ZONES”:0}
17:40:15: debug Requesting List of Thermostats
17:40:15: debug Removing Child Thermostats
17:40:12: error java.lang.NullPointerException: Cannot invoke method getDataValue() on null object @line 175 (refreshipaddresses)
17:40:12: debug refreships()
17:40:05: error java.lang.NullPointerException: Cannot invoke method getDataValue() on null object @line 175 (refreshipaddresses)
17:40:05: debug refreships()
17:40:05: debug updated()
@Eddie1 Presumably it is working on the nodemcu? Given you’re on ST integration steps.
Can you post a screenshot of the device in the ST web IDE (account.smartthings.com)? I think you might have added the device in the wrong way or place - given I think that error is related to ST not finding your hub.
I need the bit under events, just where you’ve cropped it sadly 
But also just making sure you haven’t added any passwords? Make sure they’re blank in the nodemcu and also in the device handler on the phone.
