New Source 2.22 version available for beta users.

[Reinder]

There is a Plugwise Source 2.22beta Release 20120301 (release candidate) available.
If you are a beta user, update your Source by using the Updates button in the Plugwise Source software.

Before you start the update, the release notes are shown.

[Verkenner]

Thanks Reinder,

Today updated to Release 20120301. So far so good.

Cheers, Verkenner

[pvgent]

What are the changes? I can't find this information on the website.

[Reinder]

Before you update you can first read the release notes.

[pvgent]

I'm not a Beta user and as i said in my previous post i can't find any information on Source 2.22 on the PlugWise site, not even the release notes.

[Akatar]

is there an update for the circles?
the last weeks i sometimes "lose" some circles
i lose 7 circles or more, an hour later they are back

my network is 31 plugs and never had problems

[Reinder]

Please see the beta release notes below (changes in relation to version 2.21).
If you are a beta user, just use the update button.
You can also use the beta setup, this will update your current installation. http://www.myplugwise.com/source/pwsetup_2.22beta.exe
===================================================================================
Please report any bugs to
helpdesk@plugwise.com
Include the version number of your Source application in your report.
You can find it in the bottom right of the blue title bar.
===================================================================================

Plugwise Source 2.22 beta 20120322

New:
- Support for climate and movement graphs in web server
- Reports: Right click on graph to copy image to Windows clipboard
- Reports: Change period with scroll wheel: Left+Wheel = expand/shrink period, Right+Wheel = move period
- Groups and rooms can be duplicated
- Comparison graph in Reports screen
- Combine 2 or more meters to 1 merged (virtual) meter
- Pro: SLP auto discovery (if supported by SLP)
- Pro: SLP configuration settings, no need for INI file
- Pro: Meter wizard for ModBus devices

Changes:
- Updated German en Greek translations
- Several textual changes
- Central meters and submeters have separate branches in Reports screen
- Use of terms 'meter' and 'sensor' instead of general term 'module'
- Separate icons for Stealth(+), Circle(+) UK and Circles US(+)

Fixed
#3000 Add Module: manually entered module ID disappears from list
#2993 Modbus: Adding new meter requires restart of Source
#2965 ModuleWizard: Module list is empty
#2967 Sense settings: Advanced settings is gone
#2973 Group settings: Triggers are not listed
#2952 Update button results in server error message
#2975 MeterWizard: Add meter causes crash
#2855 Sense: Modules only switch on Sense broadcast if Source is running
#2963 Reports: Production from main meter shifted to start of day on timeline
#2958 Reports: Production not visible
#2949 Reports: Gas usage shown as production
#2945 Crash when opening Sense properties
#2939 Pro: Merged modules are lost in import
#2935 High peak in memory usage at start up
#2931 Translator program does not start
#2930 Reports: From date higher than Until date causes crash
#2928 Backup misses .PLU extension
#2923 Wrong titles in comparison graph
#2917 ConfigWizard: Crash on last page when PC is offline
#2916 MeterWizard: Adding new meter type causes crash
#2915 MeterWizard: Test uses error box for success message
#2914 Stealth is named Circle in module list
#2907 Pro: Merge item in context menu is disabled
#2905 Check marking 'No personal data' pops up error message
#2900 No graph when period starts and ends in same month
#2854 Using decimals in Sense boundaries cause crash
#2833 Context menu not working in schedule list
#2821 Multiple 'Usage' titles in graph
#2777 Pro: Import ignores SED locations
- several crashes

Known issues:
- French translations not complete
- User manuals outdated

[pvgent]

@Reinder

In the fixes list i see : #2949 Reports: Gas usage shown as production, can Source 2.22 measure Gas usage and what hardware is needed.

[Reinder]

Yes, the Source is prepared to read gas values from the Dutch Smart meter (according to the P1 Companion Standard energiened.nl/_upload/bestellingen/publ ... l%20P1.pdf).
What you need is:
1. a Dutch Smart Meter according to the DSMR 2.1 final standard
2. a Plugwise "Smile-P1"

1. To get a Smart meter, you have to wait (for years ) till your grid owner changes the meter, buy a new house (all new installed meter from 1-1-2012 are smart meters according the standard) or ask you grid owner for a "prio plaatsing". See by example Liander: liander.nl/liander/slimme_meter_2012/pr ... atsing.htm.
2. To buy a Plugwise "Smile-P1" wait till Plugwise releases this product. They are now testing with it. I think it will be released around May/June.
If you are willing to arrange a "prio plaatsing slimme meter" I would suggest that you contact Plugwise. I know from a realible source that Plugwise is still looking for Smile-P1 testers, this could be interesting.

How it works, very simple.
You connect the Plugwise Smile-P1 to the smart meter (small box with cable to connect to the smart meter and power adapter). The Smile-P1 must be configured to join you private Wifi.
Download and install the Android or iOS APP on your smart phone and you have the smart meter (actual power usages, historic graphs and gas usages by wifi on your phone and in the Source).

[pvgent]

Reinder,

Thanks for the detailed information, is the Nuon E-manager also a possibility, as i understand this is a gateway with two sensors, one for electricity and one for gas, the sensors count light pulses. The gateway uses Z-wave, ZigBee or 6LoWPAN for communicating.

http://www.greenwavereality.com/solutions/energymgmt/

http://www.nuon.nl/energie-besparen/e-manager/

gr. Peter

[PietjeNL]

Only its useless when u have solar panels The Smile P1 will be able to show that u produce more then u use, atleast thats what the HD off Plugwise says.

[WHB]

Well first I was excited that they finally implemented some more movement support in the webserver. Bit it seems like the movement graphs have gone downhill. In 2.21 the movement graphs were near real time. You would almost immediately see any new movement in graphs. It would even nicely highlight any ongoing movement in yellow. But now the movement graph is lagging 30 minutes or so behind. It does switch the appliances with triggers correctly on/off though. As a lack of support for the Scan in the template engine I would like to (ab)use the graph for automating movement detection.

[PietjeNL]

In the beta i came across a script option, but i dont get it to work with the pte schripts that are in the www folder.
Maybe u can use it to script from a broadcast from the scan when its registered in source?
After updating source it looks its gone, or hidden?

[Darwusch]

Earlier I posted a bug in Source version 2.16. It still occurs in 2.22 beta, but I think I know the cause.
See post domoticaforum.eu/viewtopic.php?f=39& ... 849#p46030 for the bug details.
The motherboard on which the source is setup, has a clock that runs a bit too slow, which is why the clock is synchronized with the internet (time.windows.com) and this is done about 10 times a day.
Since the summertime this year, I noticed that the gaps in the measurements are now around 1 o'clock in the morning, in stead of the start of a new day like in the wintertime happened.
Could this be the reason that data is thrown away?

[T-Rex]

After installing Source 2.22 beta (20120404.2) 15 minutes ago I constantly get two windows popping up, "Schedules" and "HTTP". Looks like debugging information? See attachment.