Yes, I was replying to Dan.
Reading the settings back from that file was never implemented, I’m sorry!
I don’t have time to make that work before my holiday. And afterwards, let’s just get the new version ready asap.
I have a slightly more complicated solution though!
go to http://raspberrypi.local/sockettest.php
Or instead of raspberrypi.local use the IP address.
As messageType, enter setParameters
As message, copy content from the file between brackets, for example:
{"cooler_ti": 1800, "heater2_kp": 10.0, "cooler_td": 200, "heater2PwmPeriod": 4, "beer2fridge_dfilt": 4, "heater1_infilt": 1, "heater1_kp": 10.0, "beer2fridge_ti": 7200, "heater2_infilt": 1, "cooler_kp": 10.0, "heater1PwmPeriod": 4, "beer2fridge_td": 1200, "minCoolIdleTime": 180, "beer2fridge_infilt": 1, "heater2_dfilt": 4, "beer2fridge_pidMax": 10.0, "beer2fridge_kp": 2.0, "heater1_dfilt": 4, "cooler_dfilt": 4, "heater1_ti": 600, "minCoolTime": 120, "heater1_td": 60, "tempFormat": "C", "heater2_td": 60, "deadTime": 1800, "cooler_infilt": 1, "heater2_ti": 600, "coolerPwmPeriod": 1200}
That works for control settings and variables.
For your devices, do them one by one:
messageType: applyDevice
message (example):
{"a": "289E6CFF08000042", "c": 1, "b": 0, "d": 0, "f": 5, "i": 0, "h": 2, "j": 0.0, "p": 0, "t": 1}`
Check the log (in web interface) to see the result.