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


abigbear

Member
  • Posts

    6
  • Joined

  • Last visited

About abigbear

  • Birthday 12/14/1962

Profile information

  • Gender
    Male
  • Country
    Vasteras, Sweden
  • Gateway/s
    Home Center 2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

abigbear's Achievements

Newbie

Newbie (1/8)

2

Reputation

  1. If you want to have a switch in Home Assistant that turns on/off z-wave switches in Fibaro Home Center 2 then you could define this in configuration.yaml switch: - platform: command_line switches: <switch01>: # This is a unique id for switch in home assistant, that can be used in automations etc referenced as switch.switch01 switch.switch02 etc if you have more friendly_name: 'Fibaro Wallplug On/Off' # Direct access HC2 command_on : 'curl -u <userid>:<userpassword> -X POST "http://<HC2 ip address>:80/api/devices/<deviceid>/action/turnOn"' command_off : 'curl -u <userid>:<userpassword> -X POST "http://<HC2 ip address>:80/api/devices/<deviceid>/action/turnOff"' It works BUT it has a few inconveniences I have not found out a solution for yet: - delay of about one minute. If you issue the URL directly from Chrome the on/off is instant, but not using curl - the icons in Home Assistant does not show that the Home Cneter lights are on. That is even after you pressed the button and the lights are on, it does not show. It works ok for me in automations where I want to turn on/off according to sun or at specific times where immediate action is not vital. Still irritating though. Please note that you need to change <> and text between to valid information for your installation
  2. Hello, I've recently moved to the ZWave world when I bought a HC2 and some devices. But I still have some i Nexa and Telldus switch devices I can use outside and have not found any suitable ZWave ones. Therefore the idea to control the Nexa/Telldus devices using HTTP requests to the API of Telldus Live. Just simple things like turn on and turn off the switches. The IDs of the switches I thought I could input into the LUA code of each Virtual Device to keep it simple. What I don't seem to find any good information about is the whole Oauth thing with authorization requests, access tokens and stuff until I can finally to the request regarding the switches. Has anybody any clues or hopefully already has done this successfully? I found some documentation on the APIs at Telldus: http://api.telldus.com/documentation/phpLive (only PHP examples I don't really understand, strange language PHP) and then some more 3rd party doc at https://market.mashape.com/warting/telldus Need help/directions both on how to do the http-requests in LUA and the more Telldus API specifics. Once I understand those important things I'm sure I can get rest of the VD to work, it should be little more than on/off buttons and maybe some status message... We'll see once I get there. Look forward to some input and/or experience in the matter... Kind regards Bjorn
  3. Great, even though strange with the mute thing. I just found some documentation (very cryptic) on http://<HC2IP>/api/devices/<deviceid> and when I put my deviceid in there with the correct IP address I got a long JSON feed where I found more variables. Like state which tells if the player is playing or not. Could not get mute to work with this information either though. But state works fine. local state = fibaro:getValue(id,'state')
  4. Great, even though strange with the mute thing. I tried variants like muteOn and muteon but those did not work either. Any ideas on how to determine if the player is playing or if it's paused or stopped? I've tried the simple ones in case there were fields for Status and status and Time, time, timeRun, timerun but with no luck.
  5. I'm so happy for finding this. You are all incredibly talented. I had the same problem as you pomfritz and could also change the volume just like you. I experimented with pause and play instead of turnOff and turnOn and got them to work as they should. Maybe Fibaro has done some changes to the plugin from on version to another? (I run 4.100) fibaro:call(134, "pause"); fibaro:call(134, "play");
×
×
  • Create New...