2022-04-28 15:23:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.bedroom_lamp_electrical_measurement is taking over 10 seconds
2022-04-28 15:38:07 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 15:52:24 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x31'
2022-04-28 15:57:58 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 16:42:40 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x0a'
2022-04-28 16:43:33 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 16:44:13 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x4a'
2022-04-28 17:02:14 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:02:16 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:03:45 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:03:47 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:33:56 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x36'
2022-04-28 17:43:32 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:43:34 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:43:50 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:51:44 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 17:51:46 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 18:24:42 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x5f'
2022-04-28 19:09:28 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xa1'
2022-04-28 19:15:28 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x3c'
2022-04-28 20:00:51 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 20:01:07 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 20:37:50 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x69'
2022-04-28 21:28:52 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:28:55 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:31:04 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x45'
2022-04-28 21:52:39 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:52:41 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:52:47 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:57:03 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:57:05 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 21:57:11 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:02:06 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:02:08 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:02:08 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:03:36 WARNING (Thread-3) [homeassistant.components.mqtt] Disconnected from MQTT server core-mosquitto:1883 (7)
2022-04-28 22:38:32 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x20'
2022-04-28 22:38:44 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:43:23 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:43:23 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:43:25 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:43:25 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:44:47 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-28 22:49:40 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x6f'
2022-04-28 22:52:45 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xe3'
2022-04-28 23:09:13 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching <IP_ADDRESS> data: Unable to connect to the device: <IP_ADDRESS>
2022-04-29 00:20:04 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x45'
2022-04-29 01:10:50 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x14'
2022-04-29 01:30:12 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x24'
2022-04-29 02:10:43 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching <IP_ADDRESS> data: Unable to connect to the device: <IP_ADDRESS>
2022-04-29 02:15:06 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x7e'
2022-04-29 02:26:44 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x7e'
2022-04-29 02:29:52 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xef'
2022-04-29 02:30:23 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x0f'
2022-04-29 02:52:22 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x0a'
2022-04-29 03:22:33 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xdd'
2022-04-29 03:43:08 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xb9'
2022-04-29 04:30:00 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x5b'
2022-04-29 04:33:54 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xb2'
2022-04-29 05:24:40 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xa8'
2022-04-29 05:30:56 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x55'
2022-04-29 05:58:17 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xdb'
2022-04-29 06:10:04 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x3f'
2022-04-29 06:11:04 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x60'
2022-04-29 06:34:44 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xdb'
2022-04-29 06:44:54 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xe1'
2022-04-29 07:06:12 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x33'
2022-04-29 07:14:58 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:15:00 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:15:06 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:16:04 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xfc'
2022-04-29 07:20:03 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:20:05 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:23:46 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:23:48 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:23:55 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:24:20 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:24:28 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:26:32 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:26:34 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:26:40 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 07:44:30 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x25'
2022-04-29 07:52:21 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xfc'
2022-04-29 08:11:51 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:11:53 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:11:59 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:15:55 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:15:57 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:16:46 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:19:07 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xa5'
2022-04-29 08:31:05 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running
2022-04-29 08:31:07 WARNING (MainThread) [homeassistant.components.automation.back_door_opens] Back Door Opens: Already running

Try making your configuration yaml similar to this:
logger:
  default: error
  logs:
     custom_components.keymaster: debug

and restart Home Assistant, this will give a better run down of what's going on.

2022-04-29 09:04:32 DEBUG (MainThread) [custom_components.keymaster.binary_sensor] Connected to zwave_js network
2022-04-29 09:04:32 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
Looks like no code slots are being checked. They would have shown up between these two lines.
Can you check in zwavejs2mqtt that the code slots are infact showing up for the lock?

Excuse my "newbie" status to HA.  I'm using zwavejs.  Do I also need to install zwavejs2mqtt for this integration work?  Did I miss that in my install?

I'll work on converting that over this after work and let you know what happens.  Again, truly appreciate your help!

I got mine working by removing all the locks, uninstalling keymaster, reboot, pairing the locks again in legacy secure mode, reinstalling keymaster and adding the locks back. I then made sure all the codes for each lock matched and was able to remove/re-add codes.
I looked through the logs and couldn't find any keymaster errors before doing the above.

I’ve done that 3 times so far with no luck.  Are you using the zwavejs2mqtt integration or just the zwave js integration?  Also, what do you mean by "in legacy secure mode?"  I believe I have been doing that, but am I'm not adding them back in correctly.
Also, when reinstalling I have been adding the lock to zwave js before installing keymaster.  Maybe I should do this the other way around?

From: tommywatson @.>
Sent: Friday, April 29, 2022 2:57:10 PM
To: FutureTense/keymaster @.>
Cc: eboline @.>; Comment @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
I got mine working by removing all the locks, uninstalling keymaster, reboot, pairing the locks again in legacy secure mode, reinstalling keymaster and adding the locks back. I then made sure all the codes for each lock matched and was able to remove/re-add codes.
I looked through the logs and couldn't find any keymaster errors before doing the above.
—
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/270#issuecomment-1113671684, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARZAC25JEOBI4KI7JFKIEXDVHQ5JNANCNFSM5REGG27Q.
You are receiving this because you commented.Message ID: @.***>

js only. When adding a device there is a link you click to get more options. I added the device then installed keymaster, I don't think the order matters, the zwave linking does, also it looks like keymaster will not update the lock if the codes mismatch, you must setup the lock with the existing codes in keymaster, then you can change them, or it appears that way for me...

I'm curious about your statement of adding the existing codes in.
I have reset the lock during this process so the only codes currently in the lock are the 2 it comes with.  Are you saying I need to add those into code slot 1 and 2 in keymaster or should they be found?

@tommywatson - Thanks for the help.  I removed everything and reinstalled with the suggestions you listed above.  Same issue.
@firstof9 - The log looks a little different now though to me, but appears to still not be checking the code slots.  That said, I do see an entity for each code slot under keymaster integration, but they all say unavailable.  Here's the log after a restart:
2022-04-29 20:02:23 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-29 20:02:23 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration keymaster which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-29 20:03:11 INFO (MainThread) [custom_components.keymaster] Version v0.0.79 is starting, if you have any issues please report them here: https://github.com/FutureTense/keymaster
2022-04-29 20:03:11 DEBUG (MainThread) [custom_components.keymaster.binary_sensor] Connected to zwave_js network
2022-04-29 20:03:11 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:16 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:16 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 367, in _handle_entity_registry_updated
await self._sync_helper(to_update, to_remove)
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 311, in _sync_helper
await self.async_get_access_token()
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 173, in async_get_access_token
raise alexa_errors.RequireRelink
homeassistant.components.alexa.errors.RequireRelink
2022-04-29 20:03:16 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 367, in _handle_entity_registry_updated
await self._sync_helper(to_update, to_remove)
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 311, in _sync_helper
await self.async_get_access_token()
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 173, in async_get_access_token
raise alexa_errors.RequireRelink
homeassistant.components.alexa.errors.RequireRelink
2022-04-29 20:03:16 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 367, in _handle_entity_registry_updated
await self._sync_helper(to_update, to_remove)
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 311, in _sync_helper
await self.async_get_access_token()
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 173, in async_get_access_token
raise alexa_errors.RequireRelink
homeassistant.components.alexa.errors.RequireRelink
2022-04-29 20:03:21 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:26 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:31 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:36 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:41 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:46 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:51 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:03:56 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:04 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:09 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:14 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:19 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:24 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:29 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:34 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:39 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:44 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-04-29 20:04:49 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)

It should be saying stuff like "Code slot 1: xxxx" where the xxxx would be your code.

Would you recommend switching to zwavejs2mqtt to see if that helps?  I'm not sure I understand why that would make a difference, but it's definitely not working right now.

It would definitely help troubleshoot easier due to the builtin UI

Are you saying I need to add those into code slot 1 and 2 in keymaster or should they be found?
Yeah, you need to put the two codes into the slots for keymaster, at least that's what seems to be going on in my installation, also if you're planning on using more than 4 digits, you have to change it in the lock, that can be a source of frustration.

I tried that.  And once enabled, the status stayed as adding.  Something else is getting mixed up because all of the entities for the key slots that are generated with the keymaster integration are showing as unavailable.
I'm going to try to switch over to zwavejs2mqtt as @firstof9 suggested and see if there is better troubleshooting information in via that route.

I'm curious, does the device info show up correctly when you look at it through config->devices? And do you see the sensors?

If I go to config->devices I see a device called "keymaster."  I do not see any sensors listed under the devices.    All of those have a red filled in circle with an exclamation point in them.  When I hover over that icon it says "Unavailable".

I wonder if this isn't your problem, your device wasn't interviewed correctly. If I go to Configuration->Devices then select Devices from the top line and search for one of my locks, I see the correct model and the sensors listed, if it doesn't show up correctly Keymaster wont work...

@tommywatson I have reinterviewed the device a few times, but I'm definitely seeing some different sensors.

It looks like you have interviewed it in the highest security mode, I could never get that to work, if you check my screenshot above my device is in legacy mode. I'd suggest you remove the device from zwave, then adding it again using legacy mode.
https://github.com/FutureTense/keymaster/issues/270#issuecomment-1113745515

@firstof9 - I switched everything over to zwavejs2mqtt last night and this morning.  I reinstalled keymaster integration and I'm not seeing anything keymaster related in zwavejs2mqtt.  That being said, I could be looking in the wrong spot.  What should be seeing here?
Also, after reinstalling keymaster, I looked at the code slot entities that are created and they are all showing as unavailable still.

I tried it that way too and was getting the same issues.  Hoping the Zwavejs2mqtt integration will give Chris some more info.  It seems to me that something is goofy with the installation because I can see the created code slot entities but they are all unavailable.

From: tommywatson @.>
Sent: Saturday, April 30, 2022 3:57:03 PM
To: FutureTense/keymaster @.>
Cc: eboline @.>; Comment @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
It looks like you have interviewed it in the highest security mode, I could never get that to work, if you check my screenshot above my device is in legacy mode. I'd suggest you remove the device from zwave, then adding it again using legacy mode.
#270 (comment)https://github.com/FutureTense/keymaster/issues/270#issuecomment-1113745515
—
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/270#issuecomment-1114052906, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARZAC23XAYJUGVYFVR6MVW3VHWNB7ANCNFSM5REGG27Q.
You are receiving this because you commented.Message ID: @.***>

Check under the usercodes section for your lock and see if anything's listing.

I don’t see a user codes section.  I re-interviewed the lock and now zwavejs2mqtt is not getting the manufacturer information, battery power, product, product code, or firmware.  That info can be seen in the zwavejs intwrgration however.

From: Chris @.>
Sent: Saturday, April 30, 2022 6:19:14 PM
To: FutureTense/keymaster @.>
Cc: eboline @.>; Comment @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
Check under the usercodes section for your lock and see if anything's listing.
—
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/270#issuecomment-1114070732, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARZAC22WGC4GDE67ADQRRX3VHW5XFANCNFSM5REGG27Q.
You are receiving this because you commented.Message ID: @.***>

No usercodes is going to be your issue, fix that and everything will fall into place.
What you are describing sounds like connectivity issues, give the troubleshooting from zwave-js a shot.
https://zwave-js.github.io/node-zwave-js/#/troubleshooting/connectivity-issues

Thanks Chris.  Sorry to keep stringing this along.  I'll try some of the connectivity trouble shooting to see if that helps.  Are you saying that the connectivity issues might be what's causing the user codes not to come in?
I did one last test before I removed the integration and attempted to start over again.  I went to the lock and deleted the two user codes the came with the device.  I did this from the physical device.  I then put the one of the codes in code slot 1 and the other in code slot 2 on the lovelace dashboard and clicked enable on each (both said, "adding").  Then I programmed those 2 codes into the physical lock and both suddenly showed as "Pin Status - Connected" on the lovelace dashboard.  I thought maybe that solved the issues!
I then added a code on the lovelace dashboard in slot 3 and clicked enable.  The PIN status is showing as "Adding" and I got a notification in HA that says "front_door_lock LOCK MANAGER
You changed the PIN for front_door_lock code slot 3. Please enable it in order to make it active."  The code however, does not work at the door.  If I program the code into to the physical lock as well, it shows as "Pin Status - Connected" and works.
Before I was explaining that the entities created by the keymaster integration were showing as "Unavailable."  What's interesting is that now the code slot 1 entity and code slot 3 entity are showing as just fine the others are still "Unavailable."  This leads me to believe it's not a connectivity issue.  I'm clearly missing a step somewhere.

If this command class in zwavejs2mqtt is missing a codeslot:

you will get the "unavailable" status for the code slots in HA.

Well, I definitely do not have that command class!  I'll work through the troubleshooting steps you provided and try to start over again.
I truly appreciate yours and @tommywatson help with this.  I'm about ready to just reload the lock in Smartthings and use that integration, but I really would rather not do that!

Usually this occurs when the interview process can't complete fully, and most of that time it's due to a poor connection/connectivity issues. Those steps should help.

I'm at a loss!  I went through the troubleshooting steps, added a usb extension to the zwave controller I am using (Zooz ZST10-700).  I excluded the lock and re-added it with the lock sitting within 3 inches of the controller.  I've tried using S2 security, I've tried using S0 security.
The only command classes in zwavejs2mqtt I can get to show up are "Door Lock v2", "Manufacturer Specific v1", "Version v2", "Configuration v1", and "Battery v1".  If I re-interview the lock, it shows up as unknown manufacturer in zwavejs2mqtt all of the command classes become "v0".  Never have I seen the "User Code" command class mentioned.  The only thing I see close to this is under "Configuration v1" and I see "[26-112-0-6] User Slot Bit Field".  This is currently blank and underneath it says "Occupied slots for User Codes (Default: 0)".
Ultimately, the lock will lock and unlock in HA just fine.  What I don't have is the ability to set a code without being at the physical lock which is something I have needed to do in the past with SmartThings.  I'd really like to get this keymaster integration to work, but it seems as though my lock is not communicating properly with the zwave controller.

I am unsure, you may need to ask Al on HA Discord about the UserCode command class not showing up.

@firstof9 and @tommywatson - I think I owe you guys a drink at a minimum!
Persistence has paid off and I finally have this working!  I think the step I was missing was restarting HA after excluding the lock from the zwave network and before I readded it back in.  I did that and again moved the zwave controller right next to the lock for the inclusion and the "User Code" command class showed up and everything worked perfectly!  I can't thank you both enough!  It even works with S2 security!  It clearly wasn't completing the interview process correctly before.
Reinstalled keymaster, added the codes I already had in the lock, they synced up immediately, and was able to add a new code no problem.  Tested it out and the worked too.
Thank you both again!

:+1:
That's great news, congrats!

Hello! A fellow BE469ZP user also getting through this hurdle haha. I am in the process of re-adding my lock to my HA and in the process of reconfiguring Keymaster. One field I have never been fully sure about in the config screen is this field here:

Does this option effect which features become available in the Dashboard? I have tried a few and some seem to allow certain UI elements to work so I have been trying quite a few. Is there a for sure one of these options I should be using for this lock? Thanks for any tips!

Use binary_sensor.fake unless you have a sensor setup to monitor if your door is open/closed.

Ok I think that's what I first used. Going through a full restart of this process to see if I can get it work again

Ok so attempting the Z-Wave JS: clear a usercode from a lock and any service I call using this system gives me a failed: Unknown Error.

Check your home-assiatant.log

File "/usr/local/lib/python3.9/site-packages/zwave_js_server/util/lock.py", line 32, in get_code_slot_value
raise NotFoundError(f"{property_name} for code slot {code_slot} not found")
zwave_js_server.exceptions.NotFoundError: userIdStatus for code slot 1 not found
2022-05-10 17:26:42 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547387693664] Error handling message: Unknown error (unknown_error)
I think it's still related to the lack of unique ID that is still causing the issue with the UI communicating with the status of the door codes

Your code slots are missing, fix that and you're set.

I have code slots set to 4, and I have 4 Code tiles on my dashboard.

No, I'm referring to fixing your zwavejs issue.

So you are saying I need to add code slots to my Z-Wave.js integration? I'm not sure I understand what you mean.

I can confirm I can call other service dev tool commands like ping and refresh values to the lock, those return a green check mark. but trying to access any codes or code slots still has the unknown error.

Sounds like the same issue I was having above.  And your currently describing exactly what I was and was not able to do.  Ultimately, it came down to the interview process, that appeared to complete properly every time, but wasn't.
What I ended up having to do (multiple times), was to exclude the lock, restart HA (missed this step and wasn't able to get it to work until I did this step), re-add the lock.  I had to move my controller as close as possible to the lock for the interview to complete entirely.  Once the interview completed, try running your dev tool commands for the user codes.  If you get the error again, it didn't complete the interview process and you start this cycle over again.  Don't forget the restart of HA between the exclude and re-include steps.
Once those dev tool commands work for a user code, you can be pretty confident that the interview completed correctly and then you can continue with the keymaster install.  I ended up switching over to zwavejs2mqtt at the suggestion of @firstof9 which definitely provide some more detail on inclusion.  If your using that, it is much easier to tell when the code slots have pulled in versus trial and error.

OK cool thanks for the tip, my Z-wave seemed pretty close to the door already and I was getting all green check marks on the interview process so i thought maybe it was good enough. I have a USB extension cable i can use and I'll try this again tomorrow. Do you have a link to the Zwavejs2mqtt setup? I'll definitely look into that as well. thanks for the tips.

https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-zwavejs2mqtt

ok i have setup my HA Z-wave adapter to be very close (nearly touching) to the lock to attempt to re-interview. I removed Keymaster and removed the lock from my z-wave.js from the collection. Rebooted the HA PI and even factory reset my lock just to start from scratch.
To begin the connection I started the inclusion mode on HA. I used the programming code method of setting the lock into inclusion mode and started the interview. The Z-Wave adapter remained close to the lock the entire interview and I received all green check marks to complete the interview. I proceeded to try to use the Developer tools window to send code setting and clearing commands but after 3 attempts of this whole process, I still can't get the code slots to be identifiable.
I'm pretty sure I'm completing the setup steps discovered in this thread correctly, so I'm trying to think of anything else to try. I don't think the Zwavejs2mqtt won't work unless I can successfully connect to a code slot on the lock correct? Should I try reinstalling my Zwave.js integration? Any tips would be awesome thank you

Do not remove the integration. Do however switch to zwavejs2mqtt.

alright i have zwavejs2mqtt setup and re-interviewed the lock through Mqtt dashboard and everything looks good from an interview standpoint. Is it from this dashboard that I attempt to change codes? I haven't found a good guide yet on using this method for changing door codes, so im not sure where to go from this initial setup point.

looking through the Z-Wave JA Config DB Browser linked in the MQTT dashboard, i found the parameter for number of User Codes. By default it's set to 0, so I set it to 4 and it said it successfully updated. However in the dashboard, that value then changes to some big 8 digit value after the update completes, and upon trying to manually set a code to slot 3, i continue to have the same error adding or removing codes through the Developer Tools Service commands. Is there a way to set codes within the MQTT dashboard that would still work when this other method does not?

Open the "User Codes" command class and see if anything is listing, example screenshot:

I'm not seeing that command class on my interface, that would have been a very obvious spot to look had i had that tho hahaha.

Once you solve this you'll be in business, try a re-interview.
Your "Configuration vundefined" is concerning, either the interview went poorly or you have some RF issues.

Ok I guess it just comes down to a complete interview. I'll keep trying to some more to see if it happens. Someone showed thier logs of the interview and showed that the sections for the codes times out. I'd like to know how to see that info to more easily somfirm the interview was successful or not. Hopefully I can eventually get a solid interview soon.

In zwavejs2mqtt, click Settings on the left then enable logging like pictured and press the Save (scroll to the very bottom on the right) button.

Finally made a smidge of progress. I finally managed to get the UserCode V1 command class showing. However when I try to set a code from the dashboard i get the error message in red. If I remove code 2 and replace it with a new value on the lock itself, the code shows up in the dashboard. So i have maybe 1 way communication with a single user code slot? is this just another case of not a complete handshake, or is this salvageable?

trying to edit the user slot bit field in another command class to change how many user codes i can store, and after saying success it returns to this crazy big number

.

If you factory reset your lock, try putting the default code in there. Mine had 2 factory codes listed on the manual.  Code A and Code B.  For some reason Code B was slot 1 and Code A was slot 2.

From: cblase @.>
Sent: Thursday, May 12, 2022 5:53:29 PM
To: FutureTense/keymaster @.>
Cc: eboline @.>; Comment @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
Finally made a smidge of progress. I finally managed to get the UserCode V1 command class showing. However when I try to set a code from the dashboard i get the error message in red. If I remove code 2 and replace it with a new value on the lock itself, the code shows up in the dashboard. So i have maybe 1 way communication with a single user code slot? is this just another case of not a complete handshake, or is this salvageable?
[error code]https://user-images.githubusercontent.com/7218636/168180254-1d7b7dbc-b7b6-47c8-9e21-f2dbeb8c4575.png
[user code]https://user-images.githubusercontent.com/7218636/168180266-796ec9c3-f600-4f94-97ba-dc7f941b3682.png
—
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/270#issuecomment-1125488934, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARZAC23R3GX734ZJGTCP6SLVJWDWTANCNFSM5REGG27Q.
You are receiving this because you commented.Message ID: @.***>

yeah i added a third code just now, from the lock and it added a second user code field on the dashboard. I have user code 1 (which was code 2 on my instruction manual) and now code 3 with a random code i typed in. I can try deleting the other default code and see if that opens up that slot. I still can't change them from the dash board though.

OK, we really need to figure out a better way to beat this bug haha I continued banging my head against this process over and over, and finally i got access to all 30 User code slots! I think the trick was I Included the lock with Legacy S0 mode and that worked. Although I distinctly remember trying that before and it didn't work. The Z-Wave + indicator on the lock shows a Red "-" indicating that it did not detect the Z-wave + status, but I'm guessing the S2 security is needed for that to be detected? The battery level indications are all not functioning either, which makes me wonder if using Legacy is worth it if I can't get the battery status. Is there a way I can get these other functions working with S0 Legacy mode?

Ah, looks like using the refresh command at least got the battery indicator back up and running that's good. As for having the Z-Wave + detected or not, I'm not really sure if that is necessary? Any benefits to having that properly detected?

well in any case, thanks all for helping me get this setup, I certainly learned a lot more with this experience than if it was simple plug and play.  Did this work for that lock?

Nothing present in panel afterwards

You have to fill that data in, issuing the command just verifies the lock accepted the command. The UI doesn't populate from the lock, especially since the BE469 and FE599 report * for the code and do not follow the zwave spec properly.

2022-05-24 11:10:21 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
2022-05-24 11:10:21 ERROR (MainThread) [custom_components.keymaster.services] Error calling zwave_js.set_lock_usercode service call: userCode for code slot 5 not found
2022-05-24 11:10:21 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1: userCode for code slot 5 not found
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 447, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 680, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1627, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/config/custom_components/keymaster/__init__.py", line 224, in _add_code
    await add_code(hass, entity_id, code_slot, usercode)
  File "/config/custom_components/keymaster/services.py", line 155, in add_code
    await call_service(
  File "/config/custom_components/keymaster/services.py", line 94, in call_service
    raise err
  File "/config/custom_components/keymaster/services.py", line 89, in call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1627, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 697, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 677, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 964, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 714, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/lock.py", line 129, in async_set_lock_usercode
    await set_usercode(self.info.node, code_slot, usercode)
  File "/usr/local/lib/python3.9/site-packages/zwave_js_server/util/lock.py", line 112, in set_usercode
    value = get_code_slot_value(node, code_slot, LOCK_USERCODE_PROPERTY)
  File "/usr/local/lib/python3.9/site-packages/zwave_js_server/util/lock.py", line 32, in get_code_slot_value
    raise NotFoundError(f"{property_name} for code slot {code_slot} not found")
zwave_js_server.exceptions.NotFoundError: userCode for code slot 5 not found
2022-05-24 11:10:21 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140589140972544] Error handling message: Unknown error (unknown_error)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 626, in handle_execute_script
    await script_obj.async_run(msg.get("variables"), context=context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1513, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 405, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 449, in _async_step
    self._handle_exception(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 472, in _handle_exception
    raise exception
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 447, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 680, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1627, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/config/custom_components/keymaster/__init__.py", line 224, in _add_code
    await add_code(hass, entity_id, code_slot, usercode)
  File "/config/custom_components/keymaster/services.py", line 155, in add_code
    await call_service(
  File "/config/custom_components/keymaster/services.py", line 94, in call_service
    raise err
  File "/config/custom_components/keymaster/services.py", line 89, in call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1627, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 697, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 677, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 964, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 714, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/lock.py", line 129, in async_set_lock_usercode
    await set_usercode(self.info.node, code_slot, usercode)
  File "/usr/local/lib/python3.9/site-packages/zwave_js_server/util/lock.py", line 112, in set_usercode
    value = get_code_slot_value(node, code_slot, LOCK_USERCODE_PROPERTY)
  File "/usr/local/lib/python3.9/site-packages/zwave_js_server/util/lock.py", line 32, in get_code_slot_value
    raise NotFoundError(f"{property_name} for code slot {code_slot} not found")
zwave_js_server.exceptions.NotFoundError: userCode for code slot 5 not found
2022-05-24 11:10:23 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2022-05-24 11:10:25 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [140588839733856] Connection closed by client
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 1
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Utilizing BE469 work around code.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 2
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Utilizing BE469 work around code.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 3
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Utilizing BE469 work around code.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 4
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Utilizing BE469 work around code.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 5
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Work around code in use.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Utilizing FE599 work around code.
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 6 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 7 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 8 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 9 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 10 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 11 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 12 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 13 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 14 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 15 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 16 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 17 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 18 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 19 not enabled
2022-05-24 11:10:26 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.002 seconds (success: True)
2022-05-24 11:10:28 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)

no, this was the same issue i had, if you have Zwavejs2MQTT setup it will tell you if it received the User Code values from the lock during the interview process. Your interview process likely did not get the User code data. I would use Zwavejs2MQTT to interview with S0 security and see if you get the User Code values pop up once the interview is complete.

Yeah I don't have any experience with the FE599 lock, but when it comes to the BE469ZP, i ran into pretty much every issue listed online and finally got success through MQTT and specifically interviewing with S0 security. It's rough but once you get it it works perfectly.

well I couldn't get S2 to work with this lock, as it never received the User codes that way, I had to fall back to S0 in order to access the codes so see if that will work for your lock.

ahh... so then the keymaster coding is maybe not setup to handle S2 format?
I use more zigbee than zwave... perhaps the lead developer on keymaster can chime in on this question?
It would make more sense why we are having issues.   the zwave controller/hub is doing its job to connect using the certified S0 protocol, but the app (keymaster) is wanting to talk via S0 protocol?

Mine is working with S2 security, but it took multiple attempts to interview the lock completely.

From: fireheadman @.>
Sent: Tuesday, May 24, 2022 12:28:08 PM
To: FutureTense/keymaster @.>
Cc: eboline @.>; Comment @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
ahh... so then the keymaster coding is maybe not setup to handle S2 format?
I use more zigbee than zwave... perhaps the lead developer on keymaster can chime in on this question?
It would make more sense why we are having issues. the zwave controller/hub is doing its job to connect using the certified S0 protocol, but the app (keymaster) is wanting to talk via S0 protocol?
—
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/270#issuecomment-1136238073, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARZAC26JVAZOXEWWFU2U7XLVLUGSRANCNFSM5REGG27Q.
You are receiving this because you commented.Message ID: @.***>

btw, this is what I was thinking about getting for an upgraded repeater
https://www.zwaveproducts.com/products/ge-enbrighten-z-wave-plus-tamper-resistant-smart-outlet-55256

haha yeah I can manipulate my lock settings blindfolded now lol

so this time I got a lot more entities....
did a factory reset on this lock first

remove battery cover
unplug battery
press schlage button about 5 times to discharge device
hold schlage button while plugging battery in, will get 3 flashing check marks
done
then enter program code + 6  (remove all codes)   it will chime 3 times
then enter program code + 0 (zwave inclusion mode) and add it back into HA
be sure to also have the 5 digit PIN that is behind the lock.

restarted HA since keymaster didn't recognize any changes
now it is working.
***And onto my next issue/question, does keymaster have the ability to sync codes using the parent lock?

UPDATE:   Holy COW!... found the ka-gillion automations keymaster installs.   Thought maybe I had duplicates, but no, it just doubles up for each lock I add.   This is overwhelming to say the least.
fired off the copy from parent to child automations and that did the trick, but now I need to parse through the automations yamls to get the frequency of the updates.
Didn't realize how much of a beast this app is until now.
Someone needs a full keg, not a "buy me a beer".  ;)

yeah be sure you don't generate more User Codes than you realistically need, the YAML it generates per User Code is a lot and it can bog down the system trying to load and maintain that many cards. just start with a minimal and add more as necessary

I have 4 users with a floating guest for contractors/friends.
but also have a beefy HA server, so shouldn't be a resource issue for me.   Just a lot more weeds to sift through.
Previously I was using Smartthings for my zwave implementation using RBoy's device handlers and apps to run the same functions.
I know this is off topic, but seems to be an active crowd here.....  Does Keymaster have the ability to set the security level / tamper modes for the FE599 ?  This is the only functionality I have lost.

thank you for that!.... this screen was not fully populated last time and I totally forgot about this.    so many places to do things in HA!  (love that part!)

curious if this video explaining keymaster is outdated enough that it would provide bad info?
shows a slightly different UI than I have:  https://www.youtube.com/watch?v=_NjVbQBaOjQ
I do not have a "Ping synchronized with lock" field showing in my lovelace by default.

Yes it's slightly out of date.

I now have door locks listed in Keymaster that I no longer use.  The locks never paired properly.  The devices were removed in ZwaveJS, but remain -- broken -- in Keymaster.  How do I remove the remains?  Or how do I remove Keymaster so I can start over?  Thanks

Having the same issues with my Schlage lock , Lockmaster, and Z-wave. I have a Zooz ZST10 Z-Wave S2 USB Stick that I use on my HA. I just requested a firmware update from the manufacturer. They make you request it, it's not immediately available on their site. Hopefully this will fix some of the incomplete interview issues. Here is the link for those interested: https://www.support.getzooz.com/kb/article/1126-how-to-perform-an-ota-firmware-update-on-zooz-devices-in-home-assistant/

I finally got beyond "stuck on adding or deleting" today.  I noticed that some of the sensors on my locks were "unknown".  I have deleted, re-added etc the locks before but not today.  I just kept re-interviewing them, again and again until the codeslots where working.  Re-interviewed, re-started, and eventually both were working without add/removing from z-wave.  Screenshots are a lock before/after

The only thing I am seeing in that log related to keymaster is the warning about a custom integration which has not been tested by Home Assistant.
I have the packages directory and see a .yaml file for every code slot (10 in my case) along with the common and Lovelace file.  I also see a bunch of files under customs components->keymaster.  Do I need to edit any of these files?

From: Chris @.>
Sent: Monday, April 25, 2022 11:15:36 AM
To: FutureTense/keymaster @.>
Cc: eboline @.>; Comment @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
View your home-assistant.log file in the /config directory.
—
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/270#issuecomment-1108775753, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARZAC22SI5SWLWDXFZOELA3VG3AKRANCNFSM5REGG27Q.
You are receiving this because you commented.Message ID: @.***>

After trying most of the suggestions mentioned here and removing the schlage lock connect many times and adding it again, I finally succeeded to connect the pins.  To do it or to test it, do the following:
1- If your lock is reset it to default, it should come with 2 codes. create 4 codes during the keymaster configurations
2- after configuring keymaster and paste the code for the lovelace in the dashboard, add new user with its pin in the code 3 or code 4. Dont attempt to do that in code 1 or code 2. it will stuck in adding.
3- you can delete the default codes using service tab either with zwave clear code or keymaster.

nope, still does not work for many people. i have a yale and two schlages i tested with 2" from the hub. i can start from scratch, re-interview, anything you can think of, it doesn't work.
i created a new HA to test this with all the various fixes and still nothing works. the locks get stuck on adding/deleting. some people can get a random slot to work, or add codes manually first then add to keymaster, but what's the point? you're introducing a layer of complexity for no reason.
this issue goes back 1-2 years with various brands. threads get closed with no real resolution and there are multiple threads open with this issue. i would not trust this integration until this is fixed.

nope, still does not work for many people. i have a yale and two schlages i tested with 2" from the hub. i can start from scratch, re-interview, anything you can think of, it doesn't work.
i created a new HA to test this with all the various fixes and still nothing works. the locks get stuck on adding/deleting. some people can get a random slot to work, or add codes manually first then add to keymaster, but what's the point? you're introducing a layer of complexity for no reason.
this issue goes back 1-2 years with various brands. threads get closed with no real resolution and there are multiple threads open with this issue. i would not trust this integration until this is fixed.

Did you delete all the default codes that come with the lock? I was experiencing the same issue for weeks. I finally resolved by deleting all the codes and then went to the keymaster and start creating the users and their codes. I dont remember if I had to restart HA.

If it is of any help for anyone else, seeing I've been banging my head too on this issue for a while, I have solved it with the workaround automation I shared here!

I am having the same issue described above. I am on 2023.1.7 on my main instance running zwavejs getting events over WS from an rpi that has my zwave stick running HASS 2023.1.7 w/ zwavejs there. My zwave network is (from what I can see) super stable. My lock is a BE469ZP Here is what I have found:

In debug mode, keymaster gets the pins from slots 1-9 that are set.
using the zwavejs HASS service, I can set the pins of 1-9 w/o issue
Keymaster shows pins 1-3 in adding/deleting and those pins never get set. Zwavejs doesnt even get the event.
Setting pins 4-9 in keymaster works properly

So seems like a bug in keymaster dealing with those first 3 pins

Hopefully this helps as I was having the same issues as everyone else here and this resolved the problem for me:
Lockset: Schlage BE469ZP
using Z-Wave JS integration

include your lock on the z wave network
click the include/exclude button on the lockset (inside battery coder)
re-interview the lock from HA
All data should now come in and pins should start working.

solution found on reddit: https://www.reddit.com/r/homeassistant/comments/tuxdu9/schlage_connect_lock_cannot_set_usercodes/

Oof - that sounds like a painful process for someone with a lot of locks paired with automations already tied to them. I have five BE469ZP's, and they're finicky to pair short of removing the control board and battery pack and re-adding right next to the controller. Wish only step 3 was necessary for slots 1-3 to work and not be stuck in deleting/adding state.

A re-interview can be done in place, you don't have to move the lock anywhere.

A re-interview can be done in place, you don't have to move the lock anywhere.

Thanks - there's a known issue with the BE469ZP that causes re-interviews to lose all nodeinfo details until a magic amount of tries fixes it.
https://github.com/zwave-js/node-zwave-js/issues/3484
Used it as a chance to update my stick's firmware, so not all was lost. Unfortunately, after getting it reinterviewed correctly, the lock is still stuck on deleting. I don't think these locks are solid candidates for tweaking with. If it works with basic functionality, I'd leave it be.

I had been having this same issue, all codes stuck adding/deleting. Background, had working config with 2 x Schlage B468, zwave-js and key master. zwave-js handled by 2 x raspberry pi with zooz USB ZST10 sticks.  I accidentally cleared zwave config on one of the zooz sticks while upgrading firmware, and when I added everything back in I could never get key master to properly handle codes for the door that had to be re-configured. Long story short, for troubleshooting, in zwave-js, make sure your lock has the User Code command class (go to device detail, Node section, you should see "User Code v1" or some such along with other details. If you don't see it, re-interview the node, and you might need to tick the "Reset security classes" checkbox.
I have to wonder if Keymaster could show an intelligent error when trying to handle codes if the "User Code" command class is absent.

Having this issue on my Yale Assure 2 lock after swapping out the ZW2 module for the ZW3 module.  I deleted the existing keymaster integration and created a new one.  The code slots set through keymaster are actually being set in the lock, but keymaster doesn't reflect that (stuck on "Adding").  I can manually use both the zwave_js.{set_lock_usercode,clear_lock_usercode} and the keymaster.{add_code,clear_code) services to set and clear codes, and those both succeed (the "Call Service" button changes to a checkmark after a few seconds).
When setting the code through the UI, the debug logs show the error message "DEBUG: Code slot NNN not enabled":
2023-10-13 18:04:48.289 DEBUG (MainThread) [custom_components.keymaster] Add Code service: <ServiceCall keymaster.add_code (c:01HCNH468QJ4FJNSW6ARVV98A9): entity_id=lock.assure_2_keyless_touch_screen_deadbolt, code_slot=2, usercode=12345>
2023-10-13 18:04:48.290 DEBUG (MainThread) [custom_components.keymaster.services] Attempting to call set_usercode...
2023-10-13 18:04:52.782 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 1 not enabled
2023-10-13 18:04:52.782 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 2 not enabled
2023-10-13 18:04:52.782 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 3 not enabled
2023-10-13 18:04:52.782 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 4 not enabled
2023-10-13 18:04:52.782 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 5 not enabled
...
2023-10-13 18:04:52.839 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 496 not enabled
2023-10-13 18:04:52.839 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 497 not enabled
2023-10-13 18:04:52.839 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 498 not enabled
2023-10-13 18:04:52.839 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 499 not enabled
2023-10-13 18:04:52.839 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 500 not enabled

I've tried resetting all of the code slots manually through the service calls.  Any idea what causes the "Code slot NNN not enabled" message?

I tried debugging this a little more.  It looks like the "Code slot NNN not enabled" is coming from here: https://github.com/FutureTense/keymaster/blob/a35388b0d269ba8f4487247f8d799989c442bcc0/custom_components/keymaster/init.py#L606, which is calling into zwave_js here: https://github.com/home-assistant-libs/zwave-js-server-python/blob/ca30b7558eeac921582e3dabd8d0591d3f4364bc/zwave_js_server/util/lock.py#L80.  I didn't see any reference to this function in the zwave_js debug output.
Here is the zwave_js debug output when adding a new usercode.  The zwave_js messages show success in setting the usercode.  However there is no mention of the get_usercode function which keymaster is calling.  Any idea how to debug this further?
home-assistant_zwave_js_2023-10-16T13-17-29.568Z.log

Check to make sure the code slot is enabled via the zwavejs_ui control panel.

Check to make sure the code slot is enabled via the zwavejs_ui control panel.

I'm using the official Z-Wave JS add-on, not the Z-Wave JS UI unfortunately.  I don't see anything about code slot in the list of enabled or disabled entities, nor in the zwave-js configuration page.  Is there any other way to look this up?

Only way I know how.

A re-interview can be done in place, you don't have to move the lock anywhere.

Thanks - there's a known issue with the BE469ZP that causes re-interviews to lose all nodeinfo details until a magic amount of tries fixes it.
zwave-js/node-zwave-js#3484

Just spent a crazy amount of time trying to get this working, until I found your comment. Sure enough everything started working fine after a series of re-interviews and rebooting my HA server. Fortunately I don't have a frequent need to update pins, set schedules for them etc and that is the primary thing that this bug impacts.
At any rate @FutureTense maybe consider marking this issue as resolved or won't fix and add a note in the docs?

Sorry to reply to this thread again, but I'm having this issue again, although I've found a workaround and I wanted to get your thoughts on it.
Removing existing codes works.  They do not get stuck.  However when adding a code, KeyMaster gets stuck at "Adding".  I do get a notification saying that the code has been added, and the code actually works on the door lock.  However KeyMaster doesn't know that the code was successfully added, and remains at "Adding".  The problem with this is that when I disable a code slot, the code isn't actually disabled, I assume because KeyMaster thinks it was never actually enabled.
The first workaround that I found was to go into Z-Wave JS UI, go to the User Code config, and click "Refresh Values".  This works.  It takes a while to refresh all of the values though, and generates a lot of traffic with the lock.  When I look at the events in Z-Wave JS UI, I can see all code slots being refreshed, from slot 1 to 500, and it takes several minutes to complete.
A shorter way that I've found to refresh this value is by issuing the following service call from HA:
service: zwave_js.invoke_cc_api
target:
  entity_id: lock.assure_2_keyless_touch_screen_deadbolt
data:
  command_class: "99"
  method_name: get
  parameters:
    - 5

The parameter '5' is the code slot to refresh.
I'm wondering if this is a bug in zwave_js, and if I should report it there?

In case anybody needs it, I've permanently worked around this issue by creating an automation which triggers on the user code add zwave-js notification event, and then issues a zwave-js CC command to refesh the specific slot which generated the event.  The device_id in the trigger is the device id for the lock.
alias: Fix Keymaster User Code Add
description: ""
trigger:
  - platform: device
    device_id: ebcc82a6df7be991068406c54e9be498
    domain: zwave_js
    type: event.notification.notification
    command_class: 113
    type.: "6"
    event: "14"
condition: []
action:
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: notify.mike_notify
    metadata: {}
    data:
      message: Detected User Code Add {{ trigger.event.data.parameters.data[1] }}
    enabled: true
  - service: zwave_js.invoke_cc_api
    target:
      entity_id: lock.assure_2_keyless_touch_screen_deadbolt
    data:
      command_class: "99"
      method_name: get
      parameters:
        - "{{ trigger.event.data.parameters.data[1] }}"
mode: single

I'll just add how I got mine working. Called the clear lock user code svc on slot 1. Then all my slots started working again. Good luck.

I'll just add how I got mine working. Called the clear lock user code svc on slot 1. Then all my slots started working again. Good luck.

Unfortunately this doesn't resolve the issue for me.


communication: in environment with a few agents, some agents cannot re-connect

We see numerous following errors:
http/wsserver.go:75 (*WSServer).serveMessages ...host_id error, connection from XXX(YYY) conflicts with another one
This causes problems as the agents stop sending their data/flow logs.
A few possible hypothesis:

maybe at disconnect agents don't disconnect gracefully and their entry remains in the tables of existing speakers
while in the code we try to disable connection of a few speakers with the same ID for comparison we test only if they come from the same host. Maybe we should check a pair <HostName, Port>

fixed: #538


Ldfc spectrogram color correction issue #274

I have adjusted rendering of indices in blue ie CVR and EVN. I have also changed the colour correction for blue. This has broken unit tests involving ldfc spectrograms but can be easily fixed. Main issue is can you check the adjusted colours of ldfc spectrograms, especially the one which had insect track with a cyan halo around blue.
Closes #274

Concerning the above comment, I have been doing some reading on colour spaces and have decided that to do it properly would take more effort than I have the time for. I have reduced the effect of the "correction". I do not have the ability to test on a range of images where the "correction" can be stress tested. I have also changed the normalisation constants for EVN and CVR which are typically rendered in blue. On my test image the overall effect is to reduce the intensity of blue/cyan in ldfc spectrograms.

I have made the adjustment for blue color optional by incorporating a parameter into the config file.
The default is no adjustment. however in my tests, some adjustment is helpful. Have fixed all unit tests.


Client Allocation Request for: asd

Client Allocation Questions
Core Information

Name: asd
Website / Social Media: asd, (asd, asd)
Region: Albania
DataCap Requested: 11.13 TiB
Addresses to be Notarized: sdasd
Notary Requested: Bobby Choi

Application created via filplus.storage

This user’s identity has been verified through filplus.storage


Support for huggingface/peft

After looking through the code it currently seems to not be possible to lead adapter models produced by peft. It would be a great addition to HF DLCs.

Hello @dennisbappert, it should be possible to use PEFT models through a custom inference.py module. See for an example on how to create a inference.py https://www.philschmid.de/custom-inference-huggingface-sagemaker
Or have you tried this already?

Hi @philschmid, no I haven't tried it yet but I do also think that it is possible. Integrated support however would make it much easier to use out of the box without custom inference scripts.
Likely just a feature-request for the future :+1:

Hey @dennisbappert,
Thats a great feature request, indeed! but PEFT is still pretty new lets revisit this in a few months when we have a better understanding how it is used.


Chore/move utilities

Proposed changes
Tiny PR that moves two utility functions, as_context and is_port_in_use, from tests to test_tools. These were first introduced in #384 (see https://github.com/valory-xyz/open-aea/pull/384#discussion_r998557115)
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[ ] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

failures

ubuntu 3.10 and macos 3.9 =================================== FAILURES ===================================
 _________________________ test_supervisor_not_started __________________________

     def test_supervisor_not_started():
         """Test that TestThreadGuard supervisor thread not started."""
         timeout = 0.1
         sleep_time = 0.5

         exec_limiter = ExecTimeoutThreadGuard(timeout)

         with exec_limiter as exec_limit:
 >           assert not exec_limiter._future_guard_task
 E           assert not <Future at 0x7f44006b2f80 state=pending>
 E            +  where <Future at 0x7f44006b2f80 state=pending> = <aea.helpers.exec_timeout.ExecTimeoutThreadGuard object at 0x7f44006b0100>._future_guard_task

 tests/test_helpers/test_exec_timeout.py:179: AssertionError


Create seating map

Wanted to use this to create an office seating map based off a floor plan image. Is that possible?

Not sure I follow how would you do it based on an image? You mean you want to use background image and then write your points manually or what is that you want to create? Also, wouldn't it be easier to do this with proper drawing tools?

Yes as a background image and mark the point where to show Information. Well those tools have cost and this let's me write out everything in ps 😁.

Basically I'm thinking of a staff seating chart that's tied to a lookup table. That I can host HTML file anywhere.

Should be doable - needs this working first: https://github.com/EvotecIT/PSWriteHTML/issues/61 so someone needs to add this first.
And then you would disable physics, make fixed x/fixed y/ use X and Y position and probably other options.

Yup that's what I wanted to confirm if I missed it. I'll close this out then. Thanks.


Domain name matching rules in the plugin do not take effect as expected

Ⅰ. Issue Description
After binding the basic-auth plugin to the domain name "a.test.com", it takes effect.
The results are as follows:
➜  / curl -i localhost/put -H "host:a.test.com" -X PUT
HTTP/1.1 401 Unauthorized
www-authenticate: Basic realm=MSE Gateway
date: Wed, 01 Nov 2023 03:23:02 GMT
server: istio-envoy
content-length:

But when the port is added to the domain name, it does not take effect.
For example:
➜  / curl -i localhost/put -H "host:a.test.com:80" -X PUT
HTTP/1.1 200 OK
server: istio-envoy
date: Wed, 01 Nov 2023 03:24:42 GMT
content-type: application/json
content-length: 631
access-control-allow-origin: *
access-control-allow-credentials: true
req-cost-time: 2
req-arrive-time:<PHONE_NUMBER>031
resp-start-time:<PHONE_NUMBER>033
x-envoy-upstream-service-time: 1
{.......}

Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Even if the port is added to the domain name, the domain-level  will still take effect.
Ⅳ. How to reproduce it (as minimally and precisely as possible)

Create domain name "a.test.com"
Configure basic-auth plugin
Create route /put
Use curl to access

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

Higress version:  1.2.0

Thanks for the suggestion, I'll fix it.

@TC-wang  Try it again, maybe need restart the gateway pod, because the wasm image's pull policy is IfNotPresent by default.

ok，thanks


Rendering objects with CSS3DRenderer

I'm having a bit of difficulty getting Three's CSS3DRenderer to work in conjunction with hecs-plugin-three.
I want the ability to render both Object3D-type objects as well as CSS3DObject-type objects. Each is added to a separate three.js scene graph, but both share the same camera and transform data.
The problem seems to be that hecs-plugin-three assumes that an entity with component WorldTransform should automatically get an Object3D component added:
export class Object3DSystem extends System {
  order = Groups.Initialization

  static queries = {
    new: [WorldTransform, Not(Object3D)],
    active: [WorldTransform, Object3D],
    removed: [Not(WorldTransform), Object3D],
  }
...
  update() {
    this.queries.new.forEach(entity => {
      const object3d = new THREE.Object3D()
      object3d.name = entity.name
      object3d.userData.entityId = entity.id
      this.presentation.scene.add(object3d)
      this.presentation.object3ds.push(object3d)
      entity.add(Object3D, { value: object3d })
    })
...

WorldTransform is part of hecs-plugin-core, and gets added automatically when a Transform component is added to the entity. If I include hecs-plugin-three, then every entity automatically also gets an Object3D added as well.
I'm trying to think of a way to tell hecs-plugin-three that for this particular entity with WorldTransform, don't add the Object3D component to it, and don't add it to the presentation.scene graph. Let me handle it elsewhere (i.e. by a CSSObject3DSystem, for example).

I think I mostly have this working now. It turned out that in order to create mixed-mode HTML+WebGL, I needed an Object3D anyway, so although it might be nice to not add Object3D when unnecessary, it's no longer pressing for me.

Yeah hecs-plugin-three might be a confusing name but the intention was to only support the WebGLRenderer.
It would probably be better to have a separate plugin but I might be wrong?

I think we can close this. It was flexible enough for me, and I agree a more complex setup might merit a separate plugin.


Sponsors & Exhibitor page

Number of Volunteers: 3
TODO (Updated after #41)

[x] Edit sponsors.json. The information below need to be provided by the sponsor. For demo purpose, just put some generic values.

[x] change the logos (needs to upload images to the folder static/images/acl2020
[x] add a channel field to record the RocketChat channel, currently set them to example_sponsor
[x] add a description field to record the sponsor descriptions
[x] add a website field to record the link to the external Sponsor's website
[x] add a zoom_schedule field (list) to record Zoom Room links and schedules for live QA sessions.
[x] add a contact field (list) to record contact person information.
[x] other, e.g., downloadable links

[x] Edit main.py here to make sure the sponsor data is properly loaded. Note site_data stores the raw sponsors.json, whereas by_uid["sponsors"] record a uid-to-sponsor lookup dict.
[x] Edit sponsors.html and components.html here to make sure the "Sponsors" page look nice. See ICASSP 2020 for reference.
[x] Edit sponsor.html to make sure the individual sponsor pages look nice.

[ ] Should show the sponsor level.
[x] Should show the sponsor logo.
[x] It seems that the page is auto-focused on the RocketChat channel. Should disable this behavior.

It seems to work fine now??? Need more testing

@Chandrahasd Thanks for working on this. This is currently one of our top priority thing because sponsors need to see a working example to get some more ideas.
Please let me know if you have any questions.
@luanyi Can you send necessary information to @Chandrahasd you get from sponsors?
For missing information, we can put a placeholder field for demo purpose.

[ ] Edit sponsors.html and components.html here to make sure the "Sponsors" page look nice. See ICASSP 2020 for reference.

@Chandrahasd This might be a good starter project.

@hao-fang Sure! I'll start with this one.

UPDATE about RocketChat channels (cc @luanyi)
We will use public Broadcast Channels.  Broadcasted channels behave like read-only channels, with only users with the right permission being able to post there.

Users without permission (the same one to post on read-only channels) inside this channel won't be able to see each other in the user list.
Users without permission won't be able to react to messages.
Every message contains a reply button that redirects the user to a direct message with the user that posted the message.

Source: https://docs.rocket.chat/guides/user-guides/channels#creating-channels.
I've changed the current #example_sponsor to be a broadcast channel. You can use a test account to see what it looks like. (Your admin account will be able to post messages.)

(cc @hao-fang ) I see that @Chandrahasd has already an open PR on sponsors.html so I do hesitate to make it more beautiful by myself. Can we take the images from the ACL sponsor page and use them or do we need to ask sponsors to give them to us again? I would have a look to fix the style of sponsor.html. The other next steps I see are either blocked (sponsors.html) or need input (sponsor.html needs real data).

(cc @hao-fang ) I see that @Chandrahasd has already an open PR on sponsors.html so I do hesitate to make it more beautiful by myself. Can we take the images from the ACL sponsor page and use them or do we need to ask sponsors to give them to us again? I would have a look to fix the style of sponsor.html. The other next steps I see are either blocked (sponsors.html) or need input (sponsor.html needs real data).

@jcklie Yeah, I feel the best way is probably to have you start working on the sponsor.html -- there are more work to be done in those pages and I don't have a good intuition about how to arrange those components nicely. But I'll let you three to discuss with Yi to see how to collaborate efficiently :)

@jcklie @Chandrahasd @nickatomlin @luanyi
The current page looks nice!
I briefly tested the https://virtual.acl2020.org/sponsor_3.html.
Here are some points I found.

[ ] Make sure all clickable links are working.

[ ] "Visit Website" is not working

[ ] Add target="_blank" to all clickable links so it opens a new "external" pages.
[ ] It seems that after the page load, it still auto-focus on the RocketChat channel. Can we fix this?

For the sponsors.html:

[ ] If you resize the page, then the images overlap before hitting the responsive breakpoint to be one below each other
[ ] Some transparent logos get a grey background, I would make the background white for all

@jcklie  @hao-fang  The sponsors page looks really nice! Is there something more to be done on this issue for basic website? If not, then can we close this and move remaining enhancement tasks to a new issue?

I think the remaining tasks here is to fill in the missing data for some sponsors, e.g., https://virtual.acl2020.org/sponsor_17.html is not complete.
I'll let people who are working on this to decide whether to close or keep this issue open.
For now, I move this to "blocked" in the the project view https://github.com/acl-org/acl-2020-virtual-conference/projects/2

We are still waiting for information from several sponsors. The biggest remaining task is to add Zoom link to the virtual booths. I think it's better to keep this issue open at least during the dry run. The sponsors will raise some issues, and we need to adjust the virtual booths & correct some information accordingly.

Hi @jcklie, @hao-fang,
Just one minor concern. In the current sponsors' data, I have merged the following two pieces of information into a single "Resources" section.
7. Download (they can provide up to 5 pdf files)
9. A pdf or a link to the papers & presentation pointers can be submitted after the conference schedule is released.

They are shown in a single section on the sponsors' page.

Let me know if we need to change it.
Thank you.

@Chandrahasd okay with me :)

Just comparing the sponsors page with what's currently at https://acl2020.org/sponsors/list/, and I see that ByteDance is not listed in the Gold sponsors here. Should it be added?

@goodmami ByteDance is not in the sponsor list Priscilla provided us. I have never received any email from them either so I don't think they are one of our sponsors. I'll double check with Priscilla. In any case it's already too late to prepare a virtual booth for them. We can put a logo and add a link to their company.


Spring Cloud Vault Health Check Fails

Hey guys hope all is well.
I had a quick question about the health check for config server’s vault backend.
I seem to be having some trouble with it – I’m not able to access health for vault repo without an exception being thrown “No thread-bound request found”.
To illustrate the problem, I connect to vault backend. I created a ScheduledExecutorService that calls health on every HealthIndicator, every 30 seconds. The health check to vault repo fails.
On the other hand if I curl the actuator health endpoint the health check to vault repo, the health check succeeds. (curl localhost:8888/actuator/health).
I think this may have to do with ThreadLocal usage of RequestAttributes from ObjectProvider(HttpServletRequest) request called from AbstractVaultEnvironmentRepository::getWatchState.
I am using all the latest versions of projects: spring-cloud-config-server 3.1.2, spring-cloud-starter-bootstrap 3.1.2 and spring-boot-starter-actuator 2.6.7.
I’ve attached my simple, repeatable project here: https://github.com/speedo72/spring-cloud-config-vault-health
Thanks for any help.

So are you calling the HealthIndicator in some other way besides hitting the actuator endpoint?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Hey @ryanjbaxter thanks for the response. Yes am using HealthIndicator interface to manually check health unrelated to hitting actuator endpoint. I'm assuming this isn't the intended behavior. If so - happy to close this issue and avoid checking health that way.
Thanks for your contributions to the spring world.


Consider using develop as the default branch on Github

We mainly work on develop branch.  It'd be nice if the default branch is the one we work on.
It also has benefits:

less click for us to create a PR from web UI
the project page shows what's really going on
standard branch naming scheme for other users

While we are at it, if you are interested in, please use inclusive language for branch names: master -> main.
In conclusion, I propose:

Rename develop -> main
Rename master -> 1.0
Set main as the default

WDYT?
Reference:

https://github.com/github/renaming
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch

ps. For those with great muscle memory: git symbolic-ref is your help

I just noticed that when I mention an issue in a PR, it doesn't close the mentioned issue when the PR is merged.  This is because develop branch is not the default branch.  Just another reason to make development branch as the default :wink:

Okay. There you go.


Repo sync for protected CLA branch

The pull request is created from master637614637330362866 to master to fix git push error for protected CLA branch

@opbld16 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Support for namesapces &other optional Atomizer options

I might have surrendered to early! :)
Closes #1

Looks good!


Fix my bad code

globalThis.run referenced a run function in global scope, rather than
the button element. This is why that globalThis.[id] shouldn't be used.

(the linter is sad)


Double escaping "\n" still necessary in Python package

In the following query, I am still required to write "\n" instead of "\n" in order to be able to compile the query in the Python package (note that this specific query also fails for other reasons, see #61):
argmax(chatty_openai=True, max_len=256)
   "A rhyme:\\n"
   "Verse: [RHYME_START]\\n"
   for i in range(5):
      "Verse: [RHYME]\\n"
from
   'openai/text-davinci-003'
where
   len(TOKENS(RHYME)) == 5 and len(TOKENS(RHYME_START)) == 5

Are you using lmql.run or LMQL via decorator functions @lmql.query.

Aah yes, I am using lmql.run, forgot that the problem cannot be really fixed there. Maybe something to add to the documentation?


Support for Rancher installation using a proxy

Current Rancher installation requires direct access to the internet to pull various artifacts.  We need to support the capability of configuring a proxy in the event the installation is behind a company firewall.

Hello,
I know it's not exactly what you excepted, but you can use this container https://registry.hub.docker.com/u/klabs/forgetproxy/ waiting a solution from Rancher. This is how I launch rancher behind my company firewall. Hope that could help.

When starting the rancher agent container you can pass https_proxy environment variable - this will make the scripts configuring the agent use your proxy...
docker run ...... -e https_proxy=https://your.proxy.com:1234/


Fix Header Color in Maps

Update the header bar color in Community Partner Map, Legislative District Map, and Project Map.  The color should match the header in Community Partner Type map.

@Ruthie2018 as QA tester

QA passed.
https://docs.google.com/spreadsheets/d/1INwFZmhWnjrczbjh5YutTLmYp2YBk-m2HddFLZKvshE/edit#gid=547627265


[skip ci] Fix scipy intersphinx link

Scipy changed their docs recently to be pinned to each release, so we need to update the URL we pass to intersphinx accordingly. Skipping CI on this to unblock other developers but local testing with
python tests/scripts/ci.py docs

both showed the same error as CI before this change and no error after.
cc @junrushao1994

Let's goooo!!


Staging shared libraries before startup for startup hooks usage

For listen mode with nosuspend or connect mode, we'll need to have the user specify the path if the startup hook truly needs to be available at managed code startup. Because the target application will likely be executing managed code without waiting for .NET Monitor to instruct it to continue, any libraries that are required to exist at startup must be staged in an accessible location for the target process starts. This is problematic for process namespace separated environments such as Docker and Kubernetes where the target application does not have access to the file system of the .NET Monitor image.
To support these scenarios, the .NET Monitor tool should have a mode that can be used to stage the shared libraries BEFORE the target application container is started. This is typically done as an init container in Kubernetes. An example of how this may be used in a deployment is:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: deploy-exampleapp
spec:
  replicas: 1
  selector:
    matchLabels:
      app: exampleapp
  template:
    metadata:
      labels:
        app: exampleapp
    spec:
      restartPolicy: Always
      initContainers:
      - name: init-diag
        image: mcr.microsoft.com/dotnet/nightly/monitor:8.0.0-preview.3
        args: [ "init-shared-path" ]
        env:
        - name: DOTNETMONITOR_Storage__DefaultSharedPath
          value: /diag
        volumeMounts:
        - mountPath: /diag
          name: diagvol
      containers:
      - name: app
        image: mcr.microsoft.com/dotnet/samples:aspnetapp
        imagePullPolicy: Always
        env:
        - name: ASPNETCORE_URLS
          value: http://+:80
        - name: DOTNET_DiagnosticPorts
          value: /diag/dotnet-monitor.sock,nosuspend
        - name: DOTNET_STARTUP_HOOKS
          value: /diag/libs/8.0.0-preview.3.23180.9/any/net6.0/Microsoft.Diagnostics.Monitoring.StartupHook.dll
        volumeMounts:
        - mountPath: /diag
          name: diagvol
      - name: monitor
        image: mcr.microsoft.com/dotnet/nightly/monitor:8.0.0-preview.3
        args: [ "collect", "--urls", "http://localhost:52323", "--metricUrls", "http://+:52325", "--no-auth" ]
        imagePullPolicy: Always
        env:
        - name: DOTNETMONITOR_DiagnosticPort__ConnectionMode
          value: Listen
        - name: DOTNETMONITOR_Storage__DefaultSharedPath
          value: /diag
        - name: DotnetMonitor_Experimental_Feature_Exceptions
          value: 'true'
        - name: DOTNETMONITOR_InProcessFeatures__Enabled
          value: 'true'
        volumeMounts:
        - mountPath: /diag
          name: diagvol
      volumes:
      - name: diagvol
        emptyDir: {}

This was completed with the release of .NET Monitor 8.


raidboss: delay Spiral Thrust callout by 0.5s

An attempt to address #4389 by adding some more time to account
for lag.

I did try this out, it's about the same as when people in pf would be calling it out. Still plenty of time to get in position with this additional time.


Apollo Link State queries not supported

Apollo Link State (client state handling for Apollo) uses the @client directive for queries that query the local state. They can look like this:
query {
  amount @client {
    amount
  }
}

These seem to not be supported in the plugin, see attached:

Is it possible to temporarily ignore the errors from these Apollo Link State's queries ?

It's just underlining them with red, beyond that everything's fine.

I would argue that underlining them in red is not fine.  That causes the IDE to label the code as invalid.  I rely on that indicator heavily while coding to find syntax mistakes.

If you add the following into your GraphQL schema, it should prevent this from showing as an error.
directive @client on FIELD

The 2.0 alpha follows the latest GraphQL language draft spec as of June 2018.
As part of that, the plugin will pick up any client fields and directives that you declare as part of your client schema using GraphQL SDL.
Use the extend keyword to extend your existing server schema types with client fields.
See 2.0.0-alpha-2 if you'd like to try it and help test it.

Schema directives fixed in https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/releases/tag/2.0.0-alpha-3


Fix Makefile target for creating changelogs

Cherry-picked to v9.1.x branch.

Cherry-picked to v9.1.x branch.


color-rs needs to be updated to use git version as 0.8.0 has compilation error

it kinda works if you use, but there are other compilation issues that are unrelated
diff --git a/Cargo.toml b/Cargo.toml
index 25efb37..69cda08 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -21,3 +21,6 @@ stardust-xr-fusion = "0.43.2"

 [patch.crates-io.stardust-xr-fusion]
 git = "https://github.com/StardustXR/core.git"
+
+[patch.crates-io]
+color-rs = { git = "https://github.com/mirsella/color-rs.git" }

i seem to have gotten past this by using a nix build.


Remove dead onClick handler

Remove this, we got rid of it :)
Originally posted by @bobbyg603 in https://github.com/BugSplat-Git/ngb-filterable-dropdown/pull/60#discussion_r758646500

:tada: This issue has been resolved in version 14.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement maxOp's .Do() method

Turns out the Max function is defined, but the actual doing method  is not implemented.
#229  highlights the issue

@chewxy Has the problem been solved?  the max op still can't work in the master version.

Closing this issue the maxOp implementation seems ok in master thanks to #269.
https://github.com/gorgonia/gorgonia/blob/93e238839b7603ce80c10bb7cff058a77869ea33/op_reduction.go#L111-L120
https://github.com/gorgonia/gorgonia/blob/93e238839b7603ce80c10bb7cff058a77869ea33/op_reduction_test.go#L201-L237
Feel free to reopen if needed.