For the states.json bug. If you set the run state to STOP and run zmpkg.pl status it returns stopped, as expected. If you query the API states.json it returns that the previously active run state is still active instead of all of them = 0. ???
Code: Select all
03/24/21 18:47:23.158318 zmpkg[19552].INF [main:319] [Sanity checking States table...]
03/24/21 18:47:23.166702 zmpkg[19552].INF [main:95] [Command: status]
stopped
Code: Select all
STATES response = {'states': [{'State': {'Id': '1', 'Name': 'default', 'Definition': '', 'IsActive': '0'}}, {'State': {'Id': '8', 'Name': 'Day', 'Definition': '1:Mocord:1,2:Nodect:1,3:Modect:1,4:Modect:1,5:None:1,6:None:1,7:None:1', 'IsActive': '1'}}, {'State': {'Id': '10', 'Name': 'Night', 'Definition': '1:None:1,2:Nodect:1,3:None:1,4:None:1,5:Modect:1,6:Modect:1,7:None:1,8:Mocord:1', 'IsActive': '0'}}]}