If, like me, you have been driving yourself crazy trying to follow the instructions in the Heatmiser neoStat V2 manual page 21 and wondering why you can Power the thing off (which is required for a number of actions)…then it’s because it’s wrong. After contacting support, I found the right way 🙂
Here’s how you do it
Use the < > buttons to move to the Power Icon
Press and hold the tick ? for approx. 3 seconds
You will then see a new set of three options. ‘SETUP’, ‘CLOCK’ and Power Icon.
Now use the < > buttons to move to the Power button…again
And now just wait. Do NOT press any buttons. After about 10 secs the light will go off…but continue to wait another 10 or so secs till the ‘SETUP’ and ‘CLOCK’ menu items disappear too.
Congratulations…now it’s off and you can perform the configuration steps that now start from this position.
In any organisation it is important to get a standard naming convention in place for most things, but especially with cloud-based resources.
As many types of cloud resources require globally unique names (due to platform DNS resolution), it’s important to have a strategy that will give you a good chance of achieving global uniqueness, but also as helpful as possible to human beings, as well as codifiable in DevOps CD pipelines.
I know you shouldn’t try and subvert your companies internal security policies, but sometimes the security department just don’t seem to understand the consequences of what they do…especially when using multiple computers simultaneously!
The following script essentially presses the inaccessible F15 key at regular time intervals to ensure the screen timeout is reset and you avoid locking out.