@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.
@electrik
Thanks, I'll have a look at those updates.
Do you mean the code I am using for my appdaemon app? I got everything I use from here: https://github.com/eifinger/appdaemon-scripts
This is much cleaner and easier to understand than my code, but let me know if you want it anyway
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
I understand that I am just trying to find out why my new sensors are not getting an auto assigned node id when all I have done is move from a ethernet gateway to a serial gateway.
We have had a few version updates in HA and I am not sure what is the cause.
The IDs for humidity and temperature shown on the HA screenshot and written in the sketch don't match up.
It looks like you have already presented the sensor node with different child IDs before and HA is still expecting the previous configuration. If you reassign an existing ID to a different type (say, S_HUM to S_TEMP), HA won't update automatically.
I would suggest doing the following:
Power down your sensor node and shutdown the HA docker
Delete the existing .pickle persistance file, which may still contain the previous node configuration
Edit configuration.yaml and change the file type of the persistance file from .pickle to .json, because it's human readable (and editable).
You may also enable debug logging temporarily to get more info about what's happening when a node sends data
Restart HA and once the MySensors integration has finished initialization, power up the sensor node again
If you don't change the current sketch, temperature should show up with the ID 1 and humidity with the ID 2 in HA. I can't spot anything wrong with it.
If it still doesn't work, have a look at the HA log, e.g. with journalctl -u your-ha.service -f -n 100 | grep mysensors
You should see that messages are incoming from the sensor node (ID 2) including the sketch name and values for every sensor, that HA subscribes to a MQTT topic for every sensor ID and that HA has saved changes to the persistante.json file.
