rpcai

Results 10 comments of rpcai

I believe this is a bug that should be fixed, however my workaround was : - Generate attribute message via script - Save server attributes ![image](https://github.com/thingsboard/thingsboard/assets/168617729/e245d69e-fc4d-40ab-842e-a50ab44f226f) JS: ``` if (!msg.attributes)...

### I have replicated the issue in another environment Debian 11 / Docker, dockerfile below: ``` version: '3.7' services: mytb: restart: always image: "thingsboard/tb-postgres" ports: - "8080:9090" - "1883:1883" -...

I have a very simmilar use case (desire to show time-series chart for devices/entity aliases which have distinct keys). Features that would satisfy (as I see it) included: -Extending Entity...

I agree that the Dashboard States feature feels very limited, when developing complex, dynamic solutions. I would like to see the "Dashboard states" feature get some attention - including making...

I have struggled with this as well! In my opinion, Thingsboard is soemwhat inflexible regarding its MQTT Telemetry/Attributes API messaging implementation. It feels as thought it has been developed under...

I can work around the serviceID missing as follows: But then I get nothing posted to the MQTT topic I expect (v1/devices/me/rpc/response/+) ![image](https://github.com/user-attachments/assets/cc8136fd-11f0-4e58-8b77-03c55515a6e2) ![image](https://github.com/user-attachments/assets/00f2160c-01ae-43be-8a9b-15227f555363)

@JanCools750 - The MQTT platform integration only functions as a client, if I'm not mistaken? - I had explored this in the past, but gave up, as most end-devices/gateways expect...

Supporting this as a feature - this limitation is infuriating when attempting to re-use a dashboard states developed for different cutomers