M
I think it's a good idea.
My todo list for mysensors is already very long and I have limited time, though, so I don't think I will code this up soon. It shouldn't be very difficult though, so anyone is welcome to have a go and make a pull request. I'll happily review.
https://www.home-assistant.io/components/mysensors/#presentation
Home assistant only supports ethernet gateways that act as servers. So home assistant will connect as the client, ie we only configure the gateway address in home assistant, not the other way around.
If you changed the optimistic setting, actuators will have assumed state and this will show in the ui as two different buttons for on and off.
I recommend to not use optimistic setting, but instead feedback the new state to home assistant.
You need to send/feedback the new state to home assistant from the node in the receive function. Otherwise home assistant thinks the message was not received by the node. This behavior is modified by the optimistic setting in the mysensors config section.
V_IR_RECORD isn't yet supported by home assistant.
Have you read about the mysensors network?
https://www.mysensors.org/about/network
You need to have basic knowledge of the different parts of a mysensors network before you start configuring the controller.
You should also read about the different gateway options.
https://www.mysensors.org/build/select_gateway
If you know the different parts of the network you will more easily understand how to configure the controller.
This is on my todo list. I hope to get to it soon.
You need to feedback the state change to home assistant by sending the new state from the receive function after the calls to digitalWrite and saveState.
Please post your json persistence file.
Add the following line in the receive function eg after the call to digitalWrite.
send(msg.set(state));
You need to feedback and send the changed state to home assistant, after writing the new state to the pin, in the receive function. Otherwise home assistant thinks that the message to change state did not reach the node, and returns to the old state.
It should be compatible as 2.2.0 is not a breaking change, as far as I know.
Please edit your post and put the sketch within code blocks so it's readable.
I think you need to specify the absolute path to the persistence file. It should be in a directory where home assistant has write permission. Usually the configuration directory is good.
@antonholmstedt
If a node is unknown it means that it hasn't sent proper presentation messages.
A debug log from home assistant and a serial log from the node in question might shed some light. Usually this problem comes from messages not reaching the gateway.
Currently you can hack it by adding those value types and values to the JSON persistence file, keeping the structure. It's not a real solution, but should work. They will get represented as sensor entities in home assistant. If you want to avoid entity_id clashes the V_VAR1 and V_VAR3 should be placed on different children.
I have on the roadmap to add an option for inital values in the mysensors home assistant config section.