Search the Community

All, randomly I see some of my devices bahving strange. First TZ75 roller shutter occasionally, w/o any pattern would either open or close the blinds without any scene or other user interaction. Then recently my garden gate would open (Nice engine with IBT4ZWAVE module) though not requested through script or any other user action. Worst so far, my irrigation, managed with an FGS2x3 (Fibaro device) would just switch on, not even sending a proper signal back to the HC2, so it seemed switched off although it was actually switched on. Some additonal information - IBT4ZWAVE - I can see the action in the HC2 log, but it's certain that no scene or user request was triggering the action (remotes were at home, we were on vacation, no scene related to gate was active) - TZ75 - Most of the times there is a log entry with multiple values added e.g. open 70% or close 100%. Funny thing is that I don't have a scene requesting to open by only 70% - FGS2x3 - The most scary one as neither in the log file nor in the Yubii application would state that the switch is off, although it's running Happy for any advice. Let me know what else you need to know. Setup: HC2 ver 4.620

I have added a new HCL as a slave in a Master gateway (HC2). Issues: - Rooms are not being synced in either direction - Some of the master devices show up in the HCL slave, but unconfigured, with no names and with rooms not assigned - List of shared devices are empty Both gateways are running 4.520 Have tried the following: - Master (HC2): Under Config>Gateway Connections I have Imported multiple times. Slave rooms show up, are checked, but after a quick Sync the are not added to room list. - Master (HC2): Under Config>Gateway Connections I have Synced multiple times - no effect what so ever - Master (HC2): Under Config>Gateway Connections I have Deleted the slave (HCL) and re-added. No luck - Rebooted both devices twice. No luck I would be very happy for any advice. Device list on slave:

hi all, This is my first post on the forum SO HI!! We're hoping someone else is experiencing the same issues. Fibaro has been running very well for the last 18-24 months then this, it comprises of a gradually built system with the following HC2 and 30+ fibaro modules (doors, motion, flood, Smoke, rgbw, dimmer 1 and 2s, relays. almost the whole suite) and 4 older aeon lab relays that were laying around. I got some bizarre problems with 4.08 - 4.10 upgrades in that motion sensors stopped working, scripts changed doors from breached to armed, scenes stopped working altogether that worked fine for over a year, door sensors stopped working and loads of other issues. i thought it was because of lots of tinkering over the course of that time; so decided to restore and start fresh. I firstly installed all latest firmware 4.100 before adding any modules. Things got weird door sensors wouldn't work and toggling between awake, update ok, awake, update ok for hours gave up and took out the batteries after 4hrs removed batteries and rebooted reset and re-added nothing changed motion sensors ran like strobes and didn't work at all in scenes inspected all their parameters and most were nothing like default replaced the settings to what they are meant to be and they just won't take the new settings. Only wake for 1-2 seconds only then back to disco mode aeon labs relays that worked in 4.08. They add in and show that they work in the app/browser but don't respond at all (lights stay off) scenes don't work with variables the list goes on............. What took originally a few hours to redo a year ago i ended up wasting 12+ hours yesterday investigating all i could Today i decided again to do a fresh install buy installing modules that had issues in 4.100 straight into 3.600 (basically battery operated Motions, Flood, Smoke and door reeds, PLUS the 4 Aeon labs relays). Made sure EVERYTHING was removed on the previous install of 4.100, eprom reset every module and then recovered to V3.600 They all work fine! WOOOHOOO i'm getting somewhere..... then Updated to V4.100 and all aeon lab modules doing exactly the same ARGGGGGGGGGGGGGHHHHHHHH and most battery devices gone from the interface and doing crazy stuff again when removed and then re-added I'm hoping i'm not alone here but this is the 3rd attempt with no luck. It's that bad that the whole automation system is disabled plus all batteries removed (over the disco) and we're just using it as a normal lighting system with button dimmers:( IS THERE ANYWAY of restoring and upgrading to V4.08 only? PLEASE HELP Thanks in advance for any assistance Regards Szymon