Maarten, please let me know if there is any beta testing I can do . Don't have a Synology, but would love to run the software. Release early, release often and such and so on
--
This is a sig
HouseAgent - my home automation software
HouseAgent - my home automation software
I will contact you when the first "beta" version is available. Right now it's really user unfriendly, input goes with mysql insert etc [:)]
--
Maarten Damen
www.maartendamen.com
--
Maarten Damen
www.maartendamen.com
HouseAgent - my home automation software
Ok that would be fine. There is no hurry for what I'm concerned. I will wait with further implementation of PlugWise untill some of the additional modules are released. Pluswise should thank you, because the primitive Linux support you already delivered is a big plus for me . That makes me think that Plugwise is one of the better solutions currently availabe in the Netherlands.
I do know a fair share of python, but I don't have the time/will to start my own project. But if you were to release the code, I might be able to actually submit patches for bugs instead of just noticing said bugs.
Good luck and keep us posted
--
This is a sig
I do know a fair share of python, but I don't have the time/will to start my own project. But if you were to release the code, I might be able to actually submit patches for bugs instead of just noticing said bugs.
Good luck and keep us posted
--
This is a sig
HouseAgent - my home automation software
When beta is available, I'm like to cooperate too.
HouseAgent - my home automation software
I am planning the first beta end of april, if anyone is interested in testing please send me a PM!
--
Maarten Damen
www.maartendamen.com
--
Maarten Damen
www.maartendamen.com
HouseAgent - my home automation software
I am currently looking into event design, what should it contain?
Any new fresh idea's are welcome.
<b>What should it contain?</b>
Each event should have a trigger or multiple conditions:
For example:
if device value is (equal to, not equal to, bigger then, smaller then)
Then each event should have an action or multiple:
- Switch on device x
- Power down power consuming device y
--
Maarten Damen
www.maartendamen.com
Any new fresh idea's are welcome.
<b>What should it contain?</b>
Each event should have a trigger or multiple conditions:
For example:
if device value is (equal to, not equal to, bigger then, smaller then)
Then each event should have an action or multiple:
- Switch on device x
- Power down power consuming device y
--
Maarten Damen
www.maartendamen.com
- RDNZL
- Forum Moderator
- Posts: 1008
- Joined: Sun Sep 24, 2006 1:45 pm
- Location: Dordrecht, The Netherlands
- Contact:
HouseAgent - my home automation software
I'm busy with events too, it's not easy...
A trigger and a condition are almost the same, except for the fact that triggers are checked frequently.
If a device status changed I call a routine to see if there are events of the type "devicechange event". Same for time based events (for now every minute).
You can only do greater/smaller checks on values with numbers, otherwise it's only = or <>.
A trigger and a condition are almost the same, except for the fact that triggers are checked frequently.
If a device status changed I call a routine to see if there are events of the type "devicechange event". Same for time based events (for now every minute).
You can only do greater/smaller checks on values with numbers, otherwise it's only = or <>.
HouseAgent - my home automation software
I've recently changed my event system and added time as a trigger type. And with this trigger type i can now specify trigger values like "2 0 * * *" (every day at 00:02, works like crontab). This way i have a very flexible scheduler with conditions.
HouseAgent - my home automation software
Hi Maarten, in which language do you have programmed your application?
Like the looks of it
Like the looks of it