Skip to content

Message 3 (04 02 00) decoded - Retrieve and Set WIFI and GPRS Parameters #26

Description

@lwoggardner

So more TCP dumping, spotted my wifi password in the output.... which lead to decoding the 04 02 00 message
I'm working with a SolarRiver TL-D device which reports versions as 'V1.30', and Solar Power Browser running under wine on linux.

Format of the 04 02 00 payload is

  • 1 byte - installed comms module, 1 = GPRS, 2 = WIFI, 3 = 'No Module' [1]
  • 35 char WIFI SSID
  • 60 char WIFI Password [2]
  • 4 char GPRS PIN
  • 30 char GPRS Centre Number
  • 30 char GPRS Customer Number
  • 1 byte - 'OK to Save' - 0 is ok, non-zero is false

Total 161 bytes of payload

[1] - '1','2' enable the WIFI/GPRS input fields in Browser, 0 or >3 seems to display some kind of error code.
[2] - the wifi password shows as '*********' in the app, but is communicated in the clear on the wire - which apart from being useless to customer, means any passer-by with an ethernet cable can read the WIFI password!!

Setting WIFI and GPRS values

Messsage to set parameters coming out of SolarPower Browser are 05 0x.

If 'OK to Save' is non zero in the 04 02 payload, then these messages will not be sent.
Note Browser prompts for an input password - 'samilpower88' seems to be hard coded into the app in that if you get it wrong nothing is sent.

Request payloads

  • WIFI 05 00 00 - payload SSID (35 char), Password 60 (char)
  • GPRS 05 01 00 - payload PIN (4 char), Centre(30 char), Customer (20 char)

Response is the same identifier as the request with a 1 byte payload containing the value 0x06

  • WIFI 05 00 00 00 01 06 01 0b
  • GPRS 05 01 00 00 01 06 01 0c

If the source of https://mhvis.github.io/solar/ is here somewhere, I'm happy to send a PR to update this info.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions