Jump to content

Door Status issue


toddhutch

Recommended Posts

Posted

Do you want feedback from the releases here?  I just updated to 3.02, and I think there might be a bug.

 

Door3 state when open is 1%, door status when opening is 4%,  door status when closing is  3%

 

Door2 state when open is 1%, door status when opening is 4%  and when closing is 3%

 

Still working on installing Door1

Screenshot 2023-12-21 123843.png

Posted
6 minutes ago, toddhutch said:

Do you want feedback from the releases here?  I just updated to 3.02, and I think there might be a bug.

 

Door3 state when open is 1%, door status when opening is 4%,  door status when closing is  3%

Probably best for feedback in a new topic for each major issue.

This relates to the change in UOM of door state from built-in Barrier Status to a custom index UOM. It looks like, despite having upgraded the plugin, that your Admin Console is still using the old profile with Barrier Status. Restarting the Admin Console should clear it up. If not, you may need to reload the Profile for the plugin in the PG3 Dashboard and then restart the Admin Console.

The joys of being an early adopter! 😁

  • Like 1
Posted (edited)

Thank you for the quick response, door1,2,3 are installed.

I closed and opened the Admin console (environment is windows using IoX Launcher and Java)

No joy.

I clicked the Load Profile in the plyglot V3 ratgdo details screen.  Restarted the Admin console.

No joy.

Rebooted the Eisy box. 

No Joy.

Only the closed state is shown correctly for Door State.

Edited by toddhutch
Posted

I'm using the default installed MQTT and not  xKing's MQTT Node server.

Logs incase that would be helpful.
 

 
2023-12-21 14:47:43,479 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door2 - stateData: {'door': 'closed'}
2023-12-21 14:47:43,479 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door2_lt - stateData: {'door': 'closed'}
2023-12-21 14:47:43,601 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: ST to 0 UOM 97
2023-12-21 14:47:46,485 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door1 Light(door1_lt)
2023-12-21 14:47:46,508 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door2(door2)
2023-12-21 14:47:46,570 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door2 Light(door2_lt)
2023-12-21 14:47:46,578 MQTT udi_interface.interface INFO interface:_message: Successfully set door1_lt :: ST to 0 UOM 78
2023-12-21 14:47:46,578 MQTT udi_interface.interface INFO interface:_message: Successfully set door1_lt :: GV0 to 1 UOM 2
2023-12-21 14:47:46,760 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closed'}
2023-12-21 14:47:46,760 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closed'}
2023-12-21 14:47:46,782 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: ST to 0 UOM 97
2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV0 to 1 UOM 2
2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV1 to 0 UOM 25
2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV2 to 101 UOM 25
2023-12-21 14:47:46,921 MQTT udi_interface.interface INFO interface:_message: Successfully set door2_lt :: ST to 100 UOM 78
2023-12-21 14:47:46,921 MQTT udi_interface.interface INFO interface:_message: Successfully set door2_lt :: GV0 to 1 UOM 2
2023-12-21 14:47:46,962 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 0 UOM 97
2023-12-21 14:49:10,540 Command udi_interface INFO nodes:_cmdDON: Opening door for door3 in DON command handler: {'address': 'door3', 'cmd': 'DON', 'query': {}}
2023-12-21 14:49:12,506 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'opening'}
2023-12-21 14:49:12,506 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'opening'}
2023-12-21 14:49:12,626 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 4 UOM 97
2023-12-21 14:49:21,207 Command udi_interface INFO nodes:_cmdSTOP: Stopping door for door3 in STOP command handler: {'address': 'door3', 'cmd': 'STOP', 'query': {}}
2023-12-21 14:49:23,640 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'stopped'}
2023-12-21 14:49:23,641 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'stopped'}
2023-12-21 14:49:23,717 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 9 UOM 97
2023-12-21 14:49:27,693 Command udi_interface INFO nodes:_cmdDOF: Closing door for door3 in DOF command handler: {'address': 'door3', 'cmd': 'DOF', 'query': {}}
2023-12-21 14:49:29,579 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closing'}
2023-12-21 14:49:29,580 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closing'}
2023-12-21 14:49:29,696 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 3 UOM 97
2023-12-21 14:49:43,444 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closed'}
2023-12-21 14:49:43,445 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closed'}
2023-12-21 14:49:43,562 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 0 UOM 97
2023-12-21 14:50:03,674 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message setLogLevel
Posted

i am also getting same status...I think it worked on last version.

also.. locked shows locked, but unlock shows unknown

 

Posted (edited)

Problem 1 - Door State: fixed - even though I had changed the profile and code to use the Index UOM (25) for door state, since the nodes were created in v3.0.1 of the plugin, they are stuck in the PG3 database with the Barrier Status UOM (97). IMHO, state values should never be stored in a database for any reason, but in this particular case it means there was only one way to fix it: delete all of your nodes (in PG3 dashboard), restart the node server, and perform Discovery again. Instead, I just forced the code to report the door state explicitly using the Index UOM every time it is updated, so the two of you won't have to recreate your nodes.

Problem 2 - Lockout State: fixed - had an "if" that should have been an "else if".

Thanks for the testing!

Edited by Goose66
  • Like 1
Guest
This topic is now closed to further replies.

×
×
  • Create New...