jakub.jezek

Classic connection requires Fibaro ID for authorization and then getting list of Home Centers from your account. Then it logs you "locally". If you go to Login offline from app login page then after filling IP adress and login credentials to your Home Center, you should be fine. 🤞 🤞 🤞 🤞

Recovery image is corrupted. Send it for Re-Flash to Fibaro service. Write to [email protected] regarding service.

I do not know how in your cases, but Fibaro ID service sends me e-mail that my Home Center went Offline.

Hello @calza, Thank you. Yes, it is missing there. Generic modbus QA, that I used was written for us and there is no other development unfortunatelly, so I do not know if I will be able to add units on my own.

I see, I miss this in your 1st post. You have a ton of non-Z-Wave devices. Then why not to use Home Center 3 instead of Home Center 3 Lite? Home Center 3 Lite is ment for small project with minimal integrations.

Certified Z-Wave devices should work no matter if template is implemented or not. What devices do you run that you need extra Quick Apps for them? Also you can change device parameters by "Adding parameters" and set them according to device documentation (parameter number, size in bytes and value). Then if this change of parameters changes how device is reporting then soft-reconfiguration can be applied to read how device is behaving after setting parameters.

Yes, central scene events do work. Just associations and direct control on the device do not work.

Hi@Tomasz K. , No they still Are not compatible.

Hi @Peerf, Connect Fibaro Smart Implant and Ajax Relay to 12V. Its shown here As example, you can set Ajax Relay to trigger in case of Alarm and Smart Implant sends this to Fibaro Home Center to trigger scene.

@Neo Andersson, you set it correctly, if it works locally. There is no RTSP that works remotely outside of lan network with Fibaro. Maybe Dahua and NICE cctv plugins where RTSP possibly works remotely, but with generic cameras it does not.

Hi @petro_cz, I would use Smart Implant, its output can do 12V or 24V, or Smart module, its output can do any Voltage you connect into IN terminal. It would be just ON/OFF control.

Hello @Neo Andersson, If I'm not mistaken then Fibaro does not have cloud ready for RTSP yet the same way they have it for MJPG. So now you can get live view remotely via app only via VPN. So for now I would use app from NVR manufacturer to get camera live stream. @A.Socha or @m.roszak, Please, correct me if I'm wrong, but that is what I heard or read somewhere on this forum. I would recommend to integrate cameras via NVR to Fibaro, so it would be <IP_of_NVR>:<port_camerra_running_at>/<path_to_stream>, for example: 192.168.81.2:61100/isapi/102/preview. Best regards, Jakub

Some processes regarding data flow in cloud needs to be changed to get RTSP working remotely. We ofthen recommend to use NVR with dedicated App with Fibaro as there are all features regarding crossing camera view. Fibaro is just looking on camera streams.

Hi @JohanSj, Other than BIOS battery, there is no battery inside.

Hello @Neo Andersson, I would recommend to catch what you sending via Wireshark in HC3 GUI or Swagger while changing the variable. Then I would try to catch what you sending via Javascript and then compare headers. What I saw back with HC2, and I see you got HC3, was need for Content-Lenght in headers. API commands seems to move from HC2 to HC3 platform, so maybe it is still needed. It is part of VD I posted several years back on marketplace: Global variable change - testing device | Marketplace FIBARO Also, I think it is also part of VD generated my Reboot VD Generator: FIBARO Reboot VD generator - for both HC2 and HCL - Tutorials and Guides - Smart Home Forum by FIBARO Download VD -> Open it in TXT editor -> Pass it to JSON validator (example: JSON Formatter & Validator (curiousconcept.com)) -> Check the button how it is formated.