FAQ

Octopus

If you have a question that is not asked and answered on these pages, please contact us at support@wattics.com

Does the GND lines of the Octopus server and IO extension units need to be connected if both units are used for pulse counts?

If the Octopus Gateway and the I/O Extension unit are on the same CANBus then they already share the GND, so you just need to connect it on one of the units.

Does the Octopus accept all types of sim cards (normal, mini, nano)?

The Octopus Gateway only accepts the Standard SIM Card type.

How many parameters can be stored in the Octopus?

The Octopus Gateway has a 150000 circular log and each parameter measurement corresponds to 1 log.

How to check if my Octopus Gateway successfully transmits data to Wattics

You can use the CDT.exe tool to verify the status of the Octopus’ data push to Wattics. The CDT.exe tool is located in the same directory as the WatticsTool.exe:

 
Launch the CDT.exe Software Tool, tick ‘Serial Number’, enter your Octopus serial number (e.g. 230001AB) and click Connect.
 


 
Once connected, click on the System Messages tab, and checks the logs:

  • LAN connection: if you see a message starting with [ETH] showing up every 30 seconds, then it means that the connection to the Wattics platform fails and the Octopus tries to reconnect. If no message pops up within a minute then the connection is established.
  •  

  • GPRS connection: if you see messages with ATModem::Connect (ConnectionID: 0) and DISCONNECT: 0 | RX: 0 | TX 0 | LN: 227 showing up alternatively every 30 seconds, then it means that the connection fails due to the PIN code of the sim being active or to the use of wrong APN credentials. Logs showing new connections may also appear should the network signal strength be low. A successful connection will only show updates on network signal strength with no disconnection or reset logs.

 

Troubleshooting

1. If using a LAN connection, make sure that the IT team has configured their firewall to allow TCP communication from the Octopus to octopus.wattics.com (52.50.202.103) on port 4401. You can also double check that you have correctly set up the Wattics URL where data collected will be sent to. Navigate to Output>Services from the top menu, and do the following:

  • Enable Service 1
  • Set Wattics as Service Name
  • Enter octopus.wattics.com as Service Host Address (IMPORTANT: When using GPRS Sim cards or when your firewall does not support the use of URLs, you must enter 52.50.202.103 as Service Host Address.)
  • Set 4401 as Port
  • Click OK.

 

 
2. When using GPRS Sim cards or when your firewall does not support the use of URLs, you must enter 52.50.202.103 as Service Host Address in your Octopus project file. To check this, run the Wattics Tool and open your project, then go to Output>Services. Change octopus.wattics.com with 52.50.202.103, save and redeploy your project. Double check your APN credentials, and disable your sim card’s 4-digit PIN code using any unlocked mobile phone.

 

​​3. To check if data is being received on Wattics’ end, you must go to the Breakdown tab in your Dashboard, click on your data point and check the control panel on the right hand side. If Jan 1970 is shown then it means that no data has been received yet (please wait for at least 10-15mn). The panel will otherwise update to today’s date when data starts being collected, and you will be able to select that day and check the first data points coming in.


 

You can also check the last data packet received in the meter status available in the Attributes tab, that you can access by hovering over your name in the top right corner. Invalid Date means that no data has been received yet.

 

Please contact us at support@wattics.com if you have any question regarding this verification process.

How to insert my sim card into the Octopus GPRS Gateway

First of all, you must ensure that you use a standard sim card, with the 4-digit PIN code disabled (that can be done with any unlocked mobile phone). Other sim card types are not supported.


 

The sim card must be inserted as follows.

 

When you push the sim in, it should stop itself with 5mm of the sim card remaining outside of the Octopus, allowing you to remove it easily. There is no release mechanism, just push and remove.

 

You may contact us at support@wattics.com for any clarification.
 

How to wire different types of pulses?

The Octopus and I/O Extension units can accept 4 types of pulses, please refer to the correct wiring diagram depending on your metering setup.

 

Dry Contact Pulses

 


 

Dry Contacts (with no power source):

1. Power the Octopus off
2. Connect the Octopus V+ line to the meter’s input line
3. Connect the meter’s pulse output line to the Octopus digital input line
3. Power up the Octopus

Dry Contacts (already with power supply on common):
The first check is to ensure that the 3rd party controller’s power supply is DC and does not exceed the maximum voltage of 24VDC. Once this is confirmed, follow the steps below:

1. Power Octopus and controller off
2. Connect the GND from Octopus Power Supply to the GND of the 3rd party controller’s power supply
3. Connect pulse output(s) from the 3rd party’s controller to Octopus digital inputs
4. Power up both units

The problem with not having a common GND is that the voltage at the 3rd party controller’s input can be higher than 24VDC.

 

Diode Pulses

Same connection as the dry contact pulses but with polarity. That means the 24VDC and the pulse unit need to be connected to the right terminal input/output of the pulse meter.

 

Transistor (PNP/NPN) Pulses

 


 

Pulses types need to be verified before the installation to avoid any problems.

Pulses are not counted by the Octopus, what should I do?

Should pulses not be counted by the Octopus devices, you can follow the following steps to troubleshoot the issue:

1 – Use a multimeter to verify that:

  • Pulses are generated by the pulse-emitting device and visible at the multimeter. No pulses means an issue with the pulse-emitting device and not with the Octopus.
  • The output voltage line of the pulse-emitting device goes back to near 0V between pulses. Any base voltage over 1V can possibly mean that the 0-24V transitions are not captured by the Octopus, requiring remote assistance to update the pulse threshold on the Octopus.

2 – Short the V+ terminal outputs of the Octopus devices with any of its terminal inputs to simulate pulses and check if these are counted by the Octopus. If they are not counted then it means that there is a misconfiguration with your Octopus software project, please check you have used the correct driver and the correct input number.


API

If you have a question that is not asked and answered on these pages, please contact us at support@wattics.com

Where can I find the API documentation

How can I upload data via the Wattics REST API

This page contains the JSON format specifications as well as the rules that your software must follow when pushing data to Wattics (e.g. units, timestamp format, authentication etc). Please make sure to read everything carefully first to ensure we get it right the first time. Any clarification needed by your software team, please email us at support@wattics.com.

What do I need to start developing my API client

You must first read our API documentation:

How can I upload data via the Wattics REST API

Then you need to request an API Startup Package at support@wattics.com providing information about yourproject. Our team will send you:

  • HTTPs credentials (username and password)
  • Unique Data Stream IDs to use for three test data points (electricity, gas and environmental data)
  • Dashboard demo account in our dev environment (to verify that data is coming in nicely when you push it)

 

How to test if my software client is working

You must log in to your Wattics Dashboard using the credentials received as part of your API Startup Package. After log in you will find the three data points in your menu tree under the Breakdown tab.

To check if data is being received on Wattics’ end, you must go to the Breakdown tab, click on your data point and check the control panel on the right hand side. If Jan 1970 is shown then it means that no data has been received yet (please wait for at least two time intervals). The panel will otherwise update to today’s date, and you will be able to select that day and check the first data points coming in.

You can also check the last data packet received in the meter status available in the Attributes tab, that you can access by hovering over your name in the top right corner. Invalid Date means that no data has been received yet.

 
In case you want to validate your JSON format, you can use third party REST plugins for Firefox and Chrome which are great to push data and check if any error is returned. Sometimes you can spot a missing parenthesis or an error code indicating an incorrect password. You can also use GET calls on our API to check the last data packet received and stored on Wattics’ end to confirm that packets have been received. ​​​You just need to a standard HTTP GET request creating the URL in the following way (you will need to remove ‘dev-‘ from the url when pushing data to our production environment):

https://dev-web-collector.wattics.com/measurements/v2/unifiedjson/?stream=

Finally, when debugging, please remember to also check the timestamps and values shown in our dashboard, as these could reveal incorrect time and unit settings on your end. Once all is verified we can experiment pushing a batch of historical data and confirm that testing is done before moving to the production environment.

What is the API URL to use for testing my software client

https://dev-web-collector.wattics.com/measurements/v2/unifiedjson/

What is the Dashboard URL to use for testing my software client

https://dev-dashboard.wattics.com/

How often should my software client post data to the API

​The data push frequency can be adapted to your application requirements, as this frequency will define the granularity of the readings shown in the dashboard (e.g. if you push every 5 minutes you will have a 5-minute minimum granularity in the graphs).

It is important that you let us know what your data push frequency is at the start or whenever you decide to change it. This indeed allows us to configure our platform to detect broken communication when no data is coming in and issue real-time notifications.

If your software client does not push at regular intervals, you must choose the highest time period acceptable after which data communication can be considered as broken. All packets received during that time interval will be aggregated by our API and shown aggregated in your graphs.

Can I push Power Factor and Harmonics measurements

Not at the moment, but these may be supported in the next version of our API. Please register your interest with so we can update you when these are available.

What is the correct timestamp format?

Our API expects the standard ISO8601 yyyy-mm-ddThh:mm:ss.sss+|-hh:mm where “yyyy-mm-ddThh:mm:ss.sss” represents the local time and “+|-hh:mm” is the OFFSET to apply in order to obtain the UTC timestamp​. You can find more information here: “https://www.w3.org/TR/NOTE-datetime”.

For example, 1994-11-05T08:15:30-05:00 corresponds to November 5, 1994, 8:15:30 am, US Eastern Standard Time.

What should I do when per phase readings are not available

If your meter or data system does not record individual readings per phase, you must use the _1 entries and omit the _2 and _3 entries. For example, you must push your total kWh to the pC_1 parameter.