Hi all,
I see that there has just been an update to the detection of the Carel pCo controllers, which has added a lot of new sensor definitions for many people I expect (a good thing would have been an awful lot of work for someone which is appreciated of course!).
Unfortunately, as the pCo is a programmable unit (and we are an OEM/unit programmer for Carel) we use the units for a large number of custom applications across a number of our facilities and customers. Previously we weren't getting any sensor-specific information via Observium for these units (just network, CPU, ram etc.) which is OK as we use other BMS systems to get the environmental data.
Since the last update, we are getting a load of sensors but unfortunately (since our units are programmed by us) they are now showing alarms across most of the output, for example:
The values being polled are also non-sensical because whatever the OIDs which are being used are either not aligned to anything we use or just totally irrelevant values.
Humidity example below (obviously it's not 3,4 and 16 %):
Interestingly, we do also have some 'official' Carel chiller controllers (running genuine Airedale control pCO units, not our own) - and these are also showing crazy values as chillers (no matter where you get them from) do not have 'Delivery Air Temperature' or 'Humidification Proportional Bands' as they don't' deal with air directly - for example:
So it appears the detection logic is not just limited to incorrectly identifying our own custom controllers but also those of other manufacturers like Airedale, who also use Carel OEM pCO hardware like us.
With all this in mind, can I ask what is the best way to prevent these devices from being detected as " Carel pCOWeb (Chiller Unit) ". So that they go back to being simple pCOWeb units with basic stats like Ethernet and CPU?
Example device data is:
So like I said at the start, I fully appreciate there was a lot of effort by someone to get all these sensors setup and that's great for people using the software they were configured to detect. I just need to 'not' detect our units as being the same really.
Input welcome :)
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
