Just a tought

[Sankotronic 2,370]

Quote

Important Notices:

The following software update removes energy data collected during the use of version 5.071 beta due to a changed strategy for handling reports.

For all Z-Wave devices which feature meter capabilities (power, energy, gas, water, etc.) soft-reconfiguration procedure is required due to improvements in support of those device types.

Update 5.072 includes a new version of the Z-Wave software (called Z-Wave 3.0). This version features expanded default device support, the ability to add products using Smart Start technology and many other changes. Please note that this is a beta version and its compatibility will be developed with further updates - not all Z-Wave devices are fully supported.

ATTENTION - installing version 5.072 does not automatically change the existing Z-Wave 2.0 software to 3.0. In order to run version 3.0, it is necessary to restore the gateway to factory settings, requiring the system to be configured from scratch. In future updates we will work on extended device support and provide a mechanism to migrate your current system configuration to the new Z-Wave engine.

 

This is the reason why I still didn't replace my working HC2 with HC3 and I'm still busy coding for HC2. ?

[m.roszak 763]

Not sure what you mean, can you elaborate? 

[Sankotronic 2,370]

5 minutes ago, m.roszak said:

Not sure what you mean, can you elaborate? 

 

Hi @m.roszak ,

 

there is not much to elaborate.

 

HC3 software is still in development and not completely finished. If I had transferred all my 113 z-wave devices to HC3 now, then I will have again to reset them all and include from scratch to switch to new z-wave v3.0. That is a big job to do you have to agree. Not to mention that some other parts of HC3 software still need some effort from your team to bring it to the right level.

 

My HC2 at this moment is functioning exceptionally good and I will finish my coding of UHAS for HC2 even if HC2 will be soon EOL.

After that will start porting UHAS to HC3 and I expect that in the mean time HC3 will get decent stable firmware then I will definitely switch over.

 

Of course for new users that want to start with Fibaro I definitely recommend to go with HC3 or its smaller brothers Yubii Home or HC3L. These are excellent choices for home automation and I do believe in Fibaro team to deliver stable firmware in near future. I will on the other hand deliver UHAS for HC2 before end of this year and next year for HC3

 

[Bodyart 231]

I also believe that, but not in NEAR future because near future since HC3 is available past already and some features as described originally already disappeared ?.

[m.roszak 763]

I just wanted to know for which part of changelog your comment is directed.

I understand Z-Wave 3.0 - this is something completely new and still under development, as you probably know Z-Wave world (protocol) is big enough to make a job for 2 years for a bunch of developers just to implement crucial and mandatory functions.  That is something already ready

Now we are working on migrating all devices to new Z-Wave engine which is smaller task but also not an easy one
Still, Z-Wave 2.0 on HC3 have some advantages compared to the one used in HC2 (for example, thermostats support). 

Regards,
Michał

[afendikov 37]

3 hours ago, m.roszak said:

Now we are working on migrating all devices to new Z-Wave engine which is smaller task but also not an easy one

I'm sure that I'm not first to say it, but - are you think about to implement plugin system ( like in Athom Homey) ?

 

many people here can support and develop devices if Fibaro can provide raw data from device through Z-Wave engine

 

It can be game changer for Matter protocol as well.

 

[m.roszak 763]

"Almost" raw data is available via API (most command classes) - you can check it out in swagger.
You won't find there raw bytes of the frames but full control of most of the certified classes in our system - there is one limitation, if device does not comply with protocol some of the functionalities just won't be accessible.  

[afendikov 37]

16 hours ago, m.roszak said:

"Almost" raw data is available via API (most command classes) - you can check it out in swagger.
You won't find there raw bytes of the frames but full control of most of the certified classes in our system - there is one limitation, if device does not comply with protocol some of the functionalities just won't be accessible.  

 

But "raw bytes of the frames" is most interesting info

 

For example I have MCO Home A8-7 sensor, which is not fully supported by Fibaro.

I'd like to do full support of this sensor and it's possible, if I will have raw Z-Wave data from Z-Wave engine.

 

And for many other devices as well, because we have many Z-Wave devices on our stock

[tinman 1,070]

1 hour ago, afendikov said:

For example I have MCO Home A8-7 sensor, which is not fully supported by Fibaro.

 

which part is missing?

[tinman 1,070]

On 7/19/2021 at 5:10 PM, m.roszak said:

That is something already ready
Now we are working on migrating all devices to new Z-Wave engine which is smaller task but also not an easy one 

 

i assume some free resources there? so maybe you can implement COMMAND_CLASS_ENTRY_CONTROL during lunch break 

 

[afendikov 37]

33 minutes ago, tinman said:

 

which part is missing?

Temperature data receive information from temperature and noise sensors - from both

 

and in noisy environment it sends fire alarm report, because “temperature “ is high 

 

[tinman 1,070]

9 minutes ago, afendikov said:

Temperature data receive information from temperature and noise sensors - from both

and in noisy environment it sends fire alarm report, because “temperature “ is high 

 

lucky me, i have A8-9, no such issues.

 

However,

Please login or register to see this link.

, so i think it should be possible to fix such issue asap ...

[afendikov 37]

1 hour ago, tinman said:

 

lucky me, i have A8-9, no such issues.

 

However,

Please login or register to see this link.

, so i think it should be possible to fix such issue asap ...

I wrote to Fibaro and MCO Home and they answered, that this bug will be fixed. But then A8-7 go to EOL (End Of Life) and bug still not fixed

   @m.roszak, any chance that A8-7 bug still in backlog? 

 

1 hour ago, tinman said:

 

lucky me, i have A8-9, no such issues.

 

However,

Please login or register to see this link.

, so i think it should be possible to fix such issue asap ...

BWT, I have A8-9 too, but with old firmware, which is not supported at all.

 

And I'm dying to have support for this device also.

[m.roszak 763]

A8-7 - in theory supported in version 3.7 but from what I know this is an issue with device firmware - from template point of view noise and temperature sensors tiles does not use the same index (sensor type).
If device reprorts dBA as temperature we cannot filter it.
The best solution for now is to disable sending notifications about potential fire from this particular temperature sensor. 

I will add an issue to our backlog to investigate the source of the problem (maybe we will find some workaround) but if this is on device firmware side - we won't be able to do anything other than contact with MCO.

Regards,
Michał 

[afendikov 37]

Hi, @m.roszak,

 

I have for testing A8-9 also - version 6.4, which is supported by HC3.

 

But here is same - temperature and noise data mixed in temperature readings.

And no motion, no smoke

 

One important note - device have CN frequency and firmware - which is same as EU - 868.4

 

@tinman, do you have motion sensor child in A8-9 EU ?

 

Here is mine device data:

63.0 - multisensor child not showing any data. Same as A8-7

 

Please login or register to see this attachment.

Please login or register to see this attachment.

 

[tinman 1,070]

the EU version with fw 6.4 will get properly recognized (template 882), no mixing, all childs - you will get them as well, if your device would get the template.

Please donwload the template generated from your device, and upload here, so Fibaro can check the diffs.

 

@afendikov

Please login or register to see this spoiler.

 

Edited August 7, 2021 by tinman

[afendikov 37]

Hi @tinman, @m.roszak

 

Templates attached for both A8-9 and A8-7

 

also ticked created for Fibaro - #79148

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Edited August 7, 2021 by afendikov

[afendikov 37]

On Z-Wave 3.0 engine A8-9 have all childs and show temperature and noise data correctly.

There is no motion sensor, but have multilevel sensor with 0 and 1 values.

Can't check - is it motion or not, because data is lagging - delay to provide all data from device to HC3 is like 10-15 seconds

 

For A8-7 - there is also, 6 childs present - only noise child is missing.

 

But temperature received and stored correctly for both devices.

 

So, on Z-Wave 2.0 engine - there is only software glitch ( when temp and noise mixed in one child ) , all devices are working good

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

[tinman 1,070]

2 hours ago, afendikov said:

On Z-Wave 3.0 engine A8-9 have all childs and show temperature and noise data correctly.

There is no motion sensor, but have multilevel sensor with 0 and 1 values.

 

that's right, your MCO Home A8-9 have different product id (1358) that these supported by Fibaro z-wave engine 2.0 (they have product id 1352).

 

 

2 hours ago, afendikov said:

Can't check - is it motion or not,

 

right, it is motion, advertised as multilevelsensor. 

 

2 hours ago, afendikov said:

because data is lagging - delay to provide all data from device to HC3 is like 10-15 seconds

 

You should set some parameters (lot of them...), these devices are "loud" in manufacturer default configuration.

 

For the Z-Wave 3.0 import

 

Please login or register to see this image.

/monthly_2021_08/image.png.2a93ce7b8944aa4a0cf25a62bb90e7f8.png" />

 

attached param template,

 

 

Please login or register to see this attachment.

 

and set the values based on manual or e.g. this example configuration:

 

Please login or register to see this spoiler.

 

Edited August 7, 2021 by tinman

[afendikov 37]

882.json tried to upload and :

 

Please login or register to see this image.

/monthly_2021_08/1615632470_Screenshot2021-08-07at21_11_15.png.7fbd03569ea6ae6af6805478718a2c10.png" />