Node Red Dashboard buttons with Homeseer Switches for On / Off etc

[tool172]

I can make the documentation work for the node red homeseer library to control switches with inject objects. However whenever I try and use the node-red-dashboard buttons I can't recreate the payload or objects because they aren't selectable. What is the correct way for the flow to work to either have a button or switch call an inject in the flow? Please post an example with the flow and or methodology. I have searched high and low. Is the answer to use MQTT in NodeRed? I believe i should be able to just use the switch and somehow call the inject but for the life of me can't figure it out. I have experience in Server side scripting and html and css but i'm new to Node Red.

[Eki]

So, I use a template. Here is "Reset Power Strip" button:



<md-button class="button send" style="background-color: #0974793f" ng-click="send({topic:'control', payload:'click'})">Reset Power Strip</md-button>










Flow:

[{"id":"884889b5.70494","type":"tab","label":"Misc","disabled ":false,"info":""},{"id":"2b53ded2.92a602","type":"hs-device","z":"884889b5.70494","name":"","device":"532","serve r":"710909f1.3b2628","feature":0,"reportonstartup":false,"x" :750,"y":300,"wires":[[]]},{"id":"22a77731.4278e","type":"change","z":"884889b5.70494 ","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"{}","tot":"jsonata "},{"t":"set","p":"payload.value","pt":"msg","to":"0","tot": "num"}],"action":"","property":"","from":"","to":"","reg":false,"x" :540,"y":300,"wires":[["2b53ded2.92a602"]]},{"id":"87667524.d82058","type":"ui_template","z":"884889b5 .70494","group":"76a9f0e6.c0ff","name":"Reset Power Strip","order":14,"width":4,"height":1,"format":"<md-button class="button send" style="background-color: #0974793f" ng-click="send({topic:'control', payload:'click'})">Reset Power Strip</md-button>\n","storeOutMessages":true,"fwdInMessages":true,"res endOnRefresh":true,"templateScope":"local","x":310,"y":300," wires":[["22a77731.4278e"]]},{"id":"710909f1.3b2628","type":"hs-server","name":"Homeseer","host":"192.168.10.104","port":"80 "},{"id":"76a9f0e6.c0ff","type":"ui_group","name":"Stuff","t ab":"cdc70f44.7c717","order":1,"disp":true,"width":15,"colla pse":false},{"id":"cdc70f44.7c717","type":"ui_tab","name":"H ome","icon":"fa-home","order":1,"disabled":false,"hidden":false}]

[tool172]

Where I get confused is the flow. See pick below.

[ksum]

Did you see this write up I did on dashboards with HomeSeer devices?

[tool172]

Did you see this write up I did on dashboards with HomeSeer devices?

Thanks. Reviewing now.

Sent from my SM-N986U1 using Tapatalk

[tool172]

The write up posted above is a primer.

Thanks ksum . Now to prepare for influx and my solar install.

Mods you can close this down. I might change that from keeping in sync to a full blown out primer which is why I skipped over it.

[tool172]

So, I use a template. Here is "Reset Power Strip" button:



<md-button class="button send" style="background-color: #0974793f" ng-click="send({topic:'control', payload:'click'})">Reset Power Strip</md-button>










Flow:

[{"id":"884889b5.70494","type":"tab","label":"Misc","disabled ":false,"info":""},{"id":"2b53ded2.92a602","type":"hs-device","z":"884889b5.70494","name":"","device":"532","serve r":"710909f1.3b2628","feature":0,"reportonstartup":false,"x" :750,"y":300,"wires":[[]]},{"id":"22a77731.4278e","type":"change","z":"884889b5.70494 ","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"{}","tot":"jsonata "},{"t":"set","p":"payload.value","pt":"msg","to":"0","tot": "num"}],"action":"","property":"","from":"","to":"","reg":false,"x" :540,"y":300,"wires":[["2b53ded2.92a602"]]},{"id":"87667524.d82058","type":"ui_template","z":"884889b5 .70494","group":"76a9f0e6.c0ff","name":"Reset Power Strip","order":14,"width":4,"height":1,"format":"<md-button class="button send" style="background-color: #0974793f" ng-click="send({topic:'control', payload:'click'})">Reset Power Strip</md-button>\n","storeOutMessages":true,"fwdInMessages":true,"res endOnRefresh":true,"templateScope":"local","x":310,"y":300," wires":[["22a77731.4278e"]]},{"id":"710909f1.3b2628","type":"hs-server","name":"Homeseer","host":"192.168.10.104","port":"80 "},{"id":"76a9f0e6.c0ff","type":"ui_group","name":"Stuff","t ab":"cdc70f44.7c717","order":1,"disp":true,"width":15,"colla pse":false},{"id":"cdc70f44.7c717","type":"ui_tab","name":"H ome","icon":"fa-home","order":1,"disabled":false,"hidden":false}]

Side note, what are you using to keep track of your propane? I have to go outside and read the gauge.

[ksum]

There is an InfluxDB contrib which makes saving data there easy. I don't recall doing a write-up on that, though. I thought the toughest part was deciding how I wanted to save the data. mclMQTT also now saves data to InfluxDB, but it does not get the older style z-wave items which have no children features. It does save the data one way for all devices. I went with different days sets for different devices. Meaning a humidity sensor is saved in one data set while a light is saved in a different one.

[Eki]

Side note, what are you using to keep track of your propane? I have to go outside and read the gauge.

Sooo.... there are gauges that can auto report the propane level ... but you can get real close by doing some calculations:

My fireplace has a 30000 btu burner.
propane has 91502 btus per gallon.
My tank holds 95 gallons of propane.
You cannot run the tank all the way empty .... you can get down to 20% then start running out of pressure. So there is 75 gallons of usable propane.
The fireplace is either on or off
There is a Zwave switch that turns the fireplace on and off.
Node-Red receives the status from HS when ever the switch is on or off.

Therefore, with all of the above, you can estimate the propane consumption whenever the switch is on, and store the running data in the global context, which is stored on disk.

We are in Arizona, so there are only two seasons out here; hot and less hot. So, I do not have to really worry about temperature affecting the propane bottle. But, you could also track daily temperature to tweak the consumption.

It is not perfect, but it is good enough to let me know when the propane is getting low and I need a refill. I have a fudge factor in there as well, so I can adjust the calculations based on actual refill gallons.

The refill button you saw just zeros out the calculations and starts again.

I think this approach would work for hot water heaters and house heaters. The only use that would be difficult is the stove, as the propane usage by the stove is variable, and that would be harder to estimate.