Hi @BiBo ,
yes, it’s very good, you should check janus too. I have used janus with wappler and it really works perfectly with wappler.
It is not fully clear to me which graphql integrations you see. As a query builder or as a server?
Maybe also post a separate feature requests per service with detail description why we should integrate it, so people can vote on it.
So post separate feature requests for MQTT and other services you mention.
@nevil had previously made a feature request for this. I even wrote that we can already send queries to graphql server as an answer . I think this feature request has been forgotten because it is outdated.
but I will request separate features for mqtt and time-series db.
I’m asking out of curiosity, does knex support any time-series db ?
@George
Not the usual suspects(ie influx).
Maybe timescale which is based on PG.
Nice try @Jaymer. Don’t be that guy. Before IoT we have NFT integration waiting 
Not comparing them! IoT really is more useful than GIF scams.
1 Like
As for GraphQL query builder using the API as solution has been shared before:
yess @George , I can even make xml requests 
we are now in the same place with you , there is so much and it is already usable . It remains only to collect them under a beautiful interface.
Example: I can now use xml requests with the wappler api, but I only had to create a simple xml-json convert for the response. Now it works very well with wappler. (small fixes still needed :))
So now Wappler is capable of solving big problems with small touches.
1 Like
I finally got around to replying to you as I didn’t have much time yet
I’m currently working on a project that uses directus as CMS. So I do use graphql to bring data from it to SC. I have some helpers in the form of custom extensions to ease the work. And yes I do agree a better integration with graphql from a UI perspective would be nice(and not niche). So I’m all for that.
IoT tech stack however is quite niche and wouldn’t bring a lot of value to the product so I see that as a problem to be tackled via extensibility of the platform. But I do see real value in IoT and making it work well with Wappler. And I’m all for adding the needed changes in Wappler extensibility to allow a great integration with IoT tech.
The potential of bringing 1000 IoT users, as jaymer suggests, is not a good reason to add something to the core of the product. Bringing 1000 users of any niche is actually a very bad idea because Wappler is not a product that focuses on niches. Because why stop at IoT?
Same as I was very vocal opposing Wappler adding to the core “Web3” technologies(specially NFTs) but this was even worse because blockchain tech has attached a toxic community that would eventually have it’s impact here.
Instead of adding niche features to the core I think it’s better to push for core features that will benefit the great majority of users and for the rest improve extensibility so anyone can build and integrate whatever they need without having to resort to workarounds.
2 Likes
hi @JonL ,
I hope you will successfully complete your project soon.
I’m so glad we agree on the graphql side. Yes, there seems to be a little more time for topics such as IoT, but it is necessary not to waste too much time because the transformation will be fast. Having Wappler at the beginning of this process will be a great advantage . In other words, many new users can gain the habit of wappler.
I just want to say for IoT let’s not be late…
2 Likes