Derek Adams

The current approach for raw socket communication does not support sending commands to the device via SiteWhere command destinations. The basic flow is that the device connects via socket, after...

I'm not sure exactly what you're asking. The SiteWhere admin UI front end uses the published JavaScript API to connect to the system. The basic process is to get a...

Yes, the default topic naming convention uses the tenant token to differentiate the data. This allows the same configuration to be portable across multiple tenants. You can update the event...

Each tenant has a list of event sources that may be used to send data into the system for that tenant. By default, tenants are configured with an event source...

We support the concept of `Areas` which can be used to associate multiple devices to a physical area. Events are indexed by area as well, so it's possible to track...

Thanks for reporting the issue. We added a Jira ticket to make sure it is addressed in the 1.10.0 release: https://sitewhere.atlassian.net/browse/SITEWHERE-368 As you mentioned, this is due to the updates...

It may make sense to use an existing library such as: https://pkg.go.dev/github.com/eapache/[email protected]/batcher#section-readme to handle batching and have it call `WriteMessages` as a side-effect.

Thanks for reporting the issue! We will have this fixed in the next release.

As Jorge mentioned, the exception is probably due to a problem with Instance Management microservice startup. If you can provide the complete logs, we'll take a look. We've also seen...

Can you also attach the logs for the `Instance Management` microservice? It looks like something failed in the user management implementation, but it's not possible to tell what failed by...