Does this still work with new Batrium Firmware/Products
KidA001 opened this issue · 5 comments
I got this up and running without errors but it isn't pushing any data to MQTT. I have a new WatchmonCore, does this not work with the newest firmware?
Hello, on the newer versions the variables adresses has changed please check the documentation. I havn't updated yet but I remered to listen to Daniel saiyng that.
but I remered to listen to Daniel saiyng that.
What do you mean by this?
I'm unclear where to change the variable addresses you mention. Assuming somewhere in the index.js as I don't see an address/path defined in the files located in the payload folder. Any pointers to the documentation appreciated
The mesages changes when There is new payload versions. You need to check The payload folder and define If That have change. I have No access testing any more. I dont got any running.
/daniel
@daromer2 thanks for chiming in, appreciated. Can I ask for a little more clarification?
I see all the files in the Payload folder. What specifically needs to change in there? Just the name of the file, i.e. Msg_5831_*.js. I'm not sure what needs to be updated specifically
And where do I find the new changes that I should be looking for, is that something that Batrium publishes?
The software is made in such a way that it will Tell you if there are new messages. But if a message is just changed internally and get new revision it may not change no. On the Secondlifestorage forum you can find more help where people still use it and have done updates. But yes Batrium need to supply the updated protocol unless you can figure it out :)
I cant help atleast im sorry. I can only push through changes if someone have them such as new message configs.
In the message id you have 4 characters. The first 2 are the message and last 2 are the revision of that message.