Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

Yes, i know it is not zWave.

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

Please login or register to see this link.

WiFi, indivifual socket control and power monitoring and in the €60 price range.

Posted

Why not just use the greenwave 6 port?

What's the advantage of this device?

  • Topic Author
  • Posted
    Why not just use the greenwave 6 port?

    What's the advantage of this device?

    Well, apart from no local retailers, I am under the impression that the greenwave does not have the neccessary approvals.

    Posted

    ok, I like the device as you sometimes only need 3 sockets and it is nice that you can attach it to the wall directly. But I think it will be difficult to have it included in the HC2. You could probably do it with a virtual device but it won't look / work very nice. For instance the energy measurements could be shown on a virtual device but will not be shown in your energy panel.

    Posted

    It is quite easy to include it... The energy consumption can be shown in a label and even in the log line of the virtual device. The on off buttons can be made using a simple http request to the unit.

    The only issue I see is that it is wifi. The current wifi protocol (802.11**) really isn't suited for device networking. It is designed for relatively few, relatively large packets. So connecting a lot of "thing"-devices which send and receives a bunch of tiny packets can easily overload a wifi network creating huge latency or even crash the router at random. That is why you don't see a lot of wifi gear out there.

    Btw.: if you have a webserver and a bit of programming skills and understanding of http requests, you should be able to "cheat" your meassurements into the energy panel.

    Posted

    Btw.: if you have a webserver and a bit of programming skills and understanding of http requests, you should be able to "cheat" your meassurements into the energy panel.

    Can you explain lithe more about that Dalle1985?

  • Topic Author
  • Posted
    It is quite easy to include it... The energy consumption can be shown in a label and even in the log line of the virtual device. The on off buttons can be made using a simple http request to the unit.

    Which is why i wrote "proper" support. I can control it from HC2, but it is still a "second class citizen" in the HC2.

    Posted

    Btw.: if you have a webserver and a bit of programming skills and understanding of http requests, you should be able to "cheat" your meassurements into the energy panel.

    Can you explain lithe more about that Dalle1985?

    If you pull out the json from the appropriate device json in the api and then modify the json to include the showEnergy, valueMeter, valueSensor, you can http post it back into the virtual device json, and if I am correct, HC2 should accept it as an energymeter. I haven't tested it, but I don't imagine that hc2 is clever enough to distinguish... So you just need a way to update the valuesensor property of the json.

    [ Added: 2014-05-12, 19:15 ]

    It is quite easy to include it... The energy consumption can be shown in a label and even in the log line of the virtual device. The on off buttons can be made using a simple http request to the unit.

    Which is why i wrote "proper" support. I can control it from HC2, but it is still a "second class citizen" in the HC2.

    It's back to the integration theme. HC2 is great for the administrative task of keeping track of everything but the user interface is rubish. I have a way of including virtual devices into my custom interface so for me it would be properly integrated... But you've bought a Z-wave controller.

    I'm sorry, but if you want something that can control EVERYTHING you need to create something yourself. There are no readily available products out there which will do all you ask of it. If the manufacturer makes it, they'll have to support it aswell. Just imagine the size of the task if fibaro had to support all sorts of wifi, zigbee, rfxcom devices along with xbmc, televisions, computers etc. out there... They have a hard enough time to include z-wave products.

    I think it is already a big thing that they give you http support to link in to other devices. This really has nothing to do with controlling zwave devices.

    The only thing that comes close is products like homeseer or domoticz... But even that isn't plug'n'play.

  • Topic Author
  • Posted
    The only thing that comes close is products like homeseer or domoticz... But even that isn't plug'n'play.

    Nope. I am not asking for Plug And Play, i do not mind coding.

    But a good developer guide for the API that Fibaro claims wiull be in 4.x would be nice.

    I am, however, not getting my hopes up for that to materialise even when 4.x is actually released.

    But yes, I am fully aware now that I picked the wrong controller.

    Posted

    If you pull out the json from the appropriate device json in the api and then modify the json to include the showEnergy, valueMeter, valueSensor, you can http post it back into the virtual device json, and if I am correct, HC2 should accept it as an energymeter. I haven't tested it, but I don't imagine that hc2 is clever enough to distinguish... So you just need a way to update the valuesensor property of the json.

    Sorry won't work. You can modify properties but not add them to virtual devices.

    Posted

    I'm waiting for the EU version of this one

    Please login or register to see this link.

    Posted

    If you pull out the json from the appropriate device json in the api and then modify the json to include the showEnergy, valueMeter, valueSensor, you can http post it back into the virtual device json, and if I am correct, HC2 should accept it as an energymeter. I haven't tested it, but I don't imagine that hc2 is clever enough to distinguish... So you just need a way to update the valuesensor property of the json.

    Sorry won't work. You can modify properties but not add them to virtual devices.

    Too bad! Could have been a nice trick though!

    Please login or register to see this image.

    /emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...