search

greiginsydney / Homebridge-cbus-installer

An install script that automates the process
GNU General Public License v3.0
8 stars 4 forks source link

Source unit not found #17

Closed woodgieboodgie closed 3 years ago

woodgieboodgie commented 3 years ago

cbus:platform event source unit //PETEQLD/254/p/3 not found.

Appears repeatedly in the logs every 70 mins. How can I resolve?

JasonY00 commented 3 years ago

This indicates that you have a physical cbus device defined in your network at Group Address 3 that is not showing up!

Thats what the "p" is in the address. Its in Project PETEQLD, network 254, group address 3. Check this with Toolkit in the database and network sections and you should see what is supposed to be there...

Cheers

Jason

woodgieboodgie commented 3 years ago

Thanks Jason for your prompt response. I open Toolkit, go into PETEQLD, network 254 and can see group 3 under 'Lighting'. Nothing else there tho. Can you give me some additional direction pls?

JasonY00 commented 3 years ago

Its not a lighting group address, its the address of a physical c-bus unit on your network, eg. a dimmer, relay, light switch, temperature sensor, PIR etc. When you open Toolkit, look under "Units" on the tree on the left hand side. It will then appear in the Database, Network or hopefully Both windows on the right. That's where the problem is, whatever that unit is, its defined somewhere and cant be found.

woodgieboodgie commented 3 years ago

Good directions. Found what it is.. the CNI5500 which we installed to be able to talk to CBUS.

cbus cni error

Can you recommend what the entry should be?

JasonY00 commented 3 years ago

It is not defined in the c-bus database only on the c-bus network? Make sure it is in both by importing it from the network. (do the same for the switch above). Once you add this CNI you will have to copy your database info over to your Pi Installation.

Homebridge is wondering what this magical device is as it has no idea.

That may give you something to go on...

woodgieboodgie commented 3 years ago

Interestingly none of the items in the list exist in the database. Can I safely import them all?

And once done, you mention that the db info needs to be copied across? i already have complete control using Greigs plugin... but will need to reinstall to capture the CNI and stop the error in Homebridge?

JasonY00 commented 3 years ago

Generally, once CBus devices are connected to the network, they are then imported to the database (by you). You then define all of your lighting GA's etc. and the database provides all of the user friendly labelling for you. eg. "lounge light", etc. You can also then watch the log, and do other programming tasks such as scenes etc. Do you not have any of this defined already with the //PETEQLD project on the PC that has toolkit installed?

At some point if you followed Grieg's setup, you would have also had to copy over your C:\Clipsal\C-Gate2\tag\PETEQLD.xml project file to the pi for the homebridge-cgate plugin to "find" all of your c-bus accessories which are then imported into your config.json file in homebridge. Within the XML file is the definition of the CNI at Network Address 003 along with all of the other c-bus devices and all of the lighting and other c-bus application group addresses etc.

JasonY00 commented 3 years ago

You won't need to do a full reinstall of homebridge, you will just need to recopy the XML file as per step 12 in Griegs installer. A note, that every time you change something on your network with Toolkit, you will need to redo this step and either import the newly defined groups or manually edit your config.json file under the c-bus platform on homebridge.

woodgieboodgie commented 3 years ago

so no risk as the DB is on the pc? client install is remote so cant afford to bring it offline

woodgieboodgie commented 3 years ago

I imported the xml and they all had Group numbers which were then reverse engineered and labelled accordingly in config.json. If I understand you correctly, importing them all into the DB and then repeating the step 12 and beyond will remove the erro as the CNI will be listed but Greigs script will change the IDs/labels?

JasonY00 commented 3 years ago

So, is this a live installation at a clients house and not your own? In that case, is it really a problem worth worrying about? Generally, it's not an error that is impacting the performance of homebridge, it's just saying every now and then when the network syncs that the CNI said it was on the network, but homebridge didn't know about it. I would probably just leave it alone...

woodgieboodgie commented 3 years ago

Done, its being left alone. Thanks for your help and insight

JasonY00 commented 3 years ago

No problem. I think the cause is obvious, but in this case, the solution is not worth the trouble...