Open htool opened 1 year ago
The config seems slightly off looking at how the model id/name is used differently:
pi@boatnet:~ $ cat .signalk/plugin-config-data/signalk-shelly.json
{
"configuration": {
"tempUnits": "C",
"Device ID SHSW-1-98CDAC0D6A71": {
"deviceName": "Shelly 1 ",
"enabled": true,
"devicePath": "orionCharger"
},
"Device ID SHSW-1-3C6105FE1484": {
"deviceName": "Shelly 1 ",
"enabled": true,
"devicePath": "starlink"
},
"Device ID Shelly Plus 1 PM-shellyplus1pm-08b61fd5e38c": {
"deviceName": "Shelly Plus 1 PM ",
"enabled": true,
"devicePath": "dolphinCharger"
},
"nextGenPassswords": [],
"Device ID SHSW-1-D65B6A": {
"deviceName": "Shelly 1 ",
"enabled": true,
"devicePath": "instrumentpanel"
}
},
"enabled": true,
"enableDebug": true
And I noticed the old firmware, but updating that didn't make any difference :/
Hi Scott,
I've got 3 shellies running one, but one is acting strange through the plugin. This shows debug message after restart:
Especially this undefined stands out: Sep 24 11:01:07 boatnet signalk-server[21761]: 2023-09-24T09:01:07.401Z signalk-shelly discovered device shellyplus1pm-08b61fd5e38c Shelly Plus 1 PM @ undefined
It identifies as follows:
Host/dhcp/ip config is similar to other two. I can ping it and access the webinterface.
The plugin picks it up, updates some initial data but then seems to stop. Support for the Shelly Plus 1 PM is there according to the README and
shellies-ng/dist/devices/shelly-plus-1-pm.js
contains the model id.