Hi @chris ,
I tried to add this Fibaro Relais Switch to the z-wave database - but it seems already to be in as MegaChips, FIBEFGS-213 and endpoints are already defined. What can I do so that this device is recognised?
Regards,
Frank
network_d6a8665b__node_22.xml (11.1 KB)
It looks like the database entry needs some care as tehre are a bunch of errors - it looks like someone has started to fill it in, but not completed.
If you can try and resolve the errors, then we can get this updated. I will do an update tomorrow after which it will be next weekend as I’m away next week.
@chris This looks pretty tough based on my limited experience. To be honest I have no idea where to start unfortunately. Is there an option to use my XML file and override it? What happens with the different manufacturer IDs? I will contribute as much as possible if someone can at least guide me a little bit.
I will fix the following errors -:
thingid contains invalid characters.The others should be mostly information that comes from the device manual.
Done - hope it fits with the requirements. If not please let me know. Thanks again for your kind support.
Could not fix those two errors 
This device looks kind of strange compared to the original Fibaro:
it only has one endpoint and I think because of that it can not have the second manual switch attached to control scenes like the original Fibaro.
That means, I’m not sure if the parameters I have copied from the original Fibaro are correct 
No - I need to go into another admin database and update the manufacturer information - I’ll do that shortly.
This is very strange?
Can you find this reference number on fibaro site? I can’t find it.
After I posted I was leaving HC2 they took me of their testers list so possibly it is brand new item but how from amazon. And how is it brand new and supports
COMMAND_CLASS_CRC_16_ENCAP
I tested the first samples of FGS-213 and 223 and have loads of them working in OpenHab and the xml looks nothing like this.
I think we should smell a rat from an eastern shore in all of this.
Sorry but is it a convincing counterfeit because it has to be a fake.
I suppose the data could have been corrupted when exchanged? Is that possible?
I would not expect to - this is NOT a Fibaro device.
Many manufacturers provide OEM versions, so I assume that’s what this is - it’s certainly not a Fibaro.
agreed but this link claims a fibrao device https://www.amazon.de/dp/B01KHWI0HK
and the manual is a fibro manual on the template
also product id and type are the fibaro product id and type
If it was OEM they made for someone else they surely would not give it their type and id
There is no such thing - each manufacturer can choose their own product IDs. Also, as I said, it is not uncommon for devices to be produced as OEM devices. The device itself does not use the Fibraro IDs.
I don’t understand what you mean - the device is not using the Fibaro ID.
It is using the product id and type fibaro use for their own version. If they were making for a third party surely they would give it a different product id and version if it had different characteristics as it clearly does.
So - the IDs are not owned by Fibaro. Any manufacturer can use these IDs as they please. The fact that it’s the same as Fibaro just supports that fact that it is the same device badged as a different manufacturer. This is rally not uncommon.
But it is not
<node>
<homeId>0xc1372986</homeId>
<nodeId>80</nodeId>
<version>4</version>
<manufacturer>0x10f</manufacturer>
<deviceId>0x1000</deviceId>
<deviceType>0x403</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<sleepDelay>1000</sleepDelay>
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_CRC_16_ENCAP</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_METER</commandClass>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL</commandClass>
<commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
<commandClass>COMMAND_CLASS_PROTECTION</commandClass>
<commandClass>COMMAND_CLASS_ALARM</commandClass>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<commandClass>COMMAND_CLASS_CENTRAL_SCENE</commandClass>
<commandClass>COMMAND_CLASS_MARK</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
is the true fibaro
as opposed this
<manufacturer>0x107</manufacturer>
<deviceId>0x1000</deviceId>
<deviceType>0x403</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<sleepDelay>1000</sleepDelay>
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
<commandClass>COMMAND_CLASS_CRC_16_ENCAP</commandClass>
<commandClass>COMMAND_CLASS_METER</commandClass>
<commandClass>COMMAND_CLASS_ALARM</commandClass>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map"/>
<endpoints class="concurrent-hash-map">but it was sold to this gentleman as a genuine fibaro not some other manufacturers product
Maybe - in any case that’s not really my concern. It’s clearly using different manufacturer IDs, and I think what’s important is to make it work. I don’t really think we need to worry too much about how OEM versions etc are badged - again, we see this with Aeon devices as well so it’s not too uncommon.
and aeon mark it as aeon or partner
are you sure you want it to work and support possible counterfeiting?
The Aeon devices are also sold under different manufacturers.
I am not trying to police this. I have no proof that this is a fake version and neither do you. I’m not going to stop the binding from working with specific devices. If you think it’s fake, then I suggest that you report this to the appropriate authorities. I believe (although not sure) that Amazon have such a system, but if not I’m sure there are more appropriate ways of reporting this than suggesting I don’t support it.