Fibaro HCL virtual devices newbie questions

[Packet Loss 0]

Hi all,

My first post and new to Z-Wave but dived into a Fibaro setup based around the HCL. I've got a couple of questions I'm hoping for some help with?

1. Recognising the HCL doesn't support LUA but can I set global variables based on what is returned via a crafted TCP packet on a Virtual Device (also will LUA code work in a virtual device on the HCL)?

2. I've got Fibaro door sensor that refuses to be discovered, tried the cumbersome reset process which had worked previously but still refuses, any tips (it was previously working until I joined it with my Razberry)?

3. Is there a stable 4.x release for HCL or should I avoid until post beta (looking at plugins most notably)?

Many thanks

PL

[j.nowacki 5]

Packet Loss, answering your questions:

- you can use string in virtual device to change global variables. I attached one as an example. You can not use LUA anywhere in HCL

- Please make sure, that both buttons are pushed when you try to add a device to the system

- There are no alpha/beta releases for HCL, its 4.X firmware will follow soon after HC2 4.X premiere

To use attached device:

Change IP to 127.0.0.1 and port to 11111.

Now you need authorization. To do that enter

Please login or register to see this link.

fill the field with your credentials in following manner: login:password (e.g. admin:admin). Now change credentials in virtual device.

Please login or register to see this link.

[Packet Loss 0]

Packet Loss, answering your questions:

- you can use string in virtual device to change global variables. I attached one as an example. You can not use LUA anywhere in HCL

- Please make sure, that both buttons are pushed when you try to add a device to the system

- There are no alpha/beta releases for HCL, its 4.X firmware will follow soon after HC2 4.X premiere

To use attached device:

Change IP to 127.0.0.1 and port to 11111.

Now you need authorization. To do that enter

Please login or register to see this link.

fill the field with your credentials in following manner: login:password (e.g. admin:admin). Now change credentials in virtual device.

Many thanks for the response and useful advice, it works as you've described and exposed the API to me now so I have a whole new avenue to explore

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

However I wanted to set the global variable based on a response from the web server. For example if I send a HTTP GET to

Please login or register to see this link.

I want to save the response in Fibaro global variables?

Also I have the FGK-101 and it doesn't talk about holding down buttons to do a reset, is there a mistake in the manual, what's the full process for reset as you understand it?

[ Added: 2014-11-04, 16:28 ]

Door sensor would not join no matter how I reset, however found method on Youtube which involves tapping TMP INSIDE the cover 3 times and it worked perfectly:

[j.nowacki 5]

Packet Loss, D/W does not have auto inclusion, hence it would not simply join network after reset. You must hold down one of the two buttons (one is inside, the other one at the bottom) and click th other one 3 times. That is why I mentioned holding down two buttons.

I am afraid writing value from external server to global variable is impossible, however you can try to achieve it by external POST call e.g. use you Raspberry to process the data and update global value basing on this.

[Packet Loss 0]

Packet Loss, D/W does not have auto inclusion, hence it would not simply join network after reset. You must hold down one of the two buttons (one is inside, the other one at the bottom) and click th other one 3 times. That is why I mentioned holding down two buttons.

I am afraid writing value from external server to global variable is impossible, however you can try to achieve it by external POST call e.g. use you Raspberry to process the data and update global value basing on this.

That's what I did every time, I always put the cover back on before hitting the external TMP button 3 times but have now realised what I think the problem is. The external cover doesn't always hit the internal TMP button properly (so in a sense it wasn't pressed). Obviously by holding the external button and tapping the internal button avoided the issue (as the Youtube video shows).

That solution actually works better for my needs, since at least I know if the Raspberry is setting the global variable via the API, that the Raspberry has actually done what it said it would do (otherwise you never know if the POST actually got there or did anything).