Clicking on temperature circle deletes the schedule

[sandreialexandru]

Clicking on temperature circle in the zone modal deletes the schedule instead of disabling it.

[pihome-shc]

@sandreialexandru temperature circle have href="javascript:active_schedule();" can you check if you have same href or different?

[sandreialexandru]

This is how I have it. If I change it like you say it does not do anything.

[pihome-shc]

is that schedulelist.php ? can you check if you have latest version

[sandreialexandru]

It is homelist.php The schedule under the modal popup window (near OneTouch) gets deleted when clicking on temperature circle. In schedulelist.php work OK.

[pihome-shc]

if you have only one zone enabled in any schedule and you disable that zone from dashboard then schedulelist do not display that but it stays in db. it is bug in schedulelist.php

[pihome-shc]

line 57 need to change from

SELECT time_id, time_status, `start`, `end`, WeekDays,tz_id, tz_status, zone_id, index_id, zone_name, `category`, temperature, FORMAT(max(temperature),2) as max_c, sch_name, max(sunset) AS sunset FROM schedule_daily_time_zone_view WHERE holidays_id = 0 AND tz_status = 1 group by time_id ORDER BY start, sch_name asc

to

SELECT time_id, time_status, `start`, `end`, WeekDays,tz_id, tz_status, zone_id, index_id, zone_name, `category`, temperature, FORMAT(max(temperature),2) as max_c, sch_name, max(sunset) AS sunset FROM schedule_daily_time_zone_view WHERE holidays_id = 0 group by time_id ORDER BY start, sch_name asc

[pihome-shc]

fixed this issue, can you test this and if it works lets close this issue

[sandreialexandru]

It is working...in some way. After clicking the circle the schedule still remains active in ../schedule.php, but with no zone selected

[pihome-shc]

yes schedule time still stay active but zone become in-active hence you see schedule time active.

[sandreialexandru]

Good enough solution for now, thank you! Do you agree that this issue can be closed? Please make a commit to the GITHUB code.

[pihome-shc]

yes, you can close this issue github is updated