Announcement

Collapse
No announcement yet.

DeSerialization errors

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    DeSerialization errors

    Does anyone know where to start looking to resolve errors like this? Running v3.0.10.0 of the Z-wave PI on HS 4.2.16.0.

    -----------
    DeSerialization errors can cause a loss of data - make a backup of the \Data\Z-Wave directory and contact support if Z-Wave devices appear to be missing information.

    DeSerializing object from Bytes to HSPI_ZWave.EvACT_ZWAVE from [ActionC]: The input stream is not a valid binary format. The starting contents (in bytes) are: 7B-22-76-69-65-77-73-22-3A-5B-7B-22-24-74-79-70-65 ...
    -----------

    The errors appear rather frequently though I haven't yet determined the trigger. The "starting contents" appear to always be the same. Any tips are greatly appreciated.​
    HS4, Insteon, Z-wave, USB-UIRT, Harmony Hubs, Google Hub/Chromecasts/Speakers, Foscam & Amcrest cameras, EZVIZ DB1 doorbell
    Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Harmony Hub, Insteon, Jon00 Homeseer/Echo Skill Helper, Harmony Hub, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

    #2
    The translation of those hex bytes to ASCII is

    {"views"$type

    Sorry not more to offer.

    Comment

    Working...
    X