Fire lit trigger

[jabrans]

The only other plug-ins I have are mcsAudrey, ADIOcelot, Touchpad, RCSThermostat, xAP Conduit. This business with `3 displaying ON all started when I inadvertently set it to ON with an event. It is getting updated at the update interval by mcsTemp. I turned on the mcsTemp debug:

10/27/2005 10:53:25 PM~!~mcsTemperature~!~Temp05/08 Data: THU 22:49:30
10/27/2005 10:53:27 PM~!~mcsTemperature~!~Temp05/08 Data: Reading Sensors...
10/27/2005 10:53:27 PM~!~mcsTemperature~!~Temp05/08 Data: Voltage #00=02.70
10/27/2005 10:53:27 PM~!~mcsTemperature Debug~!~Record ID Info=00/, Type = 20, Preferred Device=, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:27 PM~!~mcsTemperature Debug~!~Record ID Info=00/, Type = 21, Preferred Device=, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:31 PM~!~mcsTemperature Debug~!~SendQueue=
10/27/2005 10:53:31 PM~!~mcsTemperature~!~Temp05/08 Data: Voltage #01[B0000000375F7C26]=00.96V 00.96V
10/27/2005 10:53:31 PM~!~mcsTemperature Debug~!~Record ID Info=01/B0000000375F7C26, Type = 20, Preferred Device=`65, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:32 PM~!~mcsTemperature Debug~!~Record ID Info Sensor Present=True, with Device Code=`65 at index 2
10/27/2005 10:53:32 PM~!~mcsTemperature Debug~!~Record ID Info=01/B0000000375F7C26, Type = 21, Preferred Device=`65, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:32 PM~!~mcsTemperature Debug~!~Record ID Info Sensor Present=True, with Device Code=`68 at index 5
10/27/2005 10:53:32 PM~!~mcsTemperature Debug~!~setIO `68 from 0 to 19
10/27/2005 10:53:32 PM~!~mcsTemperature Debug~!~setIO `65 from 0 to 19
10/27/2005 10:53:33 PM~!~mcsTemperature~!~Temp05/08 Data: Temp #01[B0000000375F7C26]=75.22F
10/27/2005 10:53:33 PM~!~mcsTemperature Debug~!~setIO `60 from 0 to 19
10/27/2005 10:53:34 PM~!~mcsTemperature Debug~!~Log Temperature Sensor Count=9, INSERT INTO Temperature(SampleDate,sB0000000375F7C26,s7000080023C6CF10,sB0000000375F7C26V,s6A00080023C37510,sF500080023C94F10,OutsideTemp,TStatTemp,sB0000000375F7C26A) SELECT #2005-10-27 10:53:34 PM# AS QT,7500 AS Q0,6100 AS Q1,9600 AS Q2,0 AS Q4,6700 AS Q5,5200 AS Q6,6600 AS Q7,9600 AS Q8
10/27/2005 10:53:34 PM~!~mcsTemperature Debug~!~V5 Temp05 Temp Sensor 01/B0000000375F7C26 Record Status = True/True
10/27/2005 10:53:34 PM~!~mcsTemperature Debug~!~Record ID Info=01/B0000000375F7C26, Type = 0, Preferred Device=`1, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:34 PM~!~mcsTemperature Debug~!~Record ID Info Sensor Present=True, with Device Code=`1 at index 0
10/27/2005 10:53:34 PM~!~mcsTemperature Debug~!~setIO `1 from 0 to 19
10/27/2005 10:53:35 PM~!~mcsTemperature~!~Temp05/08 Data: Temp #02[7000080023C6CF10]=61.10F
10/27/2005 10:53:35 PM~!~mcsTemperature Debug~!~V5 Temp05 Temp Sensor 02/7000080023C6CF10 Record Status = True/True
10/27/2005 10:53:35 PM~!~mcsTemperature Debug~!~Record ID Info=02/7000080023C6CF10, Type = 0, Preferred Device=`2, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:36 PM~!~mcsTemperature Debug~!~Record ID Info Sensor Present=True, with Device Code=`2 at index 1
10/27/2005 10:53:36 PM~!~mcsTemperature Debug~!~setIO `2 from 0 to 19
10/27/2005 10:53:37 PM~!~mcsTemperature~!~Temp05/08 Data: Temp #03[6A00080023C37510]=164.10F
10/27/2005 10:53:37 PM~!~mcsTemperature Debug~!~V5 Temp05 Temp Sensor 03/6A00080023C37510 Record Status = True/True
10/27/2005 10:53:37 PM~!~mcsTemperature Debug~!~Record ID Info=03/6A00080023C37510, Type = 0, Preferred Device=`3, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~Record ID Info Sensor Present=True, with Device Code=`3 at index 3
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~setIO `3 from 0 to 19
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~setDevice `3 from 17 to 2
10/27/2005 10:53:38 PM~!~mcsTemperature~!~Temp05/08 Data: Temp #04[F500080023C94F10]=67.00F
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~V5 Temp05 Temp Sensor 04/F500080023C94F10 Record Status = True/True
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~Record ID Info=04/F500080023C94F10, Type = 0, Preferred Device=`4, Sensor Known=6, SetupOpen=False, DB Created=True
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~Record ID Info Sensor Present=True, with Device Code=`4 at index 4
10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~setIO `4 from 0 to 19
10/27/2005 10:53:42 PM~!~mcsTemperature Debug~!~SendQueue=
10/27/2005 10:53:55 PM~!~mcsTemperature~!~Temp05/08 Data: >
10/27/2005 10:53:55 PM~!~mcsTemperature~!~Temp05/08 Data: THU 22:50:00

The most interesting thing I see is the line:

10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~setDevice `3 from 17 to 2

It looks like it is there that `3 is getting set to ON. If setDevice is the same as SetDeviceValue. `3 is the only device that has a line like this in the log.

[Michael McSharry]

It looks as if `3 is used for two things. One is the normal temp recording and the other is something else that responds to hs.SetDeviceStatus or hs.ExecX10. The DeviceAction status device change the status as well as some other sensors such as wind to indicate that a threshold has been reached. There are no temperature thresholds that do this.

You may want to observe the properties of `3 vs. those of `4 and see if there is a difference.

Delete the fire lit event and the status device associated with it and observe the `3 without it.

The bigger question is what your strings are all empty. At some time when you are not collecting a Temp05 reading manually write to the device string of `3. Then manually write to the device value and observe if the string value is still present by reading the string and writing it to the log..

[jabrans]

I have deleted the fire lit trigger event and the associated device but `3 is still getting set to ON. Here is what `3 and `4 were in the HS GUI:


And the associated DeviceStatus and DeviceString for `3 written to the log from a script:

11/3/2005 4:27:25 PM~!~mcsTemperature~!~ `3 DeviceString is >On<
11/3/2005 4:27:25 PM~!~mcsTemperature~!~ `3 DeviceValue is >129<

Then I manually set the DeviceString of `3 to 170 using a script. Here's the HS GUI after that:

And the HS log:

11/3/2005 4:29:15 PM~!~mcsTemperature~!~ `3 DeviceString is >170<
11/3/2005 4:29:15 PM~!~mcsTemperature~!~ `3 DeviceValue is >130<

Then a minute later the HS GUI showing `3 was back ON at the same time `4 was updated.

And the HS log:

11/3/2005 4:30:42 PM~!~mcsTemperature~!~ `3 DeviceString is >On<
11/3/2005 4:30:42 PM~!~mcsTemperature~!~ `3 DeviceValue is >131<

`3 gets updated with ON every minute which is when the frequency of my temp collections. There's nothing else I can find that is setting `3 to ON.

Doesn't this line that I posted before indicate that mcsTemp is setting `3 to ON, isn't 2 equal to ON?

10/27/2005 10:53:38 PM~!~mcsTemperature Debug~!~setDevice `3 from 17 to 2

[Michael McSharry]

It means that Homeseer is turning device `3 from Unknown (17) to On (2) and it giving mcsTemperature the opportunity to do whatever it want to do in case that device is associated with hardware or something else mcsTemperature is managing. The message is evidence that something is changing `3 and this something is running periodically.

You mission, should you decide to accept it, it determine who is doing it.

Do you have `3 device in the Analog or Discrete tab of mcsTemperature? Do you have a periodic event at this rate? Deselect the interface from the Interface/Main tab to isolate from a mcsTemperature data collection activity. Make certain you have no mcsTemperature event triggers or deivce actions that could be doing it such as an old one that still hangning around.

[jabrans]

I had `3 listed in the Analog (1) device tab of mcsTemp along with my other temp sensors. I don't have any periodic events running every minute besides mcsTemp.

I removed the mcsTemp from HS View --> Options --> Interface. Select mcsTemp and hit remove. I restarted HS. `3 had status of ON. I ran a script that set `3 DeviceString to 170 and then wrote `3 DeviceString and DeviceValue to the HS log. It wrote `3 DeviceString equal to 170 and `3 DeviceValue equal to 83. I waited 5 minutes and `3 still showed 170 in the HS GUI. Ran the script again this time with only the lines to write the DeviceString and DeviceValue to the log. Again it was 170 and 83. Waited 3 more minutes and it was still 170 and 83. 5 minutes later it is still 170 in HS GUI. Without mcsTemp running nothing is setting `3 to ON. Here's the log:

11/4/2005 9:55:36 PM~!~mcsTemperature~!~ `3 DeviceString is >170<
11/4/2005 9:55:36 PM~!~mcsTemperature~!~ `3 DeviceValue is >83<
11/4/2005 10:00:09 PM~!~mcsTemperature~!~ `3 DeviceString is >170<
11/4/2005 10:00:09 PM~!~mcsTemperature~!~ `3 DeviceValue is >83<
11/4/2005 10:03:05 PM~!~mcsTemperature~!~ `3 DeviceString is >170<
11/4/2005 10:03:05 PM~!~mcsTemperature~!~ `3 DeviceValue is >83<

[jabrans]

After my testing I added mcsTemp plug-in back to the interfaces and restarted HS and now `3 has the correct value in the HS GUI. That seems to be fixed.

Now when I write the DeviceString and DeviceValue of `3 and `4 to the log I get null for DeviceString and the proper value for DeviceValue. That I believe is the original problem with why my fire lit trigger event using temperature actions wasn't working. Here's the log:

11/4/2005 10:18:55 PM~!~mcsTemperature~!~ `3 DeviceString is ><
11/4/2005 10:18:55 PM~!~mcsTemperature~!~ `3 DeviceValue is >121<
11/4/2005 10:19:42 PM~!~mcsTemperature~!~ `4 DeviceString is ><
11/4/2005 10:19:42 PM~!~mcsTemperature~!~ `4 DeviceValue is >69<

[Michael McSharry]

I added a log output at the point where a temp sensor value is being evaluated to be output to the string and value. It is just a test to help isolate where next to look. Give the attachment a try.

[jabrans]

Here's what was written to the log running 4.39.0.2 version and my script for DeviceString and DeviceValue of `3:

11/5/2005 9:38:57 AM~!~mcsTemperature~!~If not same, then writing 70 to device `1, was 
11/5/2005 9:38:58 AM~!~mcsTemperature~!~If not same, then writing 56.8 to device `2, was 
11/5/2005 9:39:01 AM~!~mcsTemperature~!~If not same, then writing 133.2 to device `3, was 
11/5/2005 9:39:03 AM~!~mcsTemperature~!~If not same, then writing 68.7 to device `4, was 
11/5/2005 9:39:37 AM~!~mcsTemperature~!~ `4 DeviceString is ><
11/5/2005 9:39:37 AM~!~mcsTemperature~!~ `4 DeviceValue is >69<

[Michael McSharry]

This shows that mcsTemperature stored the desired value in the string, but the next time the stirng was read the value was blank. I put some more debug output which is a readback of the string value immediately after storing and each location where mcsTemperature stores a variable string value to a device. Try the next one.

[jabrans]

Here it is:

11/5/2005 1:53:19 PM~!~mcsTemperature~!~If not same, then writing 71.4 to device `1, was 
11/5/2005 1:53:19 PM~!~mcsTemperature~!~Changed  device `1, now 
11/5/2005 1:53:20 PM~!~mcsTemperature~!~If not same, then writing 57 to device `2, was 
11/5/2005 1:53:21 PM~!~mcsTemperature~!~Changed  device `2, now 
11/5/2005 1:53:22 PM~!~mcsTemperature~!~If not same, then writing 87.1 to device `3, was 
11/5/2005 1:53:23 PM~!~mcsTemperature~!~Changed  device `3, now 
11/5/2005 1:53:23 PM~!~mcsTemperature~!~If not same, then writing 70.4 to device `4, was 
11/5/2005 1:53:23 PM~!~mcsTemperature~!~Changed  device `4, now

[Michael McSharry]

There is not much further than I can go with this. The code segment that is now executing is shown below. Your log file shows that a value was written to the string, but when the string was read back the value was still blank. It is a basic HS method. I am not aware of anything that would prevent HS from accepting the new string value. The only other thing I can try is to change the order of the Value vs String being set. It is possible that when the value is changed then HS issues a callback to all other plugins. If a plugin, other than mcsTemperature, is acting upon the callback and changes the string of the device then it would explain it. If this does now work the next step is to write a ticket the HST guys may be able to give some more insight. It is not a bug directly with hs.setdevicestring, but there is something related to this sequence that they may be able to help with.

  hs.writelog PLUGIN_NAME, "If not same, then writing " & xvalue & " to device " & device & ", was " & hs.DeviceString(device)
                If hs.DeviceString(device) <> xvalue Then
                    hs.setdevicestring device, xvalue
                    hs.SetDeviceValue device, CLng(val(DeviceValue))
                    hs.SetDeviceLastChange device, Now()
  hs.writelog PLUGIN_NAME, "Changed  device " & device & ", now " & hs.DeviceString(device)
                End If

[jabrans]

Good News! That fixed it.

11/5/2005 3:41:55 PM~!~mcsTemperature~!~If not same, then writing 71.6 to device `1, was 71.4
11/5/2005 3:41:56 PM~!~mcsTemperature~!~Changed  device `1, now 71.6
11/5/2005 3:41:57 PM~!~mcsTemperature~!~If not same, then writing 57 to device `2, was 56.9
11/5/2005 3:41:57 PM~!~mcsTemperature~!~Changed  device `2, now 57
11/5/2005 3:41:59 PM~!~mcsTemperature~!~If not same, then writing 98.7 to device `3, was 99.2
11/5/2005 3:42:00 PM~!~mcsTemperature~!~Changed  device `3, now 98.7
11/5/2005 3:42:00 PM~!~mcsTemperature~!~If not same, then writing 71.4 to device `4, was 71.4
11/5/2005 3:42:20 PM~!~mcsTemperature~!~ `4 DeviceString is >71.4<
11/5/2005 3:42:20 PM~!~mcsTemperature~!~ `4 DeviceValue is >71<

[Michael McSharry]

For your own benefit in avoiding future problems I would suggest that you isolate the culprit that is writing null to the device string. Go back to the prior version and progressively disable plugins until the problem disappears. I know ADIOcelot had that problem in in earlier releases. I will remove the debug code in mcsTemperature and post the new version in the normal place at the top of the thread.

[jabrans]

Questions with HS2.0 and mcsTemp V5

So here's my first 2006 fire lit event question. I've upgraded to HS 2.1.102.0, mcsTemp v5.0.23.

I have created an event named "Duct Fan Control" triggered manually. The event has this action:

Turn ON D3: Living Room Duct Fanr6: Temperature Fireplace is Above 100, Turn OFF D3: Living Room Duct Fanr6: Temperature Fireplace is Below 80

If I run the event with the temp sensor r6 is above 100 it will turn on D3. If r6 falls below 80 it won't turn off D3 unless I run the script manually again. Last year you helped me get it working so I ran the script manually on startup and then it controlled D3. Well a lot has changed since then and I can't get it working properly now.

The device that mcsTemp created named "Duct Fan Control", R37, always show "control inactive".

Last year the problem was that something was interfering with mcsTemp's ability to update the DeviceValue of the temp sensor. I ran a script to write the DeviceValue and DeviceString to the log and they were both correct.

Jabran

[Michael McSharry]

With HS2 the event properties are not available when mcsTemperature starts so it is not able to initialize correctly. I have submitted a help desk ticket on it.

There is another recent thread in the subforum with DeviceAction operation where some workarounds are discussed. I think it was a thread by Steve who had a virtual thermostat that was being turned removed from control incorrectly.