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


suds32nz

Member
  • Posts

    84
  • Joined

  • Last visited

Everything posted by suds32nz

  1. HI I own an HCL running firmware 4.501 I am wanting to control some of the features remotely with an HTTP URL I have done this some time ago using http://username:password@ipaddress/api/callAction?deviceID=236&name=turnOn Now if I run this url I always get a login dialogue i.e. it does not seem to except the user and password Any ideas would be greatly appreciated
  2. espone from support below, I would have thought a system that costs so much would have log files you could check yo see what is going wrong, might need to look at a new system. hello, Thanks for your e-mail. We couldn’t reproduce your issue using our testing devices, but I consulted this issue with our developers and reported them this issue (I hope it will be fixed in one of the next updates).. You can try to synchronize it, till it works or try to update system to version beta 4.141 (it may help). Unfortunately right now we don’t have any workaround for this issue We are very sorry for your inconvenience.
  3. I have it included and moved the ccl within 0.5 meter of the lock. The issue is the sync never completes. Not sure if it is maybe an HCL issue
  4. Given up with support sorting this, have had no response since last post
  5. Well the saga continues Had this response from support 5 days after logging the issue Your issues has been probably repaired with last update of our software, so please update your system to the newest version (4.161beta).Nevertheless during synchronization process please make sure that:1) Batteries of your device are fully charged.2) Your lock need to be also close to your HCL.3) After you start synchronization please don't "refresh" page etc. just give system time to synchronization. "Also after you start synchronization" you probably need to do some action on the lock (to "wake up" it and communicate with HCL).4) Please remember that such procedure can last up to 30 minutes (in some extreme cases even 1hour). This I did and had exactly the same issue, I have responded back to support on the 17 th now waiting again. The issue to me seems to be the sync is never completed, are there any logs that could be checked ???
  6. Have logged a support call re this issue on the 12th so will see what happens. No luck last time
  7. HI. The issue has always been that when you sync the lock to retrieve the pins it gets about 20% through then stops (latest firmware for HCL) You can keep trying to sync but it never completes on previous firmware the system use to lock up. I have tried removing and re adding m multiple times. I did contact support the very first time but e=was un resolved (lock pin had just been added and was beta) I would really like to get this working but had no luck. HCL ver 4.160 Yale lock SYEDDB/220/NZ module Z-wave SYEDDB/220/NZ Lock and unlocking is flawless
  8. thanks will have to see if there is anything that will help or parameters I could add ??
  9. lock is only 1 meter away from the HCL, inclusion always works fine and says Completed Added and removed multiple times over the past year to try to get it to work. But as mention the sync never finishes. Real bummer as would bee keen to get it to integrate fully.
  10. Using an HCL on 4.154 still no luck Basically it never completes the sync process, gets about 25% though then stops
  11. HI Still no luck with my lock, do you need to remove it and re add it to get the slots to work. Have a yale lock - Touchscreen Digital Deadbolt - SYEDDB/220/NZ Works fine as a lock ie lock unlock. Device kind:Door lock Producer:ASSA ABLOY Version:83.32 Configuration:Device configured Thanks
  12. Thanks, Yep been thorugh cook book to compare and is this is quite basic it all looks the sames as the book. Reboot VD works but could not use 12.0.0.1:11111 anymore tried a few options with this one with no luck suspect it is but in there Beta since 4.130
  13. HI I am running 4.134 (just updated issue was in 4.133) I have a very simple VD to change a variable Variable is "Position" VD Below PUT /api/globalVariables/Position HTTP/1.1 Host: 127.0.0.1 Authorization: Basic a2VsdmluQHN1ZHMzMi5jby5uejp######## admin user and password (in my case admin is email address) {"name":"Position","value":"Home"} And PUT /api/globalVariables/Position HTTP/1.1 Host: 127.0.0.1 Authorization: Basic a2VsdmluQHN1ZHMzMi5jby########## {"name":"Position","value":"Out"} Screen shots attached. Basically it does not work anymore but I can't work out why, I have other VD's that have stopped working but the Reboot one works fine
  14. Strange that you say concept as it was clearly advertised on the Fibaro website and was the main reason I purchased the HCL. Very poor when a company can advertise such things but never produce them. How about some specs for ports so we can develop our own Fibaro plugins
  15. AS far as I know they were never made, also very keen if they are out there
  16. Strange My other VD's dont work either ie simpple one to change a variable that has always worked no longer works, as well as some camera ones. Only difference from mine to your can be is admin user - which for me is now an email address (which chamged a while ago with an update) But very keen to atleast get this one going, any ideas would be appreciated. All I did is import this VD and change the ip etc Just sorted this on, I can't use 12.0.0.1 port 11111 had to change it to the Actual Ip and port. So now just have to sort the others
  17. Anyone having issue with a VD to control there foscam camera since 4.133, (may not have worked with 4.130) Neither of my VD's work to control the camera anymore. ie move or arm etc VD's unchanged really not sure when they stopped as had assume all was good but definitely been working since 4.120 (did not check with 4.130) Any help wold be appreciated
  18. 4.133 not working GET /api/service/reboot HTTP/1.1 Host: 192.168.0.22 Authorization: Basic # admin:password coded base64
  19. If you ever get it working let me know as i have the same issue on 4.131 and 4.133
  20. HI just an update if anyone has struck it but since 4.131 mrs foscams can no longer be armed etc with this virtual . Both were working now neither works. Nothing else was changed
  21. I Have a Yale ZWave lock with and HCL works great (only have local and unlock though). Using Unlock to turn off alarm Touchscreen Digital Deadbolt - SYEDDB/220/NZ Wave module installed
×
×
  • Create New...