YaSolR with JSY Remote?

[hallard]

Hi there,
Just to be sure, JSY remote is just a remote and does not any routing correct?
If so is it possible to connect YaSolR to a JSY remote, I did not see any option about this setup?

I know I can direct use YaSolR but I also need to grab JSY data for other usage (at high speed) so JSY Remote is exactly what I need, but I also need to keep YaSolR and want to avoid using JSY hardawre boards.

[mathieucarbou]

Just to be sure, JSY remote is just a remote and does not any routing correct?

Correct! This is just a .ino file in the MycilaJSY project examples to flash on an ESP which sits on the main electric panel, connected to a JSY. You'll need to configure the ESP pins for RX and TX, that's all. It displays the JSY channels in a dashboard, and also sends the data through UDP.

In the project, there is also an .ino file showing how to read the data, remotely, in a client dashboard.

That's what I sue also at home to spread my Enedis stats to different ESP boards. UDP means they have to be on the same network (by default). It's really fast. The reading rate is up to 25 jsy reads per second, but there is a mechanism to only send data when a stat changes, and since the JSY makes available in its registers the stats at about 300 ms, this gives roughly 3 UDP messages sent per second in reality.

I don't use the second clamp of my JSY, but I could for example monitor my solar production with the second one.

Ref:

• https://yasolr.carbou.me/manual#jsy-mk-194t-remote
• https://github.com/mathieucarbou/MycilaJSY/tree/main/examples/RemoteUDP

[mathieucarbou]

Note for YaSolR: if you have a JSY Sender in your network, it will be automatically detected by YaSolR. You can also test by activating / deactivating "Enable UDP Transfer" in the sender the behaviour of YaSolR when stats becomes missing and appear again ;-)

[hallard]

@mathieucarbou that was the part I was missing, I was pretty sure Yasolr could works with sender, thank for the tips

[mathieucarbou]

@mathieucarbou that was the part I was missing, I was pretty sure Yasolr could works with sender, thank for the tips

Yes it can :-) Built-in and works out of the box, Zero config needed thanks to UDP :-)

[mathieucarbou]

I have updated the MycilaJSY porject: https://mathieu.carbou.me/MycilaJSY/

• Pre-built firmware (with default pinout) are available and ready to flash with OTA: https://github.com/mathieucarbou/MycilaJSY/releases

• JSY Remote USP Sender doc update: https://github.com/mathieucarbou/MycilaJSY/tree/main/examples/RemoteUDP

[hallard]

Thanks, awesome, I wanted to test before flashing remote sender.
As binaries for MycilaJSY remote UDP sender are for OTA, I just flashed YasolR pro version with factory (restarting from scratch) version of YasolR on a fresh board (same version running on production version with JSY). And then wanted to update to Remote UDP Sender with OTA.

The deal is that I'm unable to find how to OTA update from YasolR, I remember not able to do so last time bud did not pay attention. But this time searched everywhere (at least I think) from WEBUI of YasolR but can't find it. /update page is not displaying elegant OTA.

Do I miss something?

[hallard]

Ok, self answer I think it's too big so need safeboot, but restarting in safeboot just loose device (until reset), I think it's just not yet implemented correct? Another idea is that safeboot partition is not on Factory Build for pro. Look at the logs below, after safeboot set, device restart and just lock in this boot state

[  4719][I][YASOLR][1][y-pio] Enable NTP
[  4730][I][NTP][1][y-pio] Syncing time with pool.ntp.org
[  4731][I][YASOLR][1][y-pio] Enable mDNS
[  4742][I][YASOLR][1][y-pio] Enable UDP Server on port 53964
[ 61227][I][YASOLR][1][async_tcp] Dashboard refresh requested
[ 62713][E][vfs_api.cpp:99] open(): /littlefs/mqtt-server.pem does not exist, no permits for creation
[405233][I][YASOLR][1][async_tcp] Dashboard refresh requested
[414974][E][vfs_api.cpp:99] open(): /littlefs/mqtt-server.pem does not exist, no permits for creation
[410054][I][YASOLR][1][y-core] Restarting YaSolR Pro main_f6ca6ab in SafeBoot mode...
[410055][W][SYSTEM][1][y-core] Set boot partition to safeboot
[410302][W][SYSTEM][1][y-core] Restart!
E (429194) wifi:NAN WiFi stop
[420162][W][STA.cpp:135] _onStaArduinoEvent(): Reason: 8 - ASSOC_LEAVE
[410323][W][YASOLR][1][arduino_events] Disconnected!
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4688
load:0x40078000,len:15448
load:0x40080400,len:4
ho 8 tail 4 room 4
load:0x40080404,len:3196
entry 0x400805a4

[mathieucarbou]

I didn't follow what you are doing 😅

• YaSolR is a big firmware so you need to flash it initially with the factory firmware (see the Manual - everything indicated)

• updating YaSolR can be done through the app, in the management section, allowing to restart in safeboot mode

• for mycila jsy sender firmware which is deployed, this is just the app firmware, based on a a standard partition table. But I agree with you that I should have put instructions on how to flash it and also generate a factory image to flash at offset 0.... I will update today the project and doc to make that clear with some commands to run.

[hallard]

YaSolR is a big firmware so you need to flash it initially with the factory firmware (see the Manual - everything indicated

Correct no pb with that

updating YaSolR ça ne done through the app, in the management section

This is exactly the point, I don't have option to update :-)

for mycila jsy sender firmware which is deployed, this is just the app firmware, based on a a standard partition table. But I agree with you that I should have put instructions on how to flash it and also generate a factory image to flash at offset 0.... I will update today the project and doc to make that clear with some commands to run.

This is okay for this one, just /update

[mathieucarbou]

This is exactly the point, I don't have option to update :-)

Read the manual ;-) Updating with a safeboot partition requires to restart the ESP into its recovery partition.

https://yasolr.carbou.me/manual#firmware-update

This is okay for this one, just /update

Yes because this is a standard use case with no recovery partitions, 2 ota partitions of the same size, so a live OTA will update the currently unused ota partition and switch to it.

You can read more about how a safeboot recovery partition works here:

https://github.com/mathieucarbou/MycilaSafeBoot

Note: Tasmota uses the same mechanism also (except that they went a step further in automating the update through downloading a remote firmware).

[mathieucarbou]

I have updated the pio script and CI to generate 2 kinds of images for the sender:

• factory image
• ota image

Instructions in the README have also been updated.

https://github.com/mathieucarbou/MycilaJSY/releases/tag/v9.1.9

[hallard]

Read the manual ;-) Updating with a safeboot partition requires to restart the ESP into its recovery partition.

yes it was rebooting in safe mode, but as I was seeing nothing in the log (the full firmware says access point is running as far as I remember) so didn't even thought looking on Wifi AP available, sorry my bad, you're correct I should have RTFM 🥇

I have updated the pio script and CI to generate 2 kinds of images for the sender:

Awesome thanks

[hallard]

@mathieucarbou just to let you know I tried to flash an ETH-WT01 board with JSYRemoteUDPSender-wt32-eth01.FACTORY.bin you mention above, and it fires me the following error about bad magic byte in firmware each time.

Detecting chip type... ESP32
Connecting...

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-D0WDQ5 (revision v1.0)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: NO
 - Has Factory-Calibrated ADC: YES
 - MAC Address: 8C:CE:4E:95:78:44
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
 - Flash Size: 4MB
Unexpected error: The firmware binary is invalid (magic byte=FF, should be E9)

Tried also just in case JSYRemoteUDPSender-esp32dev.FACTORY.bin, same error to so I tried YaSolR pro firmware YaSolR-main-pro-wt32_eth01-en.FACTORY.bin and worked like a charm.

Suspect ci-build issue for factory for remote version.

[hallard]

if that's true, that's pretty nice and I didn't know of any tool doing that!

L'essayer c'est l'adopter :-)

[mathieucarbou]

@hallard : ok, should be fixed! https://github.com/mathieucarbou/MycilaJSY/releases/tag/v9.1.10

[hallard]

Works thanks

just to be sure I'm not missing something, with this version we can't change GPIO JSY RX/TX pin, need to be build and flash from vscode to do so?

2nd question, when doing safe boot even with Ethernet Board, it's mandatory to connect to WiFi AP presented by the device to do so? No way once running fine on Ethernet to restart in safeboot mode and access to Elegant OTA with Ethernet only? I tested few minutes ago and I was only able to do with Wifi. And, after OTA, I was not sure device was running in Ethernet (may be stayed on Wifi), will check this one.

[mathieucarbou]

Yes, with this you have to use the défaut tx/Rx mapping set in the code (they are listed on the readme page). If I remember this is going 4 and 25

[mathieucarbou]

Safeboot does not support eth: the goal of a safeboot partition is to be as small as possible to give more size to the app image.

When restarting YaSolR in safeboot mode, only ap more is available to flash.

Jsy sender is a normal app: there is no safeboot bust just 2 ota partitions and you can flash live at /update

For YaSolR, if eth is available, the initial captive portal is skipped. Eth has priority. You can even set static IP in YaSolR. Eth boards are slower to boot because there is an initial timeout at startup let to allow DHCP before starting the captive portal if no network cable is connected

[hallard]

Hi @mathieucarbou

I installed the new version of JSY with 2 external tor, and connected to an old Denky D4 flashed with Sender of RemoteUPD with success

Remote JSY working as expected with correct values, thank you very, rocks.

Anyway when running YaSolR on same network, this one get automaticly values sent by Remote JSY, rocks also :-)

But as grid source, looks like it takes the 2nd channel, not the 1st one, is that intentional?
Since I'm building on my own with custom RX/TX pin also, I can build also swapping channel powers 1 and 2, but just surprised to see this.

[mathieucarbou]

C'est limite pour le mien... Je pense que le boitier mériterait 1 millimètre en moins d'épaisseur et 1 mm en moins de heuteur

[mathieucarbou]

je viens de mettre à jour le stl:

• épaisseur couvercle + boitier passée de 3mm à 2mm (donc gain de 2mm à l'intérieur)
• hauteur des cyclindres intérieurs passée de 8mm à 7mm (donc gain de 1mm à l'intérieur)
• hauteur boitier passée de 45mm à 42mm donc gain de 3mm en hauteur

[hallard]

excellent top, tu sais aligner les cylindres avec les trous de la carte ? faut vraiment que je regarde ces histoires de custom boitiers en 3D j'ai bien vu qu'on pouvait modifier mais je sais pas encore comment et dans quelles mesures.
J'aimerais vraiment y glisser l'ESP32 aussi dedans (et en POE pour être royal)

Un peu comme mon 1er modèle mais sans le connecteur USB (je sais pas pkoi je sens qu'il va te plaire ce connecteur)

[mathieucarbou]

Un peu comme mon 1er modèle mais sans le connecteur USB (je sais pas pkoi je sens qu'il va te plaire ce connecteur)

Ahah! J'en ai plusieurs en stock de ces connecteurs là, avec capuchon. Ils m'ont bien servis pour faire des prototypes de mon projet Beelance (balances connectées en LTE-M /NB-IoT pour ruches)

[hallard]

bien vu :-)