Changes between Version 10 and Version 11 of Proposal

Timestamp:

May 27, 2013, 3:30:34 PM (11 years ago)

Author:

Frédéric

Comment:

--

Proposal

@@ -19 +19 @@
 This will be the central feature of '''pKNyX''', allowing user to create virtual devices which mimics real KNX devices. They will follow the same architecture, like having '''Datapoints''' (aka as Communication Objects), which have to be linked to '''Group Address''' to communicate.
 
-Here is a very simple example of what I have in mind: creating a virtual weather station, which uses informations from a non-KNX real weather-station, or even from a web site, like Weather Underground or so:
+Here is a very simple example of what I have in mind: creating a virtual weather station, which uses informations from a non-KNX real weather-station, or even from a web site, like xxx:
 
 {{{
@@ -32 +32 @@
     DP_02 = dict(name="humidity", dptId="9.007", flags="CRT", priority="low", initValue=0.)
     DP_03 = dict(name="wind_speed", dptId="9.005", flags="CRT", priority="low", initValue=0.)
-    DP_04 = dict(name="wind_alarm", dptId="1.005", flags="CRT", priority="high", initValue=""No alarm")
+    DP_04 = dict(name="wind_alarm", dptId="1.005", flags="CRT", priority="high", initValue="No alarm")
     DP_05 = dict(name="wind_speed_limit", dptId="9.005", flags="CWTU", priority="low", initValue=15.)
     DP_06 = dict(name="wind_alarm_enable", dptId="1.003", flags="CWTU", priority="low", initValue="Disable")
@@ -65 +65 @@
     DP_02 = dict(name="humidity", dptId="9.007", flags="CRT", priority="low", initValue=0.)
     DP_03 = dict(name="wind_speed", dptId="9.005", flags="CRT", priority="low", initValue=0.)
-    DP_04 = dict(name="wind_alarm", dptId="1.005", flags="CRT", priority="high", initValue=""No alarm")
+    DP_04 = dict(name="wind_alarm", dptId="1.005", flags="CRT", priority="high", initValue="No alarm")
     DP_05 = dict(name="wind_speed_limit", dptId="9.005", flags="CWTU", priority="low", initValue=15.)
     DP_06 = dict(name="wind_alarm_enable", dptId="1.003", flags="CWTU", priority="low", initValue="Disable")
 
-    @Device.schedule.every(minutes=5)
+    @Device.schedule.every(minute=5)
     def readWindSpeed(self):
 
@@ -100 +100 @@
 That's it for now. This is only a draft version; final implementation may change, according to feedback/suggestions I will get. But the core is all there. Again, the goal of the framework is to provide very high level tools to build complete and powerfull applications and KNX extensions.
 
-== Other ideas ==
+== Simple rules ==
 
+My first idea was to provide a special API to create rules, in a simple way, like this:
+
+{{{
+#!python
+from pknyx.api import trigger, group
+
+@trigger.schedule.every(minute=5)
+def heatingBathroomManagement(event):
+
+    tempObj = group.findById("bathroom_temp")
+    tempSetupObj = group.findById("bathroom_temp_setup")
+    heaterObj = group.findById("bathroom_heater")
+
+    if temp.value < tempSetup.value - 0.25:
+        heaterObj.value = 1
+    elif temp.value > tempSetup.value + 0.25:
+        heaterObj.value = 0
+}}}
+
+but it implies to define the group objects mapping, which is exactly what we did in the [[#Virtual device|Virtual Device]] example! So, let's see rules as virtual devices... All we have to do is to define the needed Datapoints:
+
+{{{
+#!python
+from pknyx.api import Rule, ETS
+
+class BathroomHeater(Rule):
+
+    DP_01 = dict(name="bathroom_temp", dptId="9.001", flags="CWTU", priority="low")
+    DP_02 = dict(name="bathroom_temp_setup", dptId="9.001", flags="CWTU", priority="low")
+    DP_04 = dict(name="bathroom_heater", dptId="1.001", flags="CWTU", priority="high")
+
+    @Rule.schedule.every(minute=5)
+    def readTemperature(self):
+
+        if self.dp["bathroom_temp"].value < self.dp["bathroom_temp_setup"].value - 0.25:
+            self.dp["bathroom_heater"].value = "On"
+        elif self.dp["bathroom_temp"].value > self.dp["bathroom_temp_setup"].value + 0.25:
+            self.dp["bathroom_heater"].value = "Off"
+
+rule = BathroomHeater(name="bathroom_heater", desc="Bathroom heating management", address="1.2.3")
+ETS.link(device=station, dp="bathroom_temp", gad="1/1/1")
+ETS.link(device=station, dp="bathroom_temp_setup", gad="1/1/2")
+ETS.link(device=station, dp="bathroom_heater", gad="1/1/3")
+}}}
+
+This way, we use the same paradigm, which is always better ;)
+
+== '''linknx''' compatibility mode ==
+
+As I still want to use knxweb, I also plan to develop a special device-like object to mimic '''linknx''' behaviour. All it has to do is to provide the basic xml services used by clients, to display bus status and send orders. Other features, like advanced configuration, rules and so, will be omitted.
+
+Again, we can use the same paradigm as for virtual devices and rules. The framework will provide another custom class for that purpose, but it will be used the same way. It will just add specific features, and the internal structure to act as a '''linknx'''-like server.
+
+== Specific server mode ==
+
+== Unsorted ideas ==
+
+ * xxx