Report Bugs Plugwise Beta Source April 2009
Report Bugs Plugwise Beta Source April 2009
Please report the bugs regarding the Beta release of the Plugwise Source version V20090401 in this topic so Plugwise can read this and hopefully solve it [;)]
- updatewizard crash
- Webserver not backwards compatible, some commands changed.
******
above bugs solved at beta release of 20-4, new remarks:
- the TypeText method of Module object used to return a description of the type of module and now it returns Plugwise.Dal.PWType
-
- updatewizard crash
- Webserver not backwards compatible, some commands changed.
******
above bugs solved at beta release of 20-4, new remarks:
- the TypeText method of Module object used to return a description of the type of module and now it returns Plugwise.Dal.PWType
-
Report Bugs Plugwise Beta Source April 2009
When starting the update process, the application can crash. It looks like some files are locked. When trying it again, the update works ok. Some locking file problem.
Report Bugs Plugwise Beta Source April 2009
Reinder
Can you give a complete list what exactly is changed in the source and the Webserver interface?
And are any of the bugs or wishes solved from this topic
http://www.domoticaforum.eu/topic.asp?TOPIC_ID=1777
Can you give a complete list what exactly is changed in the source and the Webserver interface?
And are any of the bugs or wishes solved from this topic
http://www.domoticaforum.eu/topic.asp?TOPIC_ID=1777
Report Bugs Plugwise Beta Source April 2009
I am sorry, I don't have that list. I'm sure Plugwise have solved as many bugs as they could.
Report Bugs Plugwise Beta Source April 2009
I'm sure you can get your hands on that list, don't you think?
Report Bugs Plugwise Beta Source April 2009
From what I have heard/think the following subject from the list are solved:
Summary (detailed in posts below):
* Plugwise Ethernet controller instead of the USB dongle - ALL -> NO, not planned
* Option to run the software as a service - Wifi -> NO not yet but planned for the future
* Remote web application with full functions as in the client - Chak -> NO not yet but planned for the future
* Explanation of the fields in the MSAccess MDB database - DJF3-2 -> NO, not planned
* Complete the small webserver version PlugwiseServer.exe, is
not running good now! - Chak/Bwired -> YES, must be solved but bugs found.
* Homeseer plugin - Rualblas/ALL -> Yes, by Rene Klootwijk
* 64 bits support - Snelvuur -> Yes, must be solved but not tested
* LINUX Support - Snelvuur/ALL -> No, but working on that (Mono).
* Fill-in registrationkey without
Internet connection is not clear - Snelvuur -> Yes, separated registration possible.
* Fill in custom "Application types" - Wifi -> No, but list updated.
* On Off button on the circles" - All (seperate On Off switch is planned) -> No, with separate switch
* Graphs and Data updated more frequently" - de.lesse -> Yes, solved.
* Publication of the protocol between source and stick - ALL -> No, please use webserver.
* Dimm options - wwolkers -> No, not planned.
* Less flimsy safety ground pins - Lennart -> Yes solved. Metal construction of grounding change
* Automatic restoration of on/off state after a power failure - Lennart -> No, hardware change necessary (relais).
* UK Plugs - Wifi -> No, but planned second half 2009!
as in between solution already a "build in"
PCB product deliverable with crown stone
connection (de Stealth).
* Readings are dropping to 0 while device is in fully use on the circle -> Yes, solved!
see (severe bug plugwise) topic http://www.domoticaforum.eu/topic.asp?TOPIC_ID=2383
Summary (detailed in posts below):
* Plugwise Ethernet controller instead of the USB dongle - ALL -> NO, not planned
* Option to run the software as a service - Wifi -> NO not yet but planned for the future
* Remote web application with full functions as in the client - Chak -> NO not yet but planned for the future
* Explanation of the fields in the MSAccess MDB database - DJF3-2 -> NO, not planned
* Complete the small webserver version PlugwiseServer.exe, is
not running good now! - Chak/Bwired -> YES, must be solved but bugs found.
* Homeseer plugin - Rualblas/ALL -> Yes, by Rene Klootwijk
* 64 bits support - Snelvuur -> Yes, must be solved but not tested
* LINUX Support - Snelvuur/ALL -> No, but working on that (Mono).
* Fill-in registrationkey without
Internet connection is not clear - Snelvuur -> Yes, separated registration possible.
* Fill in custom "Application types" - Wifi -> No, but list updated.
* On Off button on the circles" - All (seperate On Off switch is planned) -> No, with separate switch
* Graphs and Data updated more frequently" - de.lesse -> Yes, solved.
* Publication of the protocol between source and stick - ALL -> No, please use webserver.
* Dimm options - wwolkers -> No, not planned.
* Less flimsy safety ground pins - Lennart -> Yes solved. Metal construction of grounding change
* Automatic restoration of on/off state after a power failure - Lennart -> No, hardware change necessary (relais).
* UK Plugs - Wifi -> No, but planned second half 2009!
as in between solution already a "build in"
PCB product deliverable with crown stone
connection (de Stealth).
* Readings are dropping to 0 while device is in fully use on the circle -> Yes, solved!
see (severe bug plugwise) topic http://www.domoticaforum.eu/topic.asp?TOPIC_ID=2383
Report Bugs Plugwise Beta Source April 2009
OK
That is good News, lots of things should be solved now!
That is good News, lots of things should be solved now!
Report Bugs Plugwise Beta Source April 2009
I will make a list of all API calls that do not work anymore or give other results than previously:
- The .Appliance method of the Modules object gives the following error message: "Unknown member 'Appliance' for type 'Module'". According to the documentation this method should return the assigned appliance.
- The .Module method of the Appliances object used to return a module object which could then be used to determine the specifics of the module, for instance the MacAddress. Now it returns "=PWModule[14:23717D]", where 14 is the Id of the module and 23717D the macaddress. However this is not a string but an object and cannot be parsed.
- The /xml/appliances.xml, coming with the web server, is broken because of these errors.
- The TypeText method of the Appliances object used to return a description of the appliance type, now it returns "Plugwise.Dal.PWType"
- The Date and Time methods of the System object used to return the date and time and both return a complete timestamp (date+time). The is always shown in the Plugwise webinterface where you see two timestamps, one with the time set to 00:00:00 and one the correct time.
At this moment I can not figure out how to relate an appliance to the Mac Address of a specific circle within this version of the API. Because the internals of the Homeseer plugin are based on this relationship, the plugin is not going to work with this version of the API.
Rene.
- The .Appliance method of the Modules object gives the following error message: "Unknown member 'Appliance' for type 'Module'". According to the documentation this method should return the assigned appliance.
- The .Module method of the Appliances object used to return a module object which could then be used to determine the specifics of the module, for instance the MacAddress. Now it returns "=PWModule[14:23717D]", where 14 is the Id of the module and 23717D the macaddress. However this is not a string but an object and cannot be parsed.
- The /xml/appliances.xml, coming with the web server, is broken because of these errors.
- The TypeText method of the Appliances object used to return a description of the appliance type, now it returns "Plugwise.Dal.PWType"
- The Date and Time methods of the System object used to return the date and time and both return a complete timestamp (date+time). The is always shown in the Plugwise webinterface where you see two timestamps, one with the time set to 00:00:00 and one the correct time.
At this moment I can not figure out how to relate an appliance to the Mac Address of a specific circle within this version of the API. Because the internals of the Homeseer plugin are based on this relationship, the plugin is not going to work with this version of the API.
Rene.
Report Bugs Plugwise Beta Source April 2009
All posted bugs are probably fixed!
New version released!
New version released!
Report Bugs Plugwise Beta Source April 2009
The Homeseer plugin works with this version of the beta! Thanks Plugwise.
However, and I see I did not report this before, the TypeText method of Module object used to return a description of the type of module and now it returns Plugwise.Dal.PWType
Rene.
However, and I see I did not report this before, the TypeText method of Module object used to return a description of the type of module and now it returns Plugwise.Dal.PWType
Rene.
Report Bugs Plugwise Beta Source April 2009
Thanks Rene, so everybody here could safely use the beta?
So Plugwise can gather the last remarks and solve them.
So Plugwise can gather the last remarks and solve them.
Report Bugs Plugwise Beta Source April 2009
Nice to see that Plugwise use this forum as a serious test panel. 

Report Bugs Plugwise Beta Source April 2009
From a plugin compatibility point of view everybody could start testing the beta;-)
Another problem I experienced:
I missed one of my devices, the one I added as last although this was a couple of weeks ago. When I started the dialog to add a new circle, it was detected but all the info I had assigned to this circle (appliance type, location etc. was gone). I continued the add circle dialog but end up with a dialog box mentioning 'Een naam mag niet leeg zijn. Voer a.u.b. een geldige naam in' and that's it. The source hangs and does not react to anything.
I restarted the source and started the dialog to add a new circle again. I filled in all the fields and now it is complaining there is already a device with the name specified. And again the source is hanging.
I restarted the source and started the dialog to add a new circle again. I gave the appliance another name and the dialog was completed succesfully. However, I am unable to give the module the correct name because the source is complaining this name already exists but it shows up nowhere.
Rene.
Another problem I experienced:
I missed one of my devices, the one I added as last although this was a couple of weeks ago. When I started the dialog to add a new circle, it was detected but all the info I had assigned to this circle (appliance type, location etc. was gone). I continued the add circle dialog but end up with a dialog box mentioning 'Een naam mag niet leeg zijn. Voer a.u.b. een geldige naam in' and that's it. The source hangs and does not react to anything.
I restarted the source and started the dialog to add a new circle again. I filled in all the fields and now it is complaining there is already a device with the name specified. And again the source is hanging.
I restarted the source and started the dialog to add a new circle again. I gave the appliance another name and the dialog was completed succesfully. However, I am unable to give the module the correct name because the source is complaining this name already exists but it shows up nowhere.
Rene.
Report Bugs Plugwise Beta Source April 2009
Hmmmm, that looks like a strange (user related?) problem.
Could you please send a backup file, with problem description to helpdesk@plugwise.com ?
I am sure they look into it.
By the way, new update posted! version 20090415.6
Could you please send a backup file, with problem description to helpdesk@plugwise.com ?
I am sure they look into it.
By the way, new update posted! version 20090415.6
Report Bugs Plugwise Beta Source April 2009
Reinder,
What backup file do you mean? The backup of the database of the previous version of the Source?
Rene.
What backup file do you mean? The backup of the database of the previous version of the Source?
Rene.