• Announcements

    • GeorgiTsatsev

      Some Agents Stopped Working   10/30/17

      Dear Domotz Users,    
       
      Symptom
      Please be aware that we are currently experiencing a problem on some Domotz Agents that marks them offline and makes them unreachable. This is primarily affecting the users outside of the US/North American countries.  Domotz is actively working on the resolution of this issue to minimize the impact to you and your customers.
       
      Agents Affected
      QNAP
      Synology
      Raspberry Pi
      Virtual Machine - Debian
      Domotz Boxes   Agents that were affected were running older versions of the Domotz Package (older than 2.1.4).   Agents that had the latest package should not be affected by this issue (2.1.4 or higher).   Root Cause
      Domotz is constantly updating the agent software to improve features and ensure device and network security.   In this instance, Domotz was doing a routine agent upgrade and Agents that had older versions of the package running on the hardware ended up in an offline state.  
       
       
      Resolution
      Domotz is actively working to bring back Domotz Boxes.  We have been able to recover a majority of the Domotz Boxes that had this issue through the Provisioning channel (a parallell channel to the software, mainly used for maintenance and provisioning).   For QNAP, Synology, Raspberry Pi and VM installations, it may be necessary for you to reinstall the latest Domotz software.  
      You can find instructions for updating to the latest version for the Raspberry Pi and VM version might be found on the Domotz Portal (https://portal.domotz.com --> Domotz Software --> Install Instruction for Raspberry Pi and Debian).   The new package (2.1.4) has been published on the QNAP store (available for x86-64 models and ARM x41 models (x31+, x31P, x31P2, x31X, X35) with QTS 4.3.0 and above), and on the Synology store.   We sincerely apologize for any inconvenience caused by this outage. We appreciate the fact that this affects your operations and will do our best to minimize the impact.    Regards,
      The Domotz Support Team
admin-St-Andre

SNMP Gude Sensor Box

6 posts in this topic

Hello,

I have a Expert Sensor Box 7211-0 from Gude.

I can not display the information of my probe thanks to the functionality "Eyes"
According to the MIB file provided by Gude, the OID is: .1.3.6.1.4.1.28507.31.1.6.1.1.2. Unfortunately nothing is displayed.
The interface tab is enabled, demonstrating that the SNMP is enabled.

What can I do ?
Thank you

 

Bonjour,

je possède un SensorBox Temperature 7211-0 de chez Gude.

je n'arrive pas à afficher les informations de ma sonde grâce à la fonctionnalité "Eyes"
D'après le fichier MIB fourni par Gude, l'OID est : .1.3.6.1.4.1.28507.31.1.6.1.1.2 . Malheureusement rien ne s'affiché.
L’onglet interface est bien activé, ce qui démontre que le SNMP est bien activé.

Que puis-je faire ?
Merci

GUDEADS-ENC7212-MIB.txt

0

Share this post


Link to post
Share on other sites

Have you tried by removing the dot at the beginning?

If no success I would recommend to send an email to our support by indicating the name of the agent that is affected.

Thanks

0

Share this post


Link to post
Share on other sites

Hello,

To understand if the issue is either specific to that OID or related to the SNMP information gathering, you could:

1. go to the device details view, (the one where you can choose the room as well)

2. look above the "First Seen" row, searching for the "SNMP Name".

3. If "SNMP Name" is displaying a reasonable string, the problem is specific to Gude OID otherwise something else is happening at SNMP level.

 

0

Share this post


Link to post
Share on other sites

Hello,
There is no dot at the beginning.

Here is a screenshot.
I will send a message to domotz support.
Thank you

Capture d’écran 2017-04-10 à 19.56.50.png

Capture d’écran 2017-04-10 à 19.57.45.png

0

Share this post


Link to post
Share on other sites

By looking at the MIB usually used by Gude (but other manufacturer as well use a similar approach), the "single item" you need to GET, need to be specified with the index number (e.g. 1, 2, 3, etc).

In your specific case, the OID which can be retrieved by Domotz as a single value (not a walk into the OID tree) should be the following:

1.3.6.1.4.1.28507.31.1.6.1.1.2.1 (please notice the last index id at the end of the one you originally used)

By using this OID you should get the value you are looking for.

In general, I would recommend a MIB browser which is able to perform single SNMPGET from the device you need to monitor, to find out the exact OID. I personally use MIB Browser iReader (http://ireasoning.com/mibbrowser.shtml – free version).

Of course, we will simplify this part, and add a similar tool to check the exact OID directly in Domotz, allowing a simpler way of configuring/discover OID which need to be configured. It just a matter of putting the requirements together and develop these further improvements.

2

Share this post


Link to post
Share on other sites

The support domotz is very good and very fast.
They solved my problem.
I forgot a ".1" in the OID

Thank you

2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now