Getting an error

[jmayes2]

Trying to use this on a very old software hub and getting this error on the cmd line for each detected device

'WARN async_failure, error: SimpleError { err: "Output does not match regex:'

no records appear to be going out to my broker.
Can I assume this is because of the old firmware (old apontest)

TX, J

[mikekap]

Hey there! Thanks for giving this a try. Indeed it seems like the aprontest binary you have outputs in a different format than the one with which I’m testing.

Could you paste the output of “aprontest -l” and “aprontest -l -m N” where “N” are all the device ids you see in the first command? I can roll out a fix pretty quickly after I have those!

[jmayes2]

Hi, Thank you for getting back to me! I was getting nowhere trying to get my hub to update, have it too hacked up to connect to their servers anymore. ``` [root@flex-dvt ~]# aprontest -l Found 4 devices in database... MASTERID | INTERCONNECT | USERNAME 1 | ZIGBEE | LV_Lamp1 2 | ZIGBEE | LV_Lamp2 3 | ZIGBEE | Fireplace-L 4 | ZIGBEE | Fireplace-R [root@flex-dvt ~]# aprontest -l -m 1 Device has 2 attributes... LV_Lamp1 ATTRIBUTE | DESCRIPTION | TYPE | MODE | GET | SET 1 | On_Off | STRING | R/W | ON | ON 2 | Level | UINT8 | R/W | 0 | 0 [root@flex-dvt ~]# aprontest -l -m 2 Device has 2 attributes... LV_Lamp2 ATTRIBUTE | DESCRIPTION | TYPE | MODE | GET | SET 1 | On_Off | STRING | R/W | ON | ON 2 | Level | UINT8 | R/W | 0 | 10 [root@flex-dvt ~]# aprontest -l -m 3 Device has 2 attributes... Fireplace-L ATTRIBUTE | DESCRIPTION | TYPE | MODE | GET | SET 1 | On_Off | STRING | R/W | ON | ON 2 | Level | UINT8 | R/W | 254 | 254 [root@flex-dvt ~]# aprontest -l -m 4 Device has 2 attributes... Fireplace-R ATTRIBUTE | DESCRIPTION | TYPE | MODE | GET | SET 1 | On_Off | STRING | R/W | ON | ON 2 | Level | UINT8 | R/W | 254 | 254 [root@flex-dvt ~]# ``` I am not exactly sure what I need to do once the server is working, will the devices just show up in HA or do I need to add an integration? Thankx again for your help! J

…

On Thu, Dec 10, 2020 at 12:45 PM Mike Kaplinskiy ***@***.***> wrote: Hey there! Thanks for giving this a try. Indeed it seems like the aprontest binary you have outputs in a different format than the one with which I’m testing. Could you paste the output of “aprontest -l” and “aprontest -l -m N” where “N” are all the device ids you see in the first command? I can roll out a fix pretty quickly after I have those! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOELA6M43YT6ILURX6NFYK3SUECKVANCNFSM4USF4M5A> .

[BobRyan530]

I'm getting a different error but potentially related. I had a new, unopened, hub I pulled out yesterday and rooted before ever connecting it to the internet. I think I got it updated to the most current release. I setup homeassistant for the first time today and while I'm able to control the device using aprontest I can't seem to control it through MQTT. Attempting to publish a packet to topic 'home/wink/1/set' with payload '{"On_Off": 0}' I'm getting the failure below

Dec 12 02:17:49.453 WARN async_failure, error: SimpleError { err: "Bad attribute type: STRING" }, type: poll_device
Dec 12 02:17:59.380 WARN async_failure, error: SimpleError { err: "Bad attribute type: STRING" }, type: poll_device
Dec 12 02:18:09.540 WARN async_failure, error: SimpleError { err: "Bad attribute type: STRING" }, type: poll_device

[root@flex-dvt ~]# aprontest -u -m 1 -t 1 -v OFF
Update device with master ID 1, setting value OFF for attribute 1
Waiting for 1 callbacks...
Received a myNodeDataCallback from Zigbee
                Source: aprontest
                Event:  RADIO_EVT_NODE_UPDATE
                Status: FLX_OK
                Node:   1
[root@flex-dvt ~]# aprontest -u -m 1 -t 1 -v ON
Update device with master ID 1, setting value ON for attribute 1
Waiting for 1 callbacks...
Received a myNodeDataCallback from Zigbee
                Source: aprontest
                Event:  RADIO_EVT_NODE_UPDATE
                Status: FLX_OK
                Node:   1

[root@flex-dvt ~]# aprontest -l
Found 1 devices in database...
MASTERID |     INTERCONNECT |                         USERNAME
       1 |           ZIGBEE |            New HA Dimmable Light

Found 0 master groups in database...
GROUP ID |             NAME |            RADIO |

Found 0 control groups in database...
GROUP ID |             NAME |            RADIO |

[root@flex-dvt ~]# aprontest -l -m 1
Gang ID: 0x7ce8f9f9
Manufacturer ID: 0x10dc, Product Number: 0xdfbf
Device is ONLINE, 0 failed tx attempts, 4 seconds since last msg rx'ed, polling period 0 seconds
Device has 14 attributes...
New HA Dimmable Light
   ATTRIBUTE |                         DESCRIPTION |   TYPE | MODE |                              GET |                              SET
           1 |                              On_Off | STRING |  R/W |                              OFF |                              OFF
           2 |                               Level |  UINT8 |  R/W |                              254 |
           4 |                         NameSupport |  UINT8 |    R |                                0 |
       61440 |                          ZCLVersion |  UINT8 |    R |                                1 |
       61441 |                  ApplicationVersion |  UINT8 |    R |                                2 |
       61442 |                        StackVersion |  UINT8 |    R |                                2 |
       61443 |                           HWVersion |  UINT8 |    R |                                1 |
       61444 |                    ManufacturerName | STRING |    R |                               GE |
       61445 |                     ModelIdentifier | STRING |    R |                        SoftWhite |
       61446 |                            DateCode | STRING |    R |                         20150515 |
       61447 |                         PowerSource |  UINT8 |    R |                                1 |
      258048 |                        IdentifyTime | UINT16 |  R/W |                                0 |
     1699842 |               ZB_CurrentFileVersion | UINT32 |    R |                         33554952 |
  4294901760 |                   WK_TransitionTime | UINT16 |  R/W |                                  |

EDIT:
version information
[root@flex-dvt ~]# grep 0 /database/cf*
/database/cf_build:00.01
/database/cf_fver2:00.01
/database/cf_fver3:04.01

[mikekap]

Sorry for the duplicate post, just wanted to include formatted aprontest output:

[root@flex-dvt ~]# aprontest -l
Found 4 devices in database...
MASTERID |     INTERCONNECT |                         USERNAME
       1 |           ZIGBEE |                         LV_Lamp1
       2 |           ZIGBEE |                         LV_Lamp2
       3 |           ZIGBEE |                      Fireplace-L
       4 |           ZIGBEE |                      Fireplace-R

[root@flex-dvt ~]# aprontest -l -m 1
Device has 2 attributes...
LV_Lamp1
ATTRIBUTE |               DESCRIPTION |   TYPE | MODE |          GET |
     SET
        1 |                    On_Off | STRING |  R/W |           ON |
      ON
        2 |                     Level |  UINT8 |  R/W |            0 |
       0

[root@flex-dvt ~]# aprontest -l -m 2
Device has 2 attributes...
LV_Lamp2
ATTRIBUTE |               DESCRIPTION |   TYPE | MODE |          GET |
     SET
        1 |                    On_Off | STRING |  R/W |           ON |
      ON
        2 |                     Level |  UINT8 |  R/W |            0 |
      10

[root@flex-dvt ~]# aprontest -l -m 3
Device has 2 attributes...
Fireplace-L
ATTRIBUTE |               DESCRIPTION |   TYPE | MODE |          GET |
     SET
        1 |                    On_Off | STRING |  R/W |           ON |
      ON
        2 |                     Level |  UINT8 |  R/W |          254 |
     254

[root@flex-dvt ~]# aprontest -l -m 4
Device has 2 attributes...
Fireplace-R
ATTRIBUTE |               DESCRIPTION |   TYPE | MODE |          GET |
     SET
        1 |                    On_Off | STRING |  R/W |           ON |
      ON
        2 |                     Level |  UINT8 |  R/W |          254 |
     254

[root@flex-dvt ~]#

[mikekap]

This should be fixed in 0.1.4 - just re-run the installation command and let me know if you find any more issues!

[jmayes2]

Now I am getting "Segmentation fault" when I try to run it.

…

On Sat, Dec 12, 2020 at 11:16 PM Mike Kaplinskiy ***@***.***> wrote: This should be fixed in 0.1.4 - just re-run the installation command and let me know if you find any more issues! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOELA6MXBW34SR7GH4NDCJDSUQ53FANCNFSM4USF4M5A> .

[mikekap]

That's unfortunate - sorry to hear that! Segmentation fault is pretty weird - wink-mqtt-rs doesn't use any unsafe code itself, so it's definitely a head scratcher.

Do you have any more information before the crash? Does anything get printed in the log file (/var/log/wink-mqtt-rs.log) at all? (e.g. INFO init_logger, min_log_level: Info or similar). If you do have some logging, could you try adding -vvv to the command line args (lives at /opt/wink-mqtt-rs/config) to print as much output as it can?

If there aren't any logs, if you could get a core dump, that would help. Try running ulimit -c unlimited before starting wink-mqtt-rs.

In theory the old firmware should be uninteresting for the actual binary - the binary completely statically linked and isolated from the host filesystem. As part of releasing 0.1.5 I did upgrade rust itself, so maybe that's the cause somehow?

[jmayes2]

Sorry, I have been to busy to get back to you sooner. I made progress using my other hub (same firmware ver). No segmentation error now. I need to reinstall it again on the other hub, I think the file is corrupt. FYI this firmware does not support the install command you provided. The SSH is outdated plus TAR does not support the z option. I have to manually import the tar.gz then unzip and untar.

Now that it's running I get this in the log;

Jan 02 04:07:50.371 INFO init_logger, min_log_level: Info
Jan 02 04:07:50.372 INFO starting, version: 0.1.5
Jan 02 04:07:50.373 INFO opening_client, client_id: wink-mqtt-rs, port: 1883, h$
Jan 02 04:07:50.379 INFO poller_starting, resync_interval: 10000
Jan 02 04:07:50.508 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:50.810 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:50.884 INFO discovered_device, name: LV_Lamp1, id: 1
Jan 02 04:07:51.037 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:51.227 INFO discovered_device, name: LV_Lamp2, id: 2
Jan 02 04:07:51.267 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:51.491 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:51.498 INFO discovered_device, name: Fireplace-L, id: 3
Jan 02 04:07:51.776 INFO discovered_device, name: Fireplace-R, id: 4
Jan 02 04:07:51.784 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:52.029 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$
Jan 02 04:07:52.257 WARN loop_encountered_error, err: Io(Custom { kind: Invalid$

It continues with the loop_encountered_error error over and over.

Thankx again for working on this!
J