Latest Updates |
Home Automation |
Self Build House |
Parts for sale |
Electric Go Kart Part 1 |
Electric Go Kart Part 2 |
Contact |
UK Cold war related |
Bungalow Project P2 |
Bungalow Project P3 |
Bungalow Project P4 |
Bungalow Project P5 |
Bungalow Project P6 |
Bungalow Project P7 |
Croyde ROC post |
RAF Holmpton cold war bunker |
Kelvedon Hatch cold war bunker |
Salisbury 2000 Pics |
4x4 Picture Gallery 1 |
Wales 2003 |
4x4 Picture Gallery 1 |
I have created a script that enables HomeSeer users to post device values to a Microsoft Azure IoT hub.
Here’s the resulting report in Power BI.
You can download the VB script from here -
You must update the script with the name of your IOT hub, the device name and the SAS token (using IOT explorer above).
You then supply it with parameters which defines a catergory (note the spelling mistake)
which is any free text field you with, it just allows you to create filters in your
reports, followed by the homeseer device name that you wish to monitor. I have several
events configured -
catergory=Water|Hot Water pressure|Water pressure|WaterLToday
catergory=Temperature|Outside Temp|New Kitchen|Midon Onboard|Master Bedroom|Living Room|Kitchen Floor|Hot Water|Guest Room|Garage|Day Room|Croyde|Hot Tub|
catergory=Humidity|Lodge Temperature 1|Lodge Relative Humidity 2|Loft Temperature 1
Create the IOT device and SAS token:
You need to download and compile Azuro IOT device explorer from here, which allows you to create devices, create SAS tokens, monitor traffic coming in and generate messages back to your device.This is mainly because I was too lazy to create the code to generate and renew the token on a regular basis (which is how you are supposed to do this). As you can see, having a 365 day expiry is very bad.