Force loading Rules - Without Function
Heishamon large, Firmware actuell
There have been several reports of this kind in the past. Now it has happened to me. There was a power outage last night. Heishamon started up correctly, but the ruleset was not loaded. As a result, the heat pump did not start up during the night.
See also #727
Ik heb een work-around via Home Assistant:
alias: HeishaMon rules crash & restore
description: ""
triggers:
- trigger: numeric_state
entity_id:
- sensor.panasonic_heat_pump_stats_14
below: 5
- trigger: state
entity_id:
- sensor.panasonic_heat_pump_stats_14
to: unknown
conditions: []
actions:
- action: notify.pushover
metadata: {}
data:
message: Heishamon rules restored
title: HeishaMon
- action: shell_command.heishamon_save_rules
metadata: {}
data: {}
mode: single
Met in configuration.yaml:
shell_command:
heishamon_save_rules: 'curl -s -X POST http://<IP ADDRESS HEISHAMON>/saverules -F rules=@/config/HeishaMon_rules.lua'
En in de config directory dus een file met de naam HeishaMon_rules.lua met mijn actuele ruleset
I can also confirm this issue and it's very easy to reproduce using following rule set
on System#Boot then
print('DEBUG: Heishamon rules start');
setTimer(1, 10);
end
on SetTargetTemperature($Temp) then
#Setpoint = $Temp;
end
on timer=1 then
#TempMax = 25;
#CompState = 0;
#Setpoint = 25;
if #CompState == 1 && @Main_Outlet_Temp >= #Setpoint + 2 then
if #Setpoint < #TempMax - 1 then
SetTargetTemperature(#Setpoint + 2);
elseif #Setpoint < #TempMax then
SetTargetTemperature(#Setpoint + 1);
end
end
end
Uploading this test rule set via http://heishamon.local/ works without problems.
It also starts without error.
By resetting the heishamon-board (via reset button) the rules does not start and I can see following error
4611: ERROR: cannot compare < with a left char value
Please fix this issue !
Many thanks, lakeroe
I do see similar errors several times, e.g. as well:
ERROR: cannot compare != with a right char value
Do you think this will ever get fixed ? I would do it myself if I could ...
Ik heb een work-around via Home Assistant:
alias: HeishaMon rules crash & restore description: "" triggers: - trigger: numeric_state entity_id: - sensor.panasonic_heat_pump_stats_14 below: 5 - trigger: state entity_id: - sensor.panasonic_heat_pump_stats_14 to: unknown conditions: [] actions: - action: notify.pushover metadata: {} data: message: Heishamon rules restored title: HeishaMon - action: shell_command.heishamon_save_rules metadata: {} data: {} mode: singleMet in configuration.yaml:
shell_command: heishamon_save_rules: 'curl -s -X POST http://<IP ADDRESS HEISHAMON>/saverules -F rules=@/config/HeishaMon_rules.lua'En in de config directory dus een file met de naam HeishaMon_rules.lua met mijn actuele ruleset
Implemented your solution today. It works wonderfully.
Of course, this feature should work, especially since it is specifically offered in the settings. Not everyone can switch to Home Assistant.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
… not solved 🤷♂️