Thanks for all the info all
But still have the problem with vera3 on ui7
Cribben, I follow the instructions on the my sensor vera plugin and it comes up with ver 1.3 and no lib #
how did you get the new plugin to load
Any help at all would be welcome as ui7 is not too smooth yet.
@nca78 about my gateways:
an old gateway running on MySensors 1.5 for years now. There are several nodes and sensors connected through it like temperature sensors, relays, switches. It controls my heating system with heat pump, buffering, 18 circles of floor heating, garden irrigation, alarm system, and some lights just for fun.
the new gateway is a gateway to a Bluetooth network. Since MySensors has a great serial API and I have some experience with it I preferred to use it without a radio. I also think that it will be an interesting way of development and it could help to make MySensors even more popular. I had an idea to fork the library but unfortunately I don't have the experience and time to make it in good quality. But I'm sure letting developers to build connectors to different protocols is a very good idea. Catching Bluetooth messages from the air and decode them (with some reverse engineering) to send it through the MySensors gateway is relatively simple compared to the bidirectional communications. Processing some simple sensor data is a good first step.
By creating the file org.eclipse.smarthome.mqttbroker.cfg in the service folder (/usr/local/etc/openhab2/services in my case, chown to openhab), with the contents
name=mosquitto
host=192.168.1.69
secure=false
port=1883
username=
password=
retain=true
I was able to just create the MySensors MQTT gateway (using paperui) and it stayed online (no mqtt broker defined, but its addon is installed). I had the impressions that with the latest versions it should be possible to do everything in the PaperUI, and that the broker would use the mqtt2 addon (but in paper ui, service, config, mqtt tab, mqtt system broker connection, manage->plus button -> expert mode, I get to see the contents of the cfg file above)
But unfortunately, it seems that the discovery services enters a endless loop (maybe I need to update my arduinos sketch to the latest mysensors code?) and I don't get any auto discovered things. If I trigger a new discovery it will stop the previous one and start again.
Finally, I was able to manually create a thing, and link items on it. Eventually my battery level and humidity were displayed in the paper ui control page (after some weird delay, not updating once it shows in the log. the temperature didn't show up though).
Not sure if my understanding is off (or paperui is limited in this sense) but in the "thing" creation page I only get to specify one child id. Then my multi sensors/value nodes would need to be define in multiple things? As I can't properly define channels for each child id, and I'm not sure what var1-5 are all about.
I'll try defining things/channels/items directly in files in the following days, because so far I couldn't enjoy most of the benefits of this new version (auto discovery, logical grouping of physical device in "things", questionable "do-it-all in paper ui"), and I'm almost considering using mqtt1 binding in the new install
Although it should not be too difficult to make the MQTT Gateway with WiFi work on hardware and software level it is a bad idea on system level:
WiFi and MySensensor NRF24L01+ use the same 2.4 GHz band and with the antennas close a transmit from one will block the other and vice-versa.