earto

Very frustrating. See here from 2 years ago:

+1 Absolutely would use this. I hope Fibaro implements digest authentication (username/password) so that my cameras can work again too.

Peter put me on to this post which didnt come up in my search. Before I read any of this I came to the same conclusion and was shocked by the poor inrush protection in some switched mode power supplies. We could blame Fibaro but overall I think they make great quality products, even if the support model is sometimes frustrating. Do we want theses modules to be twice the price and larger in order to suppress inrush currents of e.g. 100A for 1-2 ms? If some enhancements can be made then great, but its not always simple. Personally, I'm going to just avoid any cheap/small/poor quality switched mode power supplies.

Thanks Peter! Annoyingly, that didnt come up in my search I agree and after some quick research on Mr Google I came to the same conclusion. Be wary of small and/or cheap switch mode power supplies!

I just had the same issue with the 2nd channel of my FGS-223 being stuck on after months of no problems switching my 9W LED stair lights. I tried power cycling the unit and messing with settings including a re-initialise. Finally out of desperation, a sharp tap on the back of the unit released the relay. Initially, I didnt think the in-rush current for these LED lights would be a factor but now I'm not so sure. There's only 3x 3W LED lights, each one has its own small driver. After some research, it appears that smaller/cheaper drivers (switched mode power supplies) lack the inrush protection of higher quality drivers. One article suggests that the inrush current of smaller drivers is typically 40-70A for 1-2 ms (at the worst time/highest point in the phase)! Yep, that would do it! Time 5 milliseconds/division. Peak inrush is just more than 50amps for around 1.5milliseconds. Blue - mains 100V/division: Peak Yellow - input current 20amps/division My LED stair lights were already in our house and look like first generation LED lights. I could make a circuit to limit inrush current but I'll probably just replace them with better units. In conclusion, be wary of cheap/small drivers for LED lights - especially multiple in the same circuit. https://www.adminstrumentengineering.com.au/instrument-engineering-news/resolving-inrush-current-problems-with-led-divers

Same here. In the last few days the 2nd channel of my FGS-223 double switch 2 has been stuck on. The 1st channel still works perfectly. The 2nd channel only has 9W load to some LED stair lights which go on automatically every night. I tried power cycle and resetting to default settings. Maybe a known hardware issue?

Sorry for the delay in replying. Yes, this works perfectly! Thanks.

@Labtec, Did you find an answer to this? I want to configure a bed-time scene which can trigger the Logitech OFF command (this turns off TV, AV receiver, satellite box etc.) The logitech plugin has a single ON/OFF button but I think just off should be possible. Maybe need to send the HTTP command directly? Thanks, Elton.

Thanks anyway @I.Srodka. I might give one of my kids some pocket money to press the keys - I know its a minimum of 2000 key presses (message and OK). Who knows how many there are, I've read 300 already and it still says 999+....

Hi guys. Sorry to open an old thread but did you ever find a solution to delete these notifications? I have 999+ notifications shown at the top and there's too many to delete! They are not sent to an individual so must be stored somewhere in the HC2. Thanks, Elton.

Hi @I.Srodka, Thanks so much for your reply. In the notification center there are no notifications listed. But your LUA code gave me a hint. I didnt try your code yet because there wasnt anything listed. Maybe I need to be clearing it using HomeCenter.PopupService.remove(id) somehow? To clarify, I sent the notifications as "Info" using this LUA code: HomeCenter.PopupService.publish({ title = "Backyward Motion", subtitle = "The House is UNOCCUPIED", contentTitle = "House UNOCCUPIED", contentBody = "Backyard motion was detected while the house was unoccupied. See cameras for real time video", img = "http://icons.com/icons/info.png", type = "Info", buttons = { { caption = "OK", sceneId = 0 } } }) Sorry, I just realised that maybe I called it the wrong thing - it shows as "Notifications" in the app! I cleared the data in Android by going to settings, apps and then "Clear Data" and "Clear Cache". After this I restarted the App and its like default, you have to enter the passwords again and find the HC2. But the notifications all came back again. Thanks, Elton.

Please help! I added a scene a while back to test push notifications to a mobile phone. Long story but basically I left it running and now theres 999+ notifications on my Android app (see screenshot). Does anyone know how to clear the "Current" notifications? There's too many to clear individually. I tried deleting the mobile device in HC2 and re-adding it. Also tried deleting the Android app data. Thanks, Elton,

Totally agree. I suspect this one is on their radar after reading some of the other forum posts. There's no way in hell Fibaro would use plain text authentication for their own products. So only allowing plain text authentication towards IP cameras is madness.

IP camera support on Fibaro is about to become history. I love my HC2 but unless Fibaro implement simple "digest authentication" for IP cameras, support is about to die off. Here's why: Recent vulnerabilities have forced some IP camera manufacturers to REMOVE basic authentication. Fibaro ONLY supports basic authentication. Digest authentication has been around since the 90's and is one step above basic or "plain text" authentication (visible in packet captures). It is becoming more difficult to upgrade or buy new cameras that support basic authentication. Dahua - Since early 2017, basic authentication is now disabled in Dahua firmware. - In 2016, Dahua started signing its firmware which stops downgrades to unsigned versions. - So there's no solution once you have newer firmware installed. Not to mention the lack of support for RTSP, with MJPEG becoming obsolete. Digest auth is needed just to keep existing functionality. Beware of upgrading your IP cameras!

Dahua IP cameras are NOT supported anymore. In fact, most IP cameras with latest firmware will stop working very soon. Here's why: - Recent vulnerabilities have forced manufacturers to REMOVE basic authentication. - Digest authentication has become the LOWEST security mechanism - its one step above plain text authentication (visible in packet capture). - In Dahua firmware from early 2017, basic authentication is blocked. - Dahua has BLOCKED the ability to downgrade to firmware with basic authentication (firmware is signed). Fibaro MUST add digest authentication for IP cams to keep us at the current level.