boc-tothefuture / kotlin-homieiot Goto Github PK

I'm interested in leveraging your library to create a Homie controller library in Kotlin, and I'd like to gauge your interest and hear what you think about the idea, if possible.

My initial thoughts include creating base classes for Device, Node, and Property that can be shared between the (your) Device library and the Controller library. I think it would also make sense to define something similar to your Publishers, but for a controller.

Thanks for your thoughts in advance.

From #2
Question 1: Defining device
When you create Device and add nodes, properties and subscriptions to them you get lot of warnings before connecting:

WARN org.homieiot.mqtt.RootHomiePublisher - Message (true) published on topic (foo/bar/baz/$settable) without connected MqttClient
WARN org.homieiot.mqtt.RootHomiePublisher - Message (baz,bax) published on topic (foo/bar/$properties) without connected MqttClient
WARN org.homieiot.mqtt.RootHomiePublisher - Message (bai,bar) published on topic (foo/$nodes) without connected MqttClient

Hi,

I have three questions of things:

Question 1: Defining device

When you create Device and add nodes, properties and subscriptions to them you get lot of warnings before connecting:

WARN org.homieiot.mqtt.RootHomiePublisher - Message (true) published on topic (foo/bar/baz/$settable) without connected MqttClient
WARN org.homieiot.mqtt.RootHomiePublisher - Message (baz,bax) published on topic (foo/bar/$properties) without connected MqttClient
WARN org.homieiot.mqtt.RootHomiePublisher - Message (bai,bar) published on topic (foo/$nodes) without connected MqttClient

Question 2: Publishing topics multiple times

Second noticeable thing is that nodes and properties are published one by one (incrementally) e.g. homie/foo/$nodes → "bar" and then homie/foo/$nodes → "bar,baz".

Do you have any plans avoid these warnings and incomplete array values? All topics should be sent during ½ s from connecting, see Timings. I think there should be 3 phases after connecting:

1. (Define and) publish all topics once.
2. Publish device state (to ready or alert).
3. Other topic value updates etc.

Question 3: Best connecting practice

When I connect in main method like client.connect().get() the main thread will continue quite fast to the end of program or System.exit(0). How to wait (forever) and not consuming CPU cycles.

/homie/off/topic

These aren't real problems, just wondering. This repository is young and very good. Thanks!

I'm new to Homie and considering rebuilding my home automation system (for about the 10th time lol) around it. I'm investigating library options and have played around with yours with good results. I see that you haven't touched it in a year and a half, and that it doesn't support Homie 4. Do you have any further plans for this project? Do you ever plan to do a release?

No pressure and no complaint. I'm impressed with what you have done, and I'm just trying to understand what the future might hold, so I can make my decisions accordingly.