Seems like latest version 3.3.2.0 of mcsMQTT quit early this morning with the following log entries. Currently running Homeseer 3 V.3.0.0.435
May-08 3:15:24 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
May-08 3:16:19 AM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.
May-08 3:30:24 AM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
May-08 3:30:31 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
May-08 3:31:19 AM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.
May-08 3:45:24 AM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
May-08 3:45:30 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
May-08 3:46:19 AM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.
It is preventing me from navigating the HS3 GUI to disable the plugin.
I was able to shut down HomeSeer, restart and disable the mcsMQTT plugin for today.
Should I enable the plugin today and debug to watch what happens and causes it to debend Homeseer?
Relating to:
The currently is no automation for charting. Please propose what you would be useful for you. I can see an http get, mqtt json, script, and event action possibilities. To deal with browser cache the chart name is changed. A mod 10 function used so the user had the last 10 charts available to include elsewhere. With an automation interface there needs to be a way for the caller to know what file name was produced or it could be an input parameter as well.
I am fine with any methodology you want to use for charting (as long as it is documented and I can do it long math wise via the HS GUI or a short script).
Looking at your chart I can see that autoscaling is good for analysis, but not good for looking at things like temperature over time. Provisions should exist for user-specified y axis scales.
Yes the temperatures scaling isn't optimal over time and control would be nice. I have looked at the configuration file for the gnuplotting stuff.
Looking at your chart I can see that autoscaling is good for analysis, but not good for looking at things like temperature over time. Provisions should exist for user-specified y axis scales.
BTW getting ready to add the Red node running in the attic RPi for second floor / attic temperature and humidity sensors. Broker #2 serving up temperatures.
Still looking to convert my Red Node lighting 1-wire sensor to a meaningful number similiar to what you where doing for xAP.
Getting good numbers but want to reset the counter every midnight and get lightning rates per hour from the two counters.
I have put a counter function formula in one of the nodes for the 1-wire. Using a power rate formula in Red Node. Thinking though it would be better to just incorporate this in the mcsMQTT plugin.
Current raw values (no forumula)
5/8/2018, 5:37:10 AMnode: 1D.37C-Lightning11D.37C907000000/counter.A : msg.payload : string[8]
"15801445"
5/8/2018, 5:37:11 AMnode: 1D.37C-Lightning1
1D.37C907000000/counter.A : msg.payload : string[8]
"15801445"
Massaging with forumula but not implementing yet.
May-08 3:15:24 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
May-08 3:16:19 AM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.
May-08 3:30:24 AM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
May-08 3:30:31 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
May-08 3:31:19 AM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.
May-08 3:45:24 AM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
May-08 3:45:30 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
May-08 3:46:19 AM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.
It is preventing me from navigating the HS3 GUI to disable the plugin.
I was able to shut down HomeSeer, restart and disable the mcsMQTT plugin for today.
Should I enable the plugin today and debug to watch what happens and causes it to debend Homeseer?
Relating to:
The currently is no automation for charting. Please propose what you would be useful for you. I can see an http get, mqtt json, script, and event action possibilities. To deal with browser cache the chart name is changed. A mod 10 function used so the user had the last 10 charts available to include elsewhere. With an automation interface there needs to be a way for the caller to know what file name was produced or it could be an input parameter as well.
I am fine with any methodology you want to use for charting (as long as it is documented and I can do it long math wise via the HS GUI or a short script).
Looking at your chart I can see that autoscaling is good for analysis, but not good for looking at things like temperature over time. Provisions should exist for user-specified y axis scales.
Yes the temperatures scaling isn't optimal over time and control would be nice. I have looked at the configuration file for the gnuplotting stuff.
Looking at your chart I can see that autoscaling is good for analysis, but not good for looking at things like temperature over time. Provisions should exist for user-specified y axis scales.
BTW getting ready to add the Red node running in the attic RPi for second floor / attic temperature and humidity sensors. Broker #2 serving up temperatures.
Still looking to convert my Red Node lighting 1-wire sensor to a meaningful number similiar to what you where doing for xAP.
Getting good numbers but want to reset the counter every midnight and get lightning rates per hour from the two counters.
I have put a counter function formula in one of the nodes for the 1-wire. Using a power rate formula in Red Node. Thinking though it would be better to just incorporate this in the mcsMQTT plugin.
Current raw values (no forumula)
5/8/2018, 5:37:10 AMnode: 1D.37C-Lightning11D.37C907000000/counter.A : msg.payload : string[8]
"15801445"
5/8/2018, 5:37:11 AMnode: 1D.37C-Lightning1
1D.37C907000000/counter.A : msg.payload : string[8]
"15801445"
Massaging with forumula but not implementing yet.
Code:
var lastDt = context.get("lastDt"); var nextDt = new Date(msg.payload); context.set("lastDt", nextDt); var lastWh = context.get("lastWh"); var nextWh = +msg.count; context.set("lastWh", nextWh); if (lastDt && lastWh) { var diffHr = (nextDt - lastDt) / 1000 / 60 / 60; var diffWh = nextWh - lastWh; msg.payload = diffWh / diffHr; } else { msg = null; } return msg;
Comment