Menu

Few questions about KnxWeb as visualization..

RR
2009-01-22
2012-12-14
  • RR

    RR - 2009-01-22

    Hi,

    somehow I got to the state where I successfully connected KnxWeb as visualization module to my Perl-based home automation driver. Now I have few probably basic questions :

    - I miss some objects for certain devices that are needed at least in my house :
          1. Blinds(shutters - Velux for instance)  control 0-100% (something similar as dimmer, but with some other picture instead of light ? )
          2. Vertical blinds with horizontal slats (0-100% is not appropriate, cause they can travel up/down and turn open/close). In my system I have states (fully upper position) ,half-open (down, but open),shade-open (down, nearly closed), closed (down and closed). Thermostat with its modes is near that, but I wonder what would be proper to add another device based on Thermostat or maybe let user to customize Thermostat device with some custom display text and custom states... ?

          3. temperature and other sensors (I think Text is meant for this, but text, doesn't have background for clean display of values as Thermostat for instance - or am I wrong ?)  Ideally, it would be fine to have Text object + Thermostat's background with some declarative icon... What would be consistent way to do it ?

          4. How could one retrieve some similar icons for other devices (like sprinklers, pool, sauna, bath, spring, etc...) ? Are there any templates or "sources" for existing icons ?

    - I have few begginers problem with design :
          5. To learn from examples, are there any more info about interesting tips'n'tricks using KnxWeb visualization (also how to organize visualization of home) ?
           6. When I go into Edit of some existing design, I don't get black title bar that would allow me to move existing objects around and edit their properties ? Any how to somewhere? Black bar only appears on objects that are newly added to design - is something wrong or is this normal ?
           7. As I already asked in another thread - any possibility to scale objects so they could be more visible for simple desings and possibly used on touchscreens ?

    Last, but not least, I express gratitude for ability to work in such great, but simple enough system that has a lot of possibilities for enhancements and customizations.... Kudos to developers...

    When I sort out those problems and my code, I think I'll also make necessary drivers to connect KnxWeb with Misterhouse....

    Thanks in advance ofr your help,

    regards,

    Bulek.

     
    • RR

      RR - 2009-01-24

      Hi,

      I got a bit further also with my questions (got basic skeleton working now, I'm testing objects):

      1. Probably addition of custom image feature would solve it

      2. My idea: to add another object types : "heat-mode" will stay the same, then we could add "blinds-mode", "simple-heat-mode" (only heat,off), etc.... Each mode would have its own states defined... If we go a bit further we could also make more generic State-machine widget, where user could add custom states (similar as with multiswitch).
      Another idea with Thermostat: one could have additional choice of "Blank" for all three objects (mode,setpoint,temp)... In this case ("Blank") certain field would not be shown on widget...

      3. I figured out that text can be used for this. Even more, I can do nice background color and even make it transparent with this in style: -moz-opacity:0.5;filter:alpha(opacity=50);

      New question: How can I send string to text widget (is it EIS15) ?

      6. I figured out that I have to press modify layout for this....

      8. I'll probably try to add proposed features... IS it better to generalize existing objects, or make new ones ? If I add new object, what needs to be done to be integrated ?
      if I add new types for Thermostat - does this sound reasonable ?

      Thanks in advance,

      regards,

      Bulek.

       
      • EPIX

        EPIX - 2009-01-25

        Hi Bulek!

        It seems you're making progress....

        It never figured ou, what you can make with "style"....
        I begun to collect clues and tips in a wiki, but the wiki stopped....
        Like you I also pointed out the wish of scaling.

        One thing wich is also important for me is to enable/disable the "input"..
        I don't want a "user" to change my heating-system, so it would be great to enhance the system with a simple variable "usermode" on/off and "expertode" on/off
        In usermode only several changes can be made (such as setting temp. in the living-room) and in "expertmode" further possibilities are possible (but I think it's complicated to build this things) so I will try to solve this problme by hosting 2 (nearly identical) designs: one for the user and another for the expert....

        The integration was also a wish of mine, please try to look in the forum: I think Jeff changes the code to find all widgets in the js directory and integrate them to the menu.
        If you make some widgets please share them with us....

        regards from Austria
        EPIX

         
        • knx_user

          knx_user - 2009-01-26

          hi epix,
          i think a better way to match your needs is to define different views.
          i think of a button where i can change the view of knxweb. thats the same you want with usermode, but gives a lot
          more possibilities. for example you can switch to usermode or expertmode. what i want is an aditional mode like a
          "detailmode". my wish where to select the detail mode to see more details about the switches, for example to control
          the individual energy consumption or take a look at the totally burn time.
          i hope jeff will go on with developing in the last time i heard not much from him:-(

           
    • RR

      RR - 2009-01-25

      Hi,

      I've started wiki page here :

      http://linknx.wiki.sourceforge.net/KnxWeb_Objects

      I guess this is also proper spot to do so...

      Regarding inputs :
      my proposition is to have somekind of user access control on level of design. I'd add possibility to goto object to go into another design as well (not just another zone). If we get that, you can put all crucial controls into separate design and have user access control....

      Regarding Scaling: I guess pretty much can be done in style.css and objects code. I also guess (I'm not even JAvascript newbie) that scaling could be implemented in Javascript, but will probably require more experienced Javascript programmer... Maybe someone will join us....

      Regards,

      Bulek.

       
    • RR

      RR - 2009-01-25

      Hi,

      I have managed to add few new objects (simple thermostat, blind, ventilation). The problem now is they all look alike thermostat and is difficult to disseminate them visually.

      I guess there are few options :
      1. why not display their name in special title bar (that doesn't yet exist) ? I wonder if displaying all titles in same place has some special purpose or meaning... I think it's not so convenient as title bars on each object...
      2. I will probably add/leave out some icons to point out the purpose of device...

      Any other idea or advice ?

      Thanks in advance,

      regards,

      bulek.

       
    • knx_user

      knx_user - 2009-01-26

      my scaling solution:
      i use knxweb on a 10" stylistic with passive touchscreen at 1024x768.
      the background image i use has a resolution of 800x600.
      i get the best results with firefox3 in fullscreen mode when i zoom into with two steps (ctr++).
      this works for me...the images dont look blured and a can use my fingernail without problems.

      ot:
      i dont know if there are touchscreens (mybe some industrial touchscreens) wich really can be controlled by finger only.
      but the stylistic only costs about 150euros and do everything i expect from an eib vizualisation incl. low power consumption (about 15w).

       
    • jef2000

      jef2000 - 2009-01-26

      Hi,

      I'm happy to see some life on the Wiki, I was wondering if somebody else that me would ever add something to it.

      There is always a trade-off between simplicity and functionality. If the controls are too simple, they don't do what user want, and if they allow everything user want, they become too complicated to program and to use...

      For the decision to make new controls or extend existing ones, I would say it depends on the amount of common code. If 2 controls have 90% the same code and only a couple of differences, it would probably be better to make a single control with some parameters to tune the behaviour. Another thing, is that if controls clearly apply to different systems, (e.g. controls that are useless for KNX bus) they should be separate, so that user who don't need it can remove it.

      For the icons, I use the one provided by Ziki ( zikibe at users.sourceforge.net ) and modified them using an image editor, but that's surely not the best way to do it.

      Regards,

      Jean-François

       
      • RR

        RR - 2009-01-27

        Hi,

        I've tried to search for user zikibe, but not success... I just wonder if I can get access to those original starting icons...

        What interests me is the empty icon with only background, so I could try to generate new additional icons ?

        Jeff, good luck with kids, have fun. Mine are a bit older, and I already have time for other things... Devote time to them, they will grow up too fast.... If you got few minutes now and then, we will be happy if you can help us with some quick answers... I'll try to do the work and then send you for review...

        I've already added new thermostat like devices, I'm now doing new blind/shutter/drape object with merging Scale output image with Dimmer controls.

        Regards,

        Bulek.

         

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.