ILoveControl

Hi all, Wondering if anyone is using this driver and if it requires you to keep the cr@ppy default firmware or this driver still works if you flash tasmota on the sonoff devices? I'm particularly interested in it for the 20+ switches from R2s to R3s but I have tasmota flashed on all of them.

Thank you for taking the time to clarify

May I ask a really dumb question, been seeing alot of the "WHEN" programming but when I look at composer in the programing sections I only see Else , And Or etc - what am I missing where does the "WHEN" condition come from?

Hi all, I am planning to buy a bunch of these things - Shelly 1PM Mini Gen3 instead of buying a bunch of C4 switches. WIll be using it with the Chowmain Shelly driver. Question before I buy a bunch of them anyone used this specific one or the previous gens and they work as expected?

OK cool - I thought about 2 (dont like the timing one) but then how do you open fully when you want to open it using the relay because it will hit the contact and stop - or am i missing something?

Hi All, Trying to get some ideas for a requirement I have on my garage door. I use a Axxess Card Access to drive a relay to open and close my garage door. I have a Nyce garage door tilt sensor to indicate if the garage door is open or closed. What I a want to do is: I run quite a few solar inverters in the garage and the temp gets quite high, this is easily taken care of by leaving the bottom of the garage door about 20cm open. I wanted to see if I could do this automatically but since the garage door open and closes simply by a relay signal I was trying to see how I could achieve this (opening the door by 20cm only) automatically. I was thinking of a contact switch to the position I needed that open or something else but would love to hear any ideas/advice/have done something like this before from the forum?

So update for all following this: Moved the Dry Contact and Relay from EA5 Terminal blocks to C4-Z2IO and everything has stabilized its acting as intended. Wonder what happened on the EA5 side of things.

I have removed it completely off the EA5 and to a C4-Z2IO (most expensive relay / Contact switch in the world :D) to remove any potential EMI from a long outside wire to my EA5. Would rather blow the C4-Z2IO than my EA5 What this should also show me is if there is/was an issue on that contact port on the EA5 Terminal (if the notifications stop sending when the gate is closed).

As per point 2 above I have changed the Dry Contact twice (two new ones), I have also checked the distance (less than 1mm between both parts of the dry contact), in addition put some padding in the gate and using forceful movement by hand the gate does not move one bit, so I can confidently rule out "natural movement" as a cause. These Dry Contacts (as I tested it) have quite a tolerance in terms of distance like 2cm apart it still picking up as closed. I have no connected it to the C4-Z2IO Contact (Dry Contact for open close of gate) and Relay (to send msg to open close gate) - I am going to test this first before your next suggestion of just disconnecting the sensor all together and see if I am still getting notifications.

Yeah I didn't think of it that way and you 100% right - esp where I live on a hill in a region lighting is just nuts I didn't think about the possibility of long run wires in the ground and transmitting that to my EA5 and causing more damage - Have moved it to the C4-Z2IO as both a best practice and to see if I stop getting all those dam notifications.

I have rebooted a few times tbh so don't think its a reboot thats needed. Good point though! I have changed the dry contact three times already to new ones I bought same outcome.

Hi all, I have a dry contact wired up to my EA5 as per the manual on the +12 and SIG terminal on Contact 1 on the EA5 terminal block. The contact type is one of those that is typically used by alarm systems on doors and windows (uses a magnetic connection). It is on my front gate and is a simple dry contact that shows the gate open or closed. This has worked really well for over 4 years. On Gate open (contact > open) I send a notification via 4sight to notify me the gate is open with a snapshot of the gate camera. Last two weeks it’s been going nuts. Random notifications and false alarms that the gate is open through notifications. So this is where the journey that is driving me nuts started. This is what I have done to trouble shoot: 1. Checked that the contact is making the right contact and the gate isn’t bent or too far away from the contact. There is less than 1mm between the two parts of the dry contact, no play on the gate. 2. Changed out the dry contact (just to make 100% sure) at the gate with the same make/model - same issue. 3. Because 2 didn’t work - took the wire out the terminal at the EA5 on +12 & SIG and cleaned it up stripped some new wire and reinserted - Same issue. 4. Because 3 didn’t work - Pulled a new wire (over 40M) incase there was some sort of breakage for some reason in the wire between the dry contact and the terminal on the EA5 - same issue. 5. Because the physical connection side hasn’t worked - I have even added a 10 second delay on the programming of electronic gate > Open, incase its some sort of movement on the dry contact, then it checks gain to see if the gate is open > delays another 10 seconds before doing one more if open check to send me a notification - I keep getting random notifications,. So what happens with the notifications - it can go the whole day without notifications then randomly (and I am starting to notice a pattern of late at night say 10pm on wards) I get about 40 notifications of gate open with a snapshot (which shows gate was never actually open). Not sure what else to check or if I have missed some updated setting on this contact driver to make it more/less sensitive? So on such a simple thing a bit stumped here…. willing to try any suggestions. I also have a C4-Z2IO almost in the mood to take the dry contact that is connected to the EA5 Terminal block out and try it on the C4-Z2IO incase its something gone wrong on the EA5 - but surely it cant be a dry contact is like one of the dumbest things

I have both and agree with @Cyknight Axxess has some added features. Nyce well like @RAV said they nice - what I prefer between the two: If it is going to be visible - Nyce (they small, battery life is ok and they look great) If its not going to be visible and I need those additional features - Axxess as they more robust IMO. Examples - Door / windows - Use Nyce (they also have a very cool garage door sensor that uses the tilt of the garage door to sense if its open which I use) Front electric gate (open close) - Axxess

Funny - I started getting random notifications on a contact switch simple contact witch connected to the contact on a EA5, I have replaced the contact switch, the cable between the contact switch to the EA5 and I am still getting random notifications (notification is when my front gate opens) - Gate isnt open and it keeps sending notifications.

Hmmmm just checking do they have one for android watches?

My other EA5 and EA1s working fine it's just my one EA5 which is the director as well that keeps showing "starting apps". Reboots not helping so there must be something....

I have a interesting "situation" after upgrading to 3.4.1. Firstly 99.9% is working in composer everything is accessible changes can be made AV working, zigbee, composer all good. The "interesting" part is I have two EA 5 x 3 CA 1s. On all my controllers but the director the on screen navigator is working. On the one EA 5 which is the director I get a Control4 message on screen saying "starting apps" and doesn't go away, have rebooted the controller twice, have left it for 24hrs to start its apps but it just hangs on this msg when I try use the on screen navigator on this EA5 (which is the director). Any suggestions?

Hi All, I have a few Nyce sensors eventually got around to play with the NCZ-3011 (Window/door - contact switch) using the driver: Name: HA Profile Contact Switch Device File: DoorWindow_zb_nyce_3011.c4i On the device properties its behaving as you would assume - it shows sensor open and closed if you open and close it ..... Where I need help is if I go to programming there is no programming options for when its open and closed all it shows is Events: Back Online Battery Low Offline Warning Trouble I would of expected it to have Sensor status of some sort so I can program when the contact is open or closed? Or does one have to then bind it to a normal relay or contact driver and use that instead for programming? Would appreciate the help.

@DanITman - I all for testing! like the fact its on Solar Position

Man love this level of detail thank you! - I was thinking the same to control my inside / outside lighting but just havent found something that works well thank you for the post.

@South Africa C4 user - there is a Victron driver for C4? Really? I use Victron on all my residences didnt know there was a C4 driver for it.

Thats great news thank you - yes that was the LPG sensor. Question - is there a smoke detector driver one can bind to this or how do you typically set it up a Relay? It would be nice if it could come up as a smoke detector in the navigators. They are configured to the shelly cloud I have 10 of them around the house. The "sleepy" nature whilst I understand why (Battery) is a nightmare to get them woken up again so that they can reflect in the network and you can set their static IP nature.

Interesting discussion love the shelly devices just got a bunch of the Smoke plus devices - @Andrew luecke any ideas for support for these smoke & LPG detecting devices in the driver?

Good question, I am in the same boat have three EA5s and two HC300 which has served me for years and been rock solid. Was trying to do the upgrade and got stopped because of the HC300s. Interested in this thread. Sent from my SM-F926B using Tapatalk

Thank you that worked!