nograx / ioBroker.zendure-solarflow

An ioBroker adapter for Zendure SolarFlow devices
MIT License
24 stars 6 forks source link

Hyper and ACE units don't seem to appear. #52

Closed ppitkin closed 2 months ago

ppitkin commented 3 months ago

Firstly - A BIG thankyou for developing this interface. definitely more reliable than using the MQTT feed.

Describe the bug
The new Hyper and ACE devices do not seem to be picked up and delivered in the feed.

Zendure has just started sending the information via the MQTT connection - so I am assuming it should also be available via the API. I do not however see the devices appearing in the IOBroker Object list.

I do receive the data when using the MQTT connection.

Any chance that you could take a look at the issue.

If you don't have those devices I would be more than happy to assist with testing I have: Solarflow 1200 (3 units) Solarflow 2000 (3 units) AIO (1 unit) Hyper 2000 (3 units) ACE (1 unit)

nograx commented 3 months ago

There will be an update in the next days which includes support for the ACE 1500 and the Hyper 2000.

nograx commented 2 months ago

Update 1.7.0 is available. Please Test this version, as I don‘t have a ace of hyper for direct testing.

ppitkin commented 2 months ago

version 1.7.0 doesn't appear to be showing up in the list of available adaptors - its still the old version. I also tried switching to the beta repository and it still didn't appear :-(

OK managed to force it to load 1.7.0 by entering the specific version number.

Log file giving warnings and the Hypers are not being shown - only the 6 Solarflows and the 1 AIO

avascript.0 | 2024-07-29 10:09:54.569 | info | script.js.Zendure.Hyper_2: {"gridInputPower":58,"electricLevel":16,"sn":"EE1HYMCFM160013","outputPackPower":37} -- | -- | -- | -- zendure-solarflow.0 | 2024-07-29 10:09:53.154 | info | [onConnected] Connected with MQTT! zendure-solarflow.0 | 2024-07-29 10:09:50.969 | warn | State "zendure-solarflow.0.A8yh63.YrQ1X08v.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.911 | warn | State "zendure-solarflow.0.A8yh63.14CWUD28.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.899 | warn | State "zendure-solarflow.0.A8yh63.Yy912A87.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.896 | warn | State "zendure-solarflow.0.73bkTV.hCNDkQfy.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.893 | warn | State "zendure-solarflow.0.73bkTV.Mu49k0SQ.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.891 | warn | State "zendure-solarflow.0.73bkTV.M5qsmu87.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.887 | warn | State "zendure-solarflow.0.yWF7hV.NL9W6xs0.wifiStatus" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-29 10:09:50.760 | info | [onReady] Found 7 SolarFlow device(s). zendure-solarflow.0 | 2024-07-29 10:09:50.283 | info | [login] Login to Zendure Rest API successful! mqtt.2 | 2024-07-29 10:09:49.226 | info | Server: Changed type of "mqtt.2.ModusGateway3.Zaehler1.Leistungsfaktor_L1" from "string" to "number" zendure-solarflow.0 | 2024-07-29 10:09:45.718 | info | starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.zendure-solarflow, node: v18.20.3, js-controller: 5.0.19 host.iobroker | 2024-07-29 10:09:45.033 | info | instance system.adapter.zendure-solarflow.0 started with pid 2896 mqtt.2 | 2024-07-29 10:09:44.166 | info | Server: Changed type of "mqtt.2.ModusGateway3.Zaehler1.Leistungsfaktor_L1" from "number" to "string" host.iobroker | 2024-07-29 10:09:42.483 | info | instance system.adapter.zendure-solarflow.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zendure-solarflow.0 | 2024-07-29 10:09:42.427 | info | terminating host.iobroker | 2024-07-29 10:09:41.981 | info | stopInstance system.adapter.zendure-solarflow.0 send kill signal zendure-solarflow.0 | 2024-07-29 10:09:41.926 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zendure-solarflow.0 | 2024-07-29 10:09:41.926 | info | terminating zendure-solarflow.0 | 2024-07-29 10:09:41.925 | info | Got terminate signal TERMINATE_YOURSELF
nograx commented 2 months ago

Hm, that's strange. Can you try to use the "Install from Github" option in ioBroker (Advanced Mode) and install the current version from Github?

The Beta repo should contain version 1.7.2 from tomorrow.

ppitkin commented 2 months ago

Sorry but i have no idea how to install something in iobroker directly from github. never done that before.

What I did was select the adaptor an tell it to install a specific version and then i specified 1.7.2 It appeared to work and the adaptor is now saying its version 1.7.2

However, I still see that its detecting no additional devices - It says in the log that it detected 7 solarflow devices (that would be my 3 1200 Hubs, my 3 2000 hubs and my AIO. It is not seeing the 3 Hypers - although I am seeing those devices on the direct MQTT feed that I have running in parallel to your plugin.

is it possible to but the adaptor into a debug logging mode so that we can determine why it doesn't see the devices?

Also for the existing Solarflows it has a new "control" value (control.setInputLimit) - but it doesn't create the object and therefore throws an error in the log.

zendure-solarflow.0 | 2024-07-31 12:02:00.286 | warn | State "zendure-solarflow.0.A8yh63.YrQ1X08v.control.setInputLimit" has no existing object, this might lead to an error in future versions -- | -- | -- | -- zendure-solarflow.0 | 2024-07-31 12:01:59.269 | warn | State "zendure-solarflow.0.A8yh63.14CWUD28.control.setInputLimit" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-31 12:01:57.725 | warn | State "zendure-solarflow.0.A8yh63.Yy912A87.control.setInputLimit" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-31 12:01:57.113 | warn | State "zendure-solarflow.0.73bkTV.hCNDkQfy.control.setInputLimit" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-31 12:01:56.253 | warn | State "zendure-solarflow.0.73bkTV.Mu49k0SQ.control.setInputLimit" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-31 12:01:54.773 | warn | State "zendure-solarflow.0.73bkTV.M5qsmu87.control.setInputLimit" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-31 12:01:52.357 | warn | State "zendure-solarflow.0.yWF7hV.NL9W6xs0.control.setInputLimit" has no existing object, this might lead to an error in future versions zendure-solarflow.0 | 2024-07-31 12:01:47.374 | info | [onConnected] Connected with MQTT! zendure-solarflow.0 | 2024-07-31 12:01:46.478 | info | [onReady] Found 7 SolarFlow device(s). zendure-solarflow.0 | 2024-07-31 12:01:45.892 | info | [login] Login to Zendure Rest API successful! zendure-solarflow.0 | 2024-07-31 12:01:43.818 | info | starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zendure-solarflow, node: v18.20.3, js-controller: 5.0.19
nograx commented 2 months ago

It's possible by activating the "advanced mode" on the command bar when you navigated to "adapters". Then there will be an Icon to install from Github (just use the dropdown to select the Zendure Solarflow adapter).

Otherwise, version 1.7.3 should be in the beta repository... 1.7.4 from tomorrow... this will also fix the "setInputLimit" issue.

Do you use the adapter in "Fallback"-Mode? I'm not sure if this will work with the Hyper.

ppitkin commented 2 months ago

Many thanks. Found it. Never used that option before. It installed 1.7.4

still no new object created in the objects view. Still says only found 7 devices.

No, I don't have the "fallback mode" selected.

zendure-solarflow.0 | 2024-07-31 14:45:51.655 | info | [onConnected] Connected with MQTT! -- | -- | -- | -- zendure-solarflow.0 | 2024-07-31 14:45:50.740 | info | [onReady] Found 7 SolarFlow device(s). zendure-solarflow.0 | 2024-07-31 14:45:50.010 | info | [login] Login to Zendure Rest API successful! zendure-solarflow.0 | 2024-07-31 14:45:47.026 | info | starting. Version 1.7.4 (non-npm: nograx/ioBroker.zendure-solarflow) in /opt/iobroker/node_modules/iobroker.zendure-solarflow, node: v18.20.3, js-controller: 5.0.19 zendure-solarflow.0 | 2024-07-31 14:45:43.250 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zendure-solarflow.0 | 2024-07-31 14:45:43.249 | info | terminating zendure-solarflow.0 | 2024-07-31 14:45:43.248 | info | Got terminate signal TERMINATE_YOURSELF
ppitkin commented 2 months ago

here the log when debug logging level enabled....

zendure-solarflow.0 | 2024-07-31 15:08:11.084 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key YrQ1X08v! -- | -- | -- | -- zendure-solarflow.0 | 2024-07-31 15:08:11.084 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:10.813 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/A8yh63/YrQ1X08v/# zendure-solarflow.0 | 2024-07-31 15:08:09.582 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key 14CWUD28! zendure-solarflow.0 | 2024-07-31 15:08:09.582 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:09.313 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/A8yh63/14CWUD28/# zendure-solarflow.0 | 2024-07-31 15:08:08.355 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:08.086 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key Yy912A87! zendure-solarflow.0 | 2024-07-31 15:08:08.085 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:07.814 | debug | [connectMqttClient] Subscribing to MQTT Topic: /A8yh63/YrQ1X08v/properties/report zendure-solarflow.0 | 2024-07-31 15:08:07.814 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/A8yh63/Yy912A87/# zendure-solarflow.0 | 2024-07-31 15:08:07.128 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:06.814 | debug | [connectMqttClient] Subscribing to MQTT Topic: /A8yh63/14CWUD28/properties/report zendure-solarflow.0 | 2024-07-31 15:08:06.584 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key hCNDkQfy! zendure-solarflow.0 | 2024-07-31 15:08:06.584 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:06.314 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/73bkTV/hCNDkQfy/# zendure-solarflow.0 | 2024-07-31 15:08:06.084 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:05.813 | debug | [connectMqttClient] Subscribing to MQTT Topic: /A8yh63/Yy912A87/properties/report zendure-solarflow.0 | 2024-07-31 15:08:05.354 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:05.085 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key Mu49k0SQ! zendure-solarflow.0 | 2024-07-31 15:08:05.085 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:04.814 | debug | [connectMqttClient] Subscribing to MQTT Topic: /73bkTV/hCNDkQfy/properties/report zendure-solarflow.0 | 2024-07-31 15:08:04.814 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/73bkTV/Mu49k0SQ/# zendure-solarflow.0 | 2024-07-31 15:08:04.296 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:03.814 | debug | [connectMqttClient] Subscribing to MQTT Topic: /73bkTV/Mu49k0SQ/properties/report zendure-solarflow.0 | 2024-07-31 15:08:03.755 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key M5qsmu87! zendure-solarflow.0 | 2024-07-31 15:08:03.755 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:03.312 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/73bkTV/M5qsmu87/# zendure-solarflow.0 | 2024-07-31 15:08:03.212 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:02.944 | debug | [triggerFullTelemetryUpdate] Triggering full telemetry update for device key NL9W6xs0! zendure-solarflow.0 | 2024-07-31 15:08:02.944 | debug | Subscription of IOT Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:02.943 | debug | Subscription of Report Topic successful! zendure-solarflow.0 | 2024-07-31 15:08:02.813 | debug | [connectMqttClient] Subscribing to MQTT Topic: /73bkTV/M5qsmu87/properties/report zendure-solarflow.0 | 2024-07-31 15:08:02.671 | info | [onConnected] Connected with MQTT! zendure-solarflow.0 | 2024-07-31 15:08:01.819 | debug | [connectMqttClient] Subscribing to MQTT Topic: iot/yWF7hV/NL9W6xs0/# zendure-solarflow.0 | 2024-07-31 15:08:01.818 | debug | [connectMqttClient] Subscribing to MQTT Topic: /yWF7hV/NL9W6xs0/properties/report zendure-solarflow.0 | 2024-07-31 15:08:01.815 | debug | [checkStatesJob] Starting check of states and connection! zendure-solarflow.0 | 2024-07-31 15:08:01.797 | debug | [connectMqttClient] Connecting to MQTT broker mq.zen-iot.com:1883... zendure-solarflow.0 | 2024-07-31 15:08:01.797 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey A8yh63 and deviceKey YrQ1X08v. zendure-solarflow.0 | 2024-07-31 15:08:01.797 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey A8yh63 and deviceKey 14CWUD28. zendure-solarflow.0 | 2024-07-31 15:08:01.796 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey A8yh63 and deviceKey Yy912A87. zendure-solarflow.0 | 2024-07-31 15:08:01.796 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey 73bkTV and deviceKey hCNDkQfy. zendure-solarflow.0 | 2024-07-31 15:08:01.796 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey 73bkTV and deviceKey Mu49k0SQ. zendure-solarflow.0 | 2024-07-31 15:08:01.796 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey 73bkTV and deviceKey M5qsmu87. zendure-solarflow.0 | 2024-07-31 15:08:01.796 | debug | [createSolarFlowStates] Creating or updating SolarFlow states for productKey yWF7hV and deviceKey NL9W6xs0. zendure-solarflow.0 | 2024-07-31 15:08:01.794 | info | [onReady] Found 7 SolarFlow device(s). zendure-solarflow.0 | 2024-07-31 15:08:01.102 | debug | [getDeviceList] Getting device list from Zendure Rest API! zendure-solarflow.0 | 2024-07-31 15:08:01.101 | info | [login] Login to Zendure Rest API successful! zendure-solarflow.0 | 2024-07-31 15:07:58.929 | debug | [onReady] Using server global zendure-solarflow.0 | 2024-07-31 15:07:58.897 | debug | Schedule restart: 0 0 * * *

In my MQQT feed I dont have the products listed - only the devices image

ppitkin commented 2 months ago

image

ppitkin commented 2 months ago

If I "Shared" my Hypers with you in the Zendure app would you then be able to pick them up in your feed?

nograx commented 2 months ago

I have a suspicion: Do you use your 3 Hypers as a cluster? Maybe the cluster will appear as a different product...

Are you a member in the iobroker Forum? Maybe you can send me a PN there and I will give you the e-mail for my Zendure dev account.

ppitkin commented 2 months ago

no I'm not clustered - each hyper is on its own phase. I will try to reach out to you in the forum

ppitkin commented 2 months ago

Issues now solved in latest release - Thanks. You can close the ticket.