Report Bugs Plugwise Beta Source April 2009

[jcasteel]

I got this message after hitting the refresh button (latest beta)

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Plugwise.Core.Threads.NodeLogThread.SetList(List`1 list)
at Plugwise.Core.PWCore.QueryLog(List`1 appls, DateTime startdate, DateTime enddate)
at PlugwisePC.Panels.GraphsPanel.btRefresh_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
PlugwisePC
Assembly Version: 2.0.3401.38366
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/PlugwisePC.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Plugwise.Core
Assembly Version: 2.0.3401.38364
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Core.DLL
----------------------------------------
Plugwise.Util
Assembly Version: 2.0.3401.38363
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Util.DLL
----------------------------------------
Plugwise.UI
Assembly Version: 2.0.3401.38365
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.UI.DLL
----------------------------------------
Plugwise.Debug
Assembly Version: 2.0.3401.38364
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Debug.DLL
----------------------------------------
Plugwise.IO.Remote
Assembly Version: 2.0.3401.38364
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.IO.Remote.DLL
----------------------------------------
Plugwise.Images
Assembly Version: 2.0.3401.38363
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Images.DLL
----------------------------------------
PlugwiseConfig
Assembly Version: 2.0.3401.38366
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/PlugwiseConfig.EXE
----------------------------------------
netchartdir
Assembly Version: 4.1.0.0
Win32 Version: 4.1.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/netchartdir.DLL
----------------------------------------
Plugwise.Chart
Assembly Version: 2.0.3401.38364
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Chart.DLL
----------------------------------------
Plugwise.Dal
Assembly Version: 2.0.3401.38363
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Dal.DLL
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Plugwise.Net
Assembly Version: 2.0.3401.38363
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.Net.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
Plugwise.IO
Assembly Version: 2.1.0.0
Win32 Version: 2.1
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.IO.DLL
----------------------------------------
Plugwise.UI.Wizard
Assembly Version: 2.0.3401.38365
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/Plugwise/Plugwise%20Source/Plugwise.UI.Wizard.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Reinder]

@jcasteel.

Has this crash happen again? Is it reproducible?

[jcasteel]

@reinder

I do not yet have a reproducable case. Sorry about that

[jcasteel]

In the latest beta I cannot create any schedules. Even if I create a new schedule and save them, I am not capable of sending them.

[jcasteel]

Ok schedules seem to be working....
sorry about the last message

[jheerink]

The schedules i made in the Beta didn't all work ok
Some stayed on their old schedule and some behaved (according to the usage) irratic, they had consumption on times not planned now or before. The schedules showed ok in the software.
today i cancelled all scheduled first and then resend them. I left the plugwise on at the workstation i use to control the system and will check tomorrow if this worked better.

[yjb]

Not sure if this was ment to be fixed (using V20090424.0):

I'm missing a couple of hours usage data for 2 (out of 9) plugs.
One plug is missing usage data between 01:00 and 09:00, the other one between 0:00 and 12:00.
I'm absolutely positive that I was drawing power from these sockets during the referenced timeframe.

[jcasteel]

I found another problem but I am not sure what the intended behaviour is.

I installed a schedule on one of my devices. It basically shutsdown the power outside the office hours.

One evening I needed to work longer, the plug shutted the power down. After that I enabled the power with the source software. So far so good but then after a while the plug shutted the power down even after the manual override I did in the source software.

I think that the more logical behavour would be the following:

1. Plug uses the schedule according to the schedule as defined in the source.
2. In case that the Plug cuts the power according to the schedule -> user can perform override and the plug stays in the state unless a new state in the schedule is defined
3. In case that the Plug enable the power according to the schedule -> user can still cut the power with the source and the plug remains in that state unless the schedule has defined a new state transition.

[Reinder]

I think tomorrow they release a new beta, main issue solved: sending schedules.

[jcasteel]

Can somebody comment on what the designed behaviour is for the schedules and the overrides?

[jheerink]

I have the same experience, in as well the beta and the standard verstion If you haven a schedule and try to change it temporarily by switching on or off , then the schedule kicks in after a short time and goes back to scheduled program. It would be better if the behaviour would be that it picked up its programmed schedule later on. So lets say the schedules is on at 18:00 of at 23:00 every day. At 15:00 you want it to go on early, put it on, and then it stays on untill the programmed time 23:00, and then continues on its programmed schedule.

We deinstalled the beta because of the scheduling problem. We have a second separate set were we will keep testing the beta. The main set (37 plugs) is now on the standard software, which works ok

[Reinder]

The behaviour of the schedules is as follows: When you override the schedule by switch the Circle through the Source, the Circle will follow the schedule the next exact quarter. So lets say, the plug is off (by schedule) at 22.00 till 23.00 and you switch it on at 22.06 it will stay on till 22.15 and then go off and follow the schedule again. This is how it is implemented in the Circle right now. This cannot be changed through the software, because the software cannot change the behaviour of the Circle. It's a firmware issue.
Plugwise is working on a firmware update (but this takes more time, because the impact is much bigger), where this is changed, because this is requested more.

But, when you use the 'standby killer' function smart, you can achieve the same right now.

For example a lamp. In the schedule select just one (first) quarter when you want the light to go on. The quarters after that moment, select 'standby killer' with about 5W (below the usage of the lamp, but more then 3W). The lamp will stay on, until the schedule had a "off" moment. When you switch the lamp off in the "standby" period, the lamp switch off and stay off. This works fine.

I hope I made clear how to solve this at the moment, till the new firmware is release.

[Rene]

Another alternative is to use Homeseer and the Plugwise plugin;-) This could all be defined as events and actions without modification of the firmware.

Rene.

[Digit]

I am doing it by 'myself' now too. You need more then just wattage to create a good standby killer:
http://www.domoticaforum.eu/topic.asp?TOPIC_ID=1832

[Reinder]

Or use standby killer function and the Plugwise Switch (hope they release this soon....).

There are more roads to Rome