You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JB is broadcasting on the UDP network broadcast range on port 55555 and the data it is broadcasting can be customized via the broadcast.data variable. This could be used to discover the JB's on the local network (IP and telnet port are broadcast along with the uuid, mac and wifi signal strength). I'm receiving data about once every 10-60 seconds from each JB on my network. If JPP used the UUID (aka get system.uuid) as the device identifier instead of the JUICEBOX_ID, then this could be automatically discovered at startup (but would a less user-friendly id). Additional fields could be added like adc0, adc9, gpio0 if somebody knows what those fields represent and they are useful for JPP or for relaying any of these overall fields to HASS as additional sensors.
The JB is broadcasting on the UDP network broadcast range on port 55555 and the data it is broadcasting can be customized via the broadcast.data variable. This could be used to discover the JB's on the local network (IP and telnet port are broadcast along with the uuid, mac and wifi signal strength). I'm receiving data about once every 10-60 seconds from each JB on my network. If JPP used the UUID (aka
get system.uuid
) as the device identifier instead of the JUICEBOX_ID, then this could be automatically discovered at startup (but would a less user-friendly id). Additional fields could be added like adc0, adc9, gpio0 if somebody knows what those fields represent and they are useful for JPP or for relaying any of these overall fields to HASS as additional sensors.Example packet:
> get broadcast get broadcast broadcast.data: mac,bssid,channel,ip,ssid,rssi,remote_terminal_port,time,version,uuid broadcast.http.host: broadcast.interface: default broadcast.interval: 10 broadcast.udp.ip: 255.255.255.255 broadcast.udp.local_port: 55555 broadcast.udp.remote_port: 55555
The documentation shows these as available variables.
The text was updated successfully, but these errors were encountered: