# Kbus api module unsupported

**URL:** <https://www.wago.community/t/kbus-api-module-unsupported/212>\
**Category:** Node-RED\
**Tags:** mqtt\
**Created:** [August 10, 2022, 5:59pm UTC](https://www.wago.community/t/kbus-api-module-unsupported/212 "2022-08-10T17:59:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Rene](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/rene/32/396_2.png) [@Rene](https://www.wago.community/u/Rene)\
**Post date:** [October 19, 2023, 10:47am UTC](https://www.wago.community/t/kbus-api-module-unsupported/212/2 "2023-10-19T10:47:00Z")

</div>

We had the same problem; check this post:

> [@Using SSI module for absolute encoder in NR](https://www.wago.community/t/using-ssi-module-for-absolute-encoder-in-nr/512):
>
> We are setting up a test setup to get acquainted with the 750-8213 running NR and MQTT. We have most of the DI, DO, AO, AI modules working over the Kbus API by Jesse James Cox. Now we want to use the 750-492 SSI module in combination with a digital absolute rotary encoder. It seems this is not (yet) supported in the Kbus API. Any ideas on how to build a workaround? Thx!

We went for the MODbus api solution and have things up&running; we use among other modules:  
750-492  
750-502  
750-630  
We got thes working over MODbus to MQTT; did not do any benchmark testing/stress testing; still in setup phase.  
We had some trouble getting readable values from the -630 SSI module; we can elaborate on that if anyone is interested!

---

_[View the full topic](https://www.wago.community/t/kbus-api-module-unsupported/212)._
