You don't have to configure the gateway, just tell Home assistant the gateway is there.
Did you follow the instructions in the link @BearWithBeard mentioned?
Please note the nodes you use have to follow the presentation guide lines, else HA won't detect them automatically.
https://www.home-assistant.io/integrations/mysensors/#presentation
@electrik, Yes it not showing automatically but when go through the configure UI button I was able to add my switches. Thank you everyone for all your help. Mysensors has a great community.
@pw44 The HA integrations page has useful information of how it al works together, check the presentation paragraph as it is important in HA.
The node sketch shall make use of these defs for HA. Is it right?
So, on a node sensor, i can have from 0 to 255 child_id's, each with it's name. But how to give a name for each child, if more than one sensor is connected to the node?
The name can me customized in the presentation function in the description field:
https://www.mysensors.org/apidocs/group__MySensorsCoregrp.html#gaef20c35998db495bd4c85bac42a7ad49
bool present ( const uint8_t sensorId,
const mysensors_sensor_t sensorType,
const char * description = "",
const bool requestEcho = false
)
Is this all right? if not, please educate me in the right way.
And i'm also getting the following:
This entity does not have a unique ID, therefore its settings cannot be managed from the UI.
Any hint?
This is a normal error in current versions of HA, the mysensors integration is still manual via YAML and cannot be managed from the HA FrontEnd.
@Joerideman said in home Assistant and OTA support and node to node:
@MatiasV BTW why did you switch to mqtt? The wifi GW accepts multiple connections.
I was experiencing problems when starting the HA "server" (AKA Old laptop) and GW, or while the WIFI was temporary off for any cause. We had some rough weeks with our electricity company.
The GW would disconnect from HA and I had to restart the GW or sometimes even HA to get it working again.
It was a mayor headache while I was out of the house, the MQTT GW is way more reliable for me.
Thanks @electrik for the update
I got it running.
However I think I should make some work on the sensors.
As it seems the Ethernet GW are running 2.1.1 but I think the sensors are running 1.5.x (seen in MysController)
But I get plenty of :
2020-05-28 19:29:47 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:30:22 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:30:57 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:31:32 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:32:07 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:33:17 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:33:51 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:34:26 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:35:01 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:35:36 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:36:11 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:36:46 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:37:21 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:38:31 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:39:06 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:39:41 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-28 19:40:50 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
Trying to get my dev environment correct to be able to recompile.
EDIT: Since it have been so stable for a long time I am not up to date with the Arduino environment. My experience from the past is not without issues
Much appreciated!
This is what I ended up with for a working config:
automation: !include 'automations.yaml'
default_config: ~
group: !include 'groups.yaml'
scene: !include 'scenes.yaml'
script: !include 'scripts.yaml'
mysensors:
gateways:
- device: '/dev/ttyUSB0'
persistence_file: 'mysensors1.pickle'
- device: '10.10.1.69'
persistence_file: 'mysensors2.pickle'
tcp_port: 5003
optimistic: false
persistence: true
retain: true
version: '2.3'
