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


CelticWebs

Member
  • Posts

    53
  • Joined

  • Last visited

About CelticWebs

Profile information

  • Country
    United Kingdom
  • Gateway/s
    Home Center 2
    Other / Inne
  • Interests
    Jap Performance Cars, tech and gadgets!

Recent Profile Visitors

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

CelticWebs's Achievements

Learner

Learner (2/8)

2

Reputation

  1. By the way, the device is still connected dot the network and I can access the docs and also see the services which all say they are running, the device doesn't respond to the web guy for the main system and nothing in the house is working. When I call the php values I get the folliwing http://HC2IP//services/system/serviceStatus.php {"HCServer":{"running":false,"status":"Process not running"},"Zwave":{"running":true,"status":"Ok"},"FibaroServices":{"running":true,"status":"Ok"},"RemoteAccess":{"running":true,"status":"Ok"}} and http://HC2IP//services/system/systemStatus.php {"status":"IDLE","description":"TXT_IDLE","title":"TXT_IDLE_TITLE","os":"normal","stage":null,"update":null}
  2. My HC2 appears to be crashing every few days. I see a post for HCL saying something similar. Is there any way to access the logs to find out what's causing this issue? No point having an automated home that crashes all the time! Most annoyingly my HC2 is in the attic so that it's got the best central location which means it's a pain to go and reboot it!
  3. I finally had a reply from Fibaro and they confirmed that the devs are aware of fibaro servers blocking the Amazon IP addresses and are working on it. Mine has started working again with the UK / Irish amazon servers. I tried restarting and rebooting everything along with deleting and adding the skill again, none of that made the slightest difference, it just sorted working a few days later!
  4. ***EDIT 2*** It's definitely an issue with IP blocking, waited 45 minutes and tried again, same three Amazon Ireland IP addresses got blocked. Come on Fibaro! Sort it out!
  5. Same here, updated HC2 yesterday and now Alexa doesn't work, I've tried rebooting and also disconnected and reconnected the skill, all items still show as offline. Any further advice from Fibaro techs about this obvious issue? ***EDIT*** Think I just spotted something important. I have a bunch of emails saying IP addresses blocked. They're all Amazon IPs! so the stupid Fibaro system is blocking amazons IP addresses. I've had multiple issue in the past with the system blocking ip addresses, there needs to be a section where you can whitelist ip addresses! 3 of the ip addresses it's blocked are 34.252.97.206 34.242.105.79 18.203.223.188 All amazon IPs as far as I can track! Surely Fibaro haev all amazon IPs whitelisted in the system? Obviously not!
  6. Exactly the same issue here too, my bridge is being locked out all the time. Is there no way of white listing local IP addresses?
  7. So you're saying Jeedom can use HC2 as it's Xwave interface ? Strange that I've never heard of this one before?
  8. Where's the RTSP plugin? I didn't think you could add genuine plugins to Fibaro that weren't authorised by Fibaro?
  9. Not 100% if it's the same issue for you but thats usually the error I get when I type in the wrong reference to a HomeTable ID. usually from a capital letter or something similar.
  10. Please do, I only got this far from your help so I'd be very happy if it gave you something useful back. the code could probably do with some tweaking to tidy it up a little, it is after all, my very first attempt at any LUA coding on the HC2
  11. I've got a bit of a strange issue and I can't see a way to fix it, so I'm hoping somebody who's been a fibaro HC2 user longer than me may have a solution. The Home page of my HC2 states I have 15 lights, I know I actually only have 13 active lights connected to my fibaro. I'd already been through and set all the unused relays to "Other" as device type so I knew it was none of those. I spent a lot of time looking to find what these 2 extra devices were without managing to find the offending devices. Eventually I decided that I'd need to delve in a little bit deeper to find them, I wrote a little bit of Lua to find all lights and then list then along with their current status. It did in deed show 15 devices, not the 13 I thought I had, the weird thing is that two of the devices it shows as lights are actually sensors! The first device that showed was my hallway movement sensor, this is part of a Fibaro Multi sensor. The second is my gate sensor which is a Sensitive Strips door / window sensor. I have multiples of these around the house but only this one shows as a light when queried There is no setting on sensors that has anything to do with lights, why on earth is my Fibaro seeing these two sensors as lights? Any suggestions on how to fix this issue? Excluding and including again is not an options as one is too difficult to get to and is a long distance form the main hub. Any suggestions gratefully accepted! Thanks P.s. I'm on Fibaro HC2 running 4.130
  12. Not sure if this is helpful to anyone else but I modified Franks original garage door / gate virtual device to better suit my requirements. What I wanted was a simple open and close device that would show the current state of the device and allow you to toggle it's current state without having to actually go in to the device to see the open / close button. This device has a few differences from Franks original. On the main Fibaro Devices screen it simply shows a toggle button which alters the state of the device. I.e. if it's open it will close it, if closed it will open. When you open the Virtual device you will also get the options of open and close specifically. During all statuses the icon is changed accordingly to reflect the current operation / status of the door / gate. The worded status of the device is shown as opened / closed or opening / closing depending on activity. To attempt to ensure you don't get a closed icon while the door / gate is opening, pushing a button immediately changes to the appropriate icon and wording then waits a preset amount of time before it checks the sensor again to set the worded and icon status as opened / closed. To attempt to ensure it doesn't check to often, it firstly checks when the relay that controls the door was last activated, then it waits a preset amount of time after the relay activation before it checks the sensor status to confirm it's completed it's operation. Due to some doors / gates taking longer / shorter time to fully open / close, you can of course alter this time. Rather than have the virtual device turn the relays on then off again a few seconds later to replicate a button press, my devices are set to do this automatically via there parameters. I found this more reliable than having the virtual device to turn them on, wait a second or two then turn them off, it's also less traffic across the network with less likely hood of a single getting lost telling the device to turn off. Pretty simple in all and suits my purpose perfectly. Hopefully it will be useful to others too Single_Garage.vfib.json
  13. Out of sheer curiosity, I just excluded from my fibaro and included to my Vera, it does exactly the same thing on Vera Plus, it includes fine and functions correctly, what it doesn't do is update the the status icon, exactly the same issue as the Fibaro. I've contacted Vera to see if they can help, if it's the same issue, my experience of Vera support is very prompt and extremely helpful. So I expect Vera will get it sorted much quicker than Fibaro if it's able to be sorted. Watch this space!
  14. Mine Includes no problem now. I initially had an issue getting it to be included, attempted to get help from Yale who's line is "Fibaro is not one of our approved partners", so I gave up on them and worked on getting it included. From a tip I found online, I tried a new set of batteries, then it excluded and included first time! It didn't seem to have flat batteries but a new set fixed my inclusion issues When it first included, everything worked absolutely perfectly for about 30 seconds, then it was as if the reports from the device had gone to sleep or where reporting on a channel that Fibaro wasn't reading. It locks and unlocks without an issue, click lock, it locks, click unlock and you've guessed it, it unlocks. It just never updates the icon in fibaro to show it's actual status. So I decided to find out what the available Z-Wave parameters were, I looked around on the internet and I cannot find any. So I decided to try the last attempt with Yale, this time emailing them thinking I may get more useful information and help that way. I sent them an email explaining that I was aware that Fibaro wasn't a supported platform and that all I needed was a list of the Available Z-Wave parameters so that I could experiment and get it working properly. The typical absolutely bloody useless reply came back from them and simply said "I am sorry – Fibaro is not one of our smart partners, I am sorry we are not able to support this product or it’s connectivity" no use what so ever to man nor beast! From having spoken to them, it does appear that they don't really have the knowledge to help with anything more technical than getting it included / excluded from a supported system. Anything further than that and they can't help. Pretty poor from such a large company really. If anybody manages to find what parameters are available or if anybody knows a way to get them forth device, please do let me know, I'm sure this thing can work, we just need to know its' parameters to setup proper reporting.
  15. I have a YD-01-CON-ZW-CH Yale Keyless for a night latch. I've come form Vera where I believe it worked fine for the few days I had it setup before swapping to Fibaro. It's added to Fibaro seemingly without issue, when it first included I could lock and unlock and the icon would update accordingly. Moments later the lock still reacts and locks / unlocks but the icon does not update so you never know what the status of the lock is from Fibaro Home Centre 2. I'm assuming it's a Z-Wave parameter that needs setting but I can't find any Z-Wave details for the device at all! Does anybody have any suggestions on ways to fix this?
×
×
  • Create New...