Topics as Undefined

[znelbok]

I have had this running for a while but never sat down with it to look at it until now.

All topics are being published as cbus/read/undefined/undefined/undefined/level

What is causing this?

Running on a RPi, Clipsal C-Gate Version: v2.11.1 (build 3240).

CGate is operating fine on the network.

Settings.js has the correct project and is publishing to the external MQTT server

[dougrathbone]

@znelbok I am seeing this as well. After looking into it, my version of C-Gate is publishing messages that follow a different format:
254/17/28

The current code is splitting on the / and looking for objects further in the array. By updating this parse line I am able to get it to publish this correctly.

I plan to fork this project and extract out the parsing so as to enable folks like us to adjust it as needed.

Does anyone know if this is due to the format C-Gate publishes over telnet being different to more recent versions? @the1laz

[dougrathbone]

I think i appear to have found the issue. As of C-Gate version 1.5 the device addressing format has changed
https://updates.clipsal.com/ClipsalOnline/Files/Brochures/W0000360.pdf (page 7)

support the use of C-Bus applications and apply URIcompatible addressing. While the 1.0-compatible addressing can
still be used, new applications communicating with C-Gate should
move to this addressing system as soon as possible. ```

Will send a pull request addressing the above.

[the1laz]

Sorry, not getting much time for this at the moment. If you send a pull request I should be able to merge it pretty soon though.

[dougrathbone]

Are you able to test my version against your installation?

https://github.com/dougrathbone/cgateweb/tree/71c2ed5897da71a98edcc122a24523dfe6095684

I also have a further version where i've fixed ramp commands for MQTT Cover you can take a look at here:
dougrathbone@da2f6c0