Nodes, network and support — answered in detail.

No. A luminaire never moves during its service life, so its position is set once, at installation, and a GPS module adds nothing afterward — it cannot even help confirm a theft, since it loses power and RF range once removed. Installation itself is done by scanning the node and running a full functional test from the bucket truck, confirming everything works before the crew leaves, rather than relying on GPS-based auto-commissioning. Beyond that, GPS adds cost, an extra point of failure, continuous 24/7 power draw, and the time needed to acquire a fix on power-up. If you still want a GPS-equipped module, it's available as an option — just specify it when ordering.

Yes — it works with any manufacturer’s fixture, provided it has a 0-10V or DALI dimmable driver and an ANSI C136.41 or Zhaga Book 18 socket for RME twist-lock installation, or takes an RTM module mounted inside the fixture. Dimonoff has OEM agreements with most major fixture manufacturers. RME is also compatible with ANSI C136.41 5-pin and ANSI C136.10 3-pin receptacles, without light-level control.

No — each relay (node) includes everything in a single module.

Per Telcordia SR-332: at 25°C, MTBF is 4,953,260 hours (565 years), for a rated life of 175,200 hours (20 years) and a 3.98% probability of failure within that 20-year life. At 40°C, MTBF is 3,566,192 hours, the same 175,200-hour rated life, with a 5.83% failure probability over 20 years.

It is revenue-grade, accurate to ±0.5% and compliant with the ANSI C12.20 (C136.50) metering protocol, with every device individually calibrated in-plant during quality control. Voltage is auto-calibrated on the H4 generation, which also cuts false alarms.

Industry-standard 0-10V and DALI, both source and sink, with 1024 dimming steps for smooth ramping and 10 programmable levels with delayed timing and scheduling. Additional parameters cover minimum lamp burn time (to respect fixture warranties), minimum/maximum dimming percentage, a low-power demand-response mode, an option to turn off below the minimum dimming level, and a user-programmable transition time from 0% to 100% of up to 65,535 seconds.

Both options exist, to match your fixture. RTM’s small footprint fits inside the fixture enclosure, well suited to decorative styles. RME mounts externally via a NEMA C136.41 5- or 7-terminal twist-lock receptacle for power and dimming control, or can be installed in a NEMA 4X box and mounted remotely.

The external C136.41 module is fully compatible with the older C136.10 3-prong photocell socket, so installation is the same as replacing a damaged photocell. The node’s barcode is scanned at installation time to geolocate the fixture.

No, also the same thing: per IES TM-23-11, the device that physically monitors and controls luminaires at each control point, responds to inputs, makes control decisions through its own logic, and communicates over the network.

The nodes are rated 110 to 480 Vac nominal at 50 and 60 Hz, with a -13% / +6% operating tolerance, so one part number covers North American and international distribution voltages instead of a separate model per voltage. The node’s own consumption is under 1 W. Maximum switched load is 7 A at 120–240 Vac, 5 A at 277–347 Vac and 2 A at 480 Vac.

The RME fits 7-pin ANSI C136.41 and Zhaga Book 18 receptacles. It also fits standard 5-pin ANSI C136.41 and 3-pin ANSI C136.10 sockets, but those carry no dimming, so control there is limited to switching. It attaches with a twist-lock and needs no tools; physical installation takes about five minutes.

Every RME includes an integrated photocell, enabled in the default configuration, working immediately after installation with no network connection. A luminaire is never left dark waiting to be commissioned.

0–10 V or DALI, chosen per node. DALI follows IEC 62386 including SR and Dexal, with Part 252 for energy reporting and Part 253 for diagnostics and maintenance. The 0–10 V output drives source drivers up to 20 mA and sink drivers up to 5 mA. Levels are set in 1 % increments between a configurable minimum and maximum.

An RTM controls up to four drivers, and five or six may be possible depending on the load.

Lights come back on after a programmable delay rather than all at once, which eases the inrush on the grid at restoration. On the RTM the default level after a blackout is 64 % unless the node is programmed otherwise.

Yes. A demand-response load-shedding function is built into the node itself.

−40 °C to +70 °C (−40 °F to 158 °F) and up to 99 % relative humidity, non-condensing. The RME is rated IP66 for ingress and IK09 for impact. For an RTM fitted inside a luminaire, the integrator must verify the luminaire’s actual maximum internal temperature.

The RME includes 6 kV / 3 kA surge protection and complies with IEC 61000-4-3 and EN 61000-4-3 for immunity to radiated electromagnetic fields.

The RME is approved to ANSI/UL 773 and CSA 22.2 No. 182.2 under file E476540. The RTM is approved to ANSI/UL 8750 and CSA 22.2 No. 250.13-14 under file E481666. Both use UL 94V-0 flame-retardant material and are DLC and RoHS compliant.

They are designed for LED luminaires but are also compatible with high-pressure sodium, metal halide and mercury vapour.

Yes. Node firmware is updated over the air.

Every node contains an accelerometer measuring change of angle relative to the earth’s gravity, and a tilt-angle threshold can be set so the platform raises an alarm when a node moves beyond it.

The RME mounts externally on the luminaire’s receptacle. The RTM is a compact addressable module installed inside the luminaire with its antenna outside to reach the mesh, normally fitted by the luminaire manufacturer; it can alternatively go in a NEMA4 enclosure outside the luminaire or on the pole.

Generally no. Nodes are configured uniquely for each project, so a node moved to a different project will not join that network or communicate with the existing system.

Each RTM node can belong to 14 groups and 30 distinct scenarios. Any node fitted with a sensor can be configured as a master node controlling several others.

Wireless control needs an uninterrupted supply to the luminaires, so any existing control on the same circuit — a timer, relay, contactor or building-management photocell — must be bypassed by the contractor beforehand. Nodes must also be mounted vertically and perpendicular to the ground for reliable radio.

The RTM node is designed and manufactured entirely in Canada.

It depends on the radio technology chosen. Some nodes communicate directly with a cellular tower; others communicate through a local gateway. Node-to-gateway data logging and scheduling uses a Dimonoff protocol built on IEEE 802.15.4 (2.4 GHz or 900 MHz) and encrypted with 128- or 256-bit AES, above the standard. Gateway-to-server backhaul is Ethernet or cellular.

Yes — a gateway's pole can, for example, be struck by a vehicle. That's why the system has several fail-safe and fallback layers to stay operational while a crew repairs or replaces it, including the ability to transfer every node in an affected zone to a neighboring gateway within seconds, and back again once it's fixed.

Several options, depending on the radio network you prefer: mesh, Wi-SUN FAN 1.1 on the H4 nodes and the G4 gateway, LoRa or cellular. The mesh topology is a flooding approach, originally developed by DARPA for the US Army for high reliability — every radio receives and re-transmits each message until a time or hop-count limit is reached, rather than following one fixed, coordinator-assigned route the way Zigbee's routing does.

No, they’re the same thing: per IES TM-23-11, a device that interfaces between two communication networks using different protocols (for example BACnet to DALI), typically translating a wireless field-device protocol to a standard wide-area network protocol such as Wi-Fi, Ethernet or cellular LTE.

Every over-the-air transmission is encrypted (IEEE 802.15.4 secured mesh, 128- or 256-bit AES). Source and destination IP addresses are never sent unencrypted, and TCP/IP packets are never transmitted whole. Dimonoff’s own command-set protocol serializes every node individually, with additional security layered in as groups and scenarios are defined. On the Wi-SUN option, Wi-SUN FAN mandates AES-128 CCM at the link layer, combined with 802.1X/EAP-TLS certificate-based mutual authentication and periodic key rotation.

It depends on the radio network selected — for example, up to 1,000 nodes on Digi 2.4 GHz/900 MHz hardware. Dimonoff recommends an average ratio of 500 nodes per gateway for fast data collection and headroom for growth. The full 1,000 is reachable with a polling interval of one hour.

Digi XBee PRO at 2.4 GHz, Digi XBee PRO at 900 MHz, and Wi-SUN FAN 1.1 at 900 MHz — the H4 nodes and the G4 gateway all carry the Wi-SUN option. The RME also offers a Honeywell / Elster Energy Axis radio, and LTE-M for locations where a mesh is impractical.

Up to 300 metres (1,000 ft) between modules is the planning figure, and actual range varies considerably with the environment. A gateway should sit within 300 metres of, and in direct line of sight with, at least two nodes. Obstacles such as metal, walls or trees, or an elevation difference of more than 25 degrees, degrade the signal; repeaters can be added where a link will not close.

Devices communicate over a private radio network encrypted with AES-128, with AES-256 available on the Digi XBee option, and each node is uniquely serialised with an individual address. On the Wi-SUN option, Wi-SUN FAN mandates AES-128 CCM at the link layer combined with 802.1X/EAP-TLS certificate-based mutual authentication, with keys rotated periodically by the border router.

Ethernet or cellular. Ethernet needs a static IP reserved on your network, or DHCP with a reserved address. Cellular needs a nano-SIM for data only with at least 500 MB per month, which varies with node count, plus the access point name and provider. Dimonoff does not supply the SIM card or the data plan by default.

Yes. Each gateway autonomously manages its own group of nodes, so normal operation carries no dependency on a central server.

Each gateway has GPS for time based on its own location, plus a battery-backed real-time clock.

A NEMA4X (IP66) cabinet with stainless steel hinges and locking snap latches, suitable indoors or outdoors, supplied with pole and wall mounting hardware. The standard enclosure measures 10 × 8 × 6 in; with the battery back-up option it is 14.13 × 12.26 × 6.13 in.

A heater for cold climates, which draws 70 W while active below 0 °C and extends the range to −40 °C; a cellular modem at 7.5 W; and a LiFePO4 battery back-up giving one hour of autonomy with a ten-year life on maintenance charge. The gateway itself draws 2.5 W maximum and carries a 5 A fuse and 190 joule surge protection.

Yes. The H4 nodes and the G4 gateway all support Wi-SUN FAN 1.1, and Groupe Vectanor, Dimonoff’s parent company, joined the Wi-SUN Alliance as a Contributing Member in April 2026. The Alliance is a global non-profit industry association with over 300 member companies across 46 countries.

The gateway runs on 120 to 240 Vac at 50 and 60 Hz. Installations at 277 or 347 Vac need a stepdown transformer, either the STPDNXFMR-277 or the STPDNXFMR-347, which Dimonoff can supply.

Either. The Dimonoff | SCMS platform can run on the client’s own servers, on the cloud (client-managed or Dimonoff-managed), or as SaaS. The Central Management Server handles data acquisition synchronized with gateways, configuration, reporting, and serves the web and mobile access applications. In the hosted deployment, data centres are available in several regions, so a customer can choose the geographic location in which their data is kept.

Yes — the system uses industry-standard REST APIs for data exchange, and our team assists with any integration.

No — you can use Dimonoff’s desktop application or the web-based application, whichever suits your team.

Every node has a built-in demand-response load-shedding function with up to 10 priority levels.

Yes. Dimonoff | SCMS is vendor-agnostic and manages several lighting-control providers within one interface, including Dimonoff’s own system, Honeywell EnergyAxis (Netsense), Current by GE (Lightgrid), Telematics Wireless (T-Light) and the Pharos DMX system. A city that has already bought another vendor’s controllers does not have to replace them to consolidate on one platform.

Google Chrome, which is recommended, along with Microsoft Edge, Firefox, and Chrome for Android on a high-definition screen, each kept at its latest stable version. Smartphone browsers and iPads are not supported.

English, French and Spanish, chosen at sign-in and changeable afterwards from the Preferences menu.

Yes. Users sign in either with a username and password managed by the platform, or with their Microsoft Azure Active Directory account credentials.

Passwords must be at least eight characters with an uppercase letter, a lowercase letter and a special character, and the current password cannot be reused. Sessions log out automatically after 20 minutes of inactivity, with a warning beforehand. Repeated failed sign-in attempts lock the account temporarily.

Deployments are divided into business units, each representing a physical place such as a city, a municipality or a group of buildings, and an organisation can hold as many as its server capacity allows. Within a business unit, a zone is a closed geographic shape containing devices; each zone must include at least one gateway, and zones sit adjacent to one another rather than overlapping. Buildings and multi-level car parks can be added inside a zone with devices located per floor.

Yes. Each business unit can be given its own logo, header background colour and header text colour.

Devices are clustered into groups by drawing a shape on the map, and new devices falling inside that shape can be assigned automatically. Each group carries one standard schedule plus any number of non-conflicting event schedules. A scheduled command runs either at a fixed clock time or by astronomic time — dawn, sunrise, sunset or dusk — with a configurable offset in minutes either side. Schedules are managed in a calendar viewable by month, week, day or list, with the astronomic markers shown alongside each command.

Yes. An event schedule covers a date range with its own start and end, builds on top of the existing standard schedule, and is pushed to the affected nodes automatically at midnight, then rolled back to the standard calendar when the event ends. If a node cannot be reached the platform retries three times and notifies you.

Overload, over-voltage and under-voltage, low power factor, fault when on, fault when off, last gasp on power loss, power restoration, lamp burn time, driver burn time, lost module, tilt angle, CPU temperature, 0–10 V output deviation and power deviation. Which of these are available depends on the node generation and firmware version.

Users with an email address on their profile and alarm email enabled receive an hourly message listing new alarms at or above the criticality level set for their business unit. Alarm history can also be viewed as a heatmap over a chosen date and look-back period, filtered by all alarms, by network or by specific type.

Yes. Nominal voltage and tolerance, maximum lamp and module consumption, minimum power factor, maximum tilt angle, temperature limits, deadbands and transition delays are all set per node, and a tuned set can be copied to any other nodes selected on the map.

Eleven preconfigured energy log report types covering consumption in kWh or kVAh and lighting burn time, broken down by device, by zone, by hour, by day or by month, presented as either a table or a chart.

With the Dimonoff lighting control system, gateways poll nodes at a configurable frequency that is typically every 15 minutes. Aggregated reports are generated daily in 24-hour blocks from midnight to midnight using the previous day’s data.

Gaps shorter than 24 hours are interpolated between the surrounding readings. For longer outages the platform estimates consumption from the configured lamp wattage, the dim levels and the sunrise and sunset times at the device’s own position. Either way the affected values are flagged as interpolated rather than presented as measured.

Yes. Reports can be scheduled daily, weekly or monthly and emailed to selected users or exported to the server, in PDF, CSV, XLS or XLSX, with a configurable file-name prefix.

Yes. User-defined queries filter on criteria including device name, serial number, GPS coordinates, network type, alarm type, install date, last communication, last alarm, last status, connectivity, street lamp identifier, zone, group and node parameters. A query can be kept private, shared for execution only, or shared with editing rights, and pinned to the dashboard as its own panel.

Yes. A query can raise notifications at intervals from 15 minutes to one week, be targeted at particular roles, carry a cooldown period so it does not repeat immediately, and escalate to other users if the first recipient has not acknowledged it.

Access runs on roles that grant Execute, Read, Delete and Modify or Add rights per functional area, with no limit on how many roles exist; Administrator and Installer are built in and cannot be deleted. Beyond roles, individual users can be restricted to particular functional layers, groups or zones. An account can also be limited to a start and end date, to specific days of the week, to a daily time window, and capped so that one action can only affect a set number of devices.

Yes. Alongside connected devices the platform tracks unconnected inventory such as poles, benches, trash cans, manholes and municipal buildings, counted separately from smart devices. Devices and assets are organised into functional layers grouping things that play a similar role — gateways, street lighting, pathways, snow sensors, generic 0–10 V sensors, inventory items — with no limit on how many layers exist.

Yes. A lasso tool draws one or several polygons on the map and then acts on every device inside them — retrieving metering or firmware versions, switching devices on or off, enabling, disabling or clearing alarms, or raising a maintenance ticket. Node parameters, alarm thresholds, group memberships and scenarios can be copied across many nodes the same way, provided the targets sit in the same functional layer.

An optional maintenance module raises maintenance tickets against selected devices, flags ticketed devices on the map, and tracks preventive-maintenance task statuses and dates per device.

Changes made in the software are pushed over the air through a flash operation that lists every pending change and the nodes and gateways it affects, shows each device’s connectivity, reports success or failure per device and offers a retry.

Yes. From version 21 the platform keeps time-series data in a dedicated TimescaleDB and PostgreSQL database that can be exposed read-only, so a city can build its own reports in a tool such as Microsoft Power BI. A read-only account is installed by default with every installation.

Energy consumption polling logs, daily per-device and per-zone consumption reports, alarm logs, sensor logs and user event logs, together with context tables for devices, zones and sensors that refresh every 30 minutes.

Yes, both for adding connected objects and for publishing data out to an MQTT server.

Yes. The City of Laval’s deployment interfaces with Oracle E-Business Suite Enterprise Asset Management, Intelight MAXVIEW 2.0 traffic management, and ArcGIS Esri.

0–10 V and UART sensors wire directly to the nodes, including temperature, humidity and snow-level sensors, each carrying up to four configurable alarm thresholds. The RME provides a multifunction input and output that is either a 0–30 V analog input or a 24 Vdc digital output, with a 24 Vdc sensor supply up to 50 mA. The RTM provides five inputs and two outputs for accessories such as a photocell, motion detector, switch or lux meter.

In the hosted deployment the platform runs with data centres available in multiple regions, so a customer can choose the geographic location in which their data is kept. The platform can alternatively be installed on the customer’s own server.

An activity log records every action taken within each business unit, filterable by user, item type, action type, required follow-up and date range, and exportable.

Yes — real-time access to a recently deployed large-scale project can be arranged, along with interviews with the managers running it.

Yes, tailored to your team, onsite or remote, with refresher sessions available by webinar.

A North America-based team, in English, French and Spanish, with ticket management built into Dimonoff | SCMS. Response targets during support hours (Eastern Time): under 30 minutes for urgent tickets, under 4 hours for important tickets, and within 24 hours for the rest.

Yes — send us your fixture count, kW/kWh figures and the components of your electricity rate (customer, distribution, transmission, admin and market-service charges, taxes), and we’ll run a complete ROI analysis.

Yes.

Yes — see the Software and Firmware License & Warranty section of the Terms and Conditions page. On the hardware side, the nodes carry a five-year limited warranty extendable to ten years, and the G4 gateway a three-year limited warranty, also extendable to ten.

Since April 2026 Dimonoff is one of four divisions of Groupe Vectanor. Dimonoff leads smart lighting control and connected urban infrastructure; Amotus handles turnkey IoT product development and the Fundamentum platform-as-a-service; Spatium covers smart parking and mobility management; and Vigilia works in security and intelligent monitoring using AI-powered sound recognition to detect and geolocate critical events in real time. The group provides shared technology governance while each division grows within its own market.

The company has been designing and deploying large-scale IoT solutions across Québec, North America and internationally since 2006.

The City of Laval selected Dimonoff and Pierre Brossard Ltée, a subsidiary of Black & McDonald, to convert 37,000 light fixtures to LED with smart controls between 2021 and 2024. The deployment comprises 37,000 intelligent lighting controllers, 88 gateways using a mix of cellular and the city’s own IT network, and one central Dimonoff | SCMS in its hosted version.

The Laval conversion was announced as delivering annual electricity savings of 15 million kWh and an estimated annual greenhouse gas reduction of 10,607 tCO2, calculated according to EPA standards, over a 25-year fixture life span.

In a pilot with Hilo, a subsidiary of Hydro-Québec, the City of Varennes reduced the brightness of nearly 900 streetlights by 50 %, dropping further to 25 % during Hilo challenge windows in the morning between 6 a.m. and sunrise and in the evening between sunset and 9 p.m. Varennes became the first city to take part in the Hilo challenges. The pilot uses RME nodes and the platform’s event-based planning.

Publicly announced deployments include Montréal with more than 132,500 fixtures, the Fédération québécoise des municipalités collective project covering 145,000 streetlights, Laval with 37,000, and Grand Rapids, Michigan with 18,037 nodes. Mississauga and Pittsburgh are also named as group deployments.

Yes. Dimonoff’s smart lighting solutions, including Dimonoff | SCMS, are available through Sourcewell cooperative purchasing contract #041525-DIMN, valid through July 2029.

Groupe Vectanor has completed a SOC 2 Type II audit covering security, availability and data integrity. SOC 2 Type II is an attestation report rather than a certification.

Awards listed in company announcements include Prix performance Québec in 2020, finalist at Les Mercuriades in 2019, the Smart City Industry Awards in 2018, Smart Cities 50 for the Montréal intelligent street lighting project in 2018, the LSNetwork Award in 2018, the Fidéides Award in 2017, and finalist for two Sapphire Awards in 2015.