Zigate Plugin - picking up unknown transmissions?

[ForzaAlfa]

Quick question to the plugin guys!

I have the zigate hooked to a different system (Zigate plugin for OpenLuup), and i just installed Domoticz solely for the purpose of using this seemingly outstanding zigate plugin.

My Zigate is local to the machine, but used through ser2net. Its currently providing the Zigate to both Domo and Openluup (allowed mutiple connections in ser2net). Currently see deliveries form my sensors coming in as "Unknown" in the domo plugin.

I'd like to be able to test how the plugin works more extensively, but don't want to burn the bridges to Openluup unless it works.

Is there any way to make the domo plugin pick up the devices already in the network? That would mean picking up the "Unknown" devices I see coming in..

If i could test it first, the plan is to use a Domoticz bridge into Openluup where I have all my automation. This way I can make use of some other good Domo plugins that OpenLuup doesnt have too.

[pipiche]

For now, the discovery of devices if made only when pairing the device into the Network.

I never investigate to discover existing devices as :

- It will be hard (even not possible) to discover a battery device which do not listen to the Zigbee controller and so cannot be query
- the use case seems very limited

[ForzaAlfa]

You're probably right.. But the battery device issue - all the devices i tested will send a command when I push its button, or trip the sensor?

I thought that might be enough info to create a device instance?

I also see that the plugin lists the devices i have connected to the Zigate USB, no way to work from that?

Only other use-case I see is if the plugin goes crashing down, and backup doesn't work.. then you wouldn't have to reinclude the devices manually, just name them again when they report?

If i were to reset the sensor, they will mabye report in with a different ID the next time, thus F**ing up the existing system - right?

[pipiche]

As the zigate plugin the short address will change and we do not care as we manage devices by there IEEE ( MAC address) so I would indeed put the zigate in pairing mode and do a device reset.

It is up to your other application to understand how it handles. In the other side I do not understand your setup as you must have only one controller in a zigbee network .


Envoyé de mon iPhone en utilisant Tapatalk

[ForzaAlfa]

I'm running OpenLuup (Open Source development from the Vera controller community) and it has a Zigate plugin that stopped being maintained 3 years ago.. It works for simple functions, but doesn't match yours by a mile..
This and the Domo plugin now shares the Zigate USB, so there is only one controller..

Guess I'll go the path of reincluding the units to this plugin then, and use Domoticz bridge into openluup..

Any chance you would free the plugin from domoticz? Having its own GUI, mabye it could be more stand alone - say with a node-red interface?

In any case - thanks for the quick response!

[ForzaAlfa]

@pipiche: Now i'm playing with the thought of making an OpenLuup plugin for your plugin.. (if you don't mind!)

The interface I see in Domoticz looks similar to OpenLuup visually, so if all the plugin needs in terms of interface is the setup parameters and the device list sync, then it should be doable?

Not knowing the Domoticz Python framework well, what does your plugin need Domoticz for?

I can also provide an init routine, but if theres much more code-sharing with the domoticz framework, its harder..