Open DanitiKain opened 11 months ago
I installed MQTT Explorer and did notice this error -
Please Enable Six Digit User Code or KeyPad is already Locked - but that is not the case panel is unlocked.
I noticed I no longer have the Third Party Integrations option on my panel anymore. I did do a software update that was available when I checked earlier in the week. So now not sure if it was the software update that may have screwed things up or me moving to SSL.
Software Version: 2.72-ADCS 9.7.6 Build Number: 20221011_b9 Linux Version: 3.4.0 Android OS Version: 5.11
The resolution which I don't like I had to set 6 digit codes to on. I still don't know how I get to 3rd party integrations. Looks like I am stuck with the same panel_token until I can figure out how to get it back.
I noticed I no longer have the Third Party Integrations option on my panel anymore
Did you use the dealer's code to access those options?
The resolution which I don't like I had to set 6 digit codes to on
Yes, this is mandatory in more recent software versions of the panel. Without 6-digit, it is not allowed to use the control4 interface.
I used the code I have always used to set this up before the software update. Is there a list of codes to try? Maybe after the software update the installer code is now no longer able to access this feature and now I need a dealer code which I didn't need before.
This is probable yes! The installer code was sufficient for some people in the past but since I started using the panel I have always needed the dealer code. It thus might be necessary for more recent versions of the software!
Is there a list of known dealer codes or how did you obtain the dealer code?
I bought a factory-set panel, which thus had the default dealer/installer/main codes! If you bought the panel from a security provider, you can probably ask them for the code too. It's hit or miss, but technically it's your panel. Older versions of the panel also allowed for easy bruteforcing when it was 4 digits and there was no timeout between code tries, but more recent versions make it harder (6 digits + delay after 2-3 tries that failed).
I enabled Let's Encrypt and Setup SSL and the integration still works it will read the configuration of the panel. It knows what state things are in but it will no longer let me arm/disarm as I did before.
I see In Log Viewer
homeassistant.components.mqtt.sensor Invalid state message ' ' from 'homeassistant/sensor/qolsys_panel_last_error/state'
I am not sure if that is related or not be only thing I am seeing the log viewer as an error.