Nymea 1.3 release notes

Yes, already! The reason for this short release cycle is our official launch of nymea:energy! Haven’t heard of it yet? Check out its website on https://nymea.energy. If you drive an electric car and would like to use solar power to smart charge it, this is for you! It’s our first self made product for end users which connects to wallboxes and uses PV surplus energy to charge electric cars in an optimized manner.

If you’re not the target group, fret not, there are also some little goodies included for everyone:

nymea:app got another visual upgrade. We’ve got rid of the old style bottom panel too and refreshed its visuals to a more modern look. Also the configuration page for the main views was reworked. While it may seem more boring/standard now, it should increase it’s usability though. If you’re using a Raspberry Pi with touchscreen you may be happy to hear that we’ve improved the performance a bit. During the evaluation, we’ve found some more places that give the little GPU on the RPi a hard time which we haven’t managed to address yet, but they’re on the to-do list for the future now. Thanks to @loosrob for the great testing and feedback on this one.

nymea:core got the CoAP support reworked which fixes some bugs adds some missing extensions that prevented nymea to community with Shelly devices via CoAP. The network device monitor was tuned so it should not cause devices to be marked as offline any more at the first packet loss.

In nymea:plugins the biggest change is probably the rework of the entire Shelly plugin to communicate to the devices via CoAP (or CoIoT as Shelly calls it) and finally allows Shelly devices to be connected to the Shelly cloud and nymea at the same time, or to multiple nymea instances. Thanks to @plasmediaX, who contributed a Shelly Plus device, we’ve also been able to directly add support for the 2nd generation Shelly devices. The Tasmota plugin received support for energy metering and the SystemMonitor plugin was reworked to support monitoring the entire System (CPU/Memory/Storage) as well as individual processes, including any other other processes besides nymea itself. There is one new plugin, named powerfox which adds support for the powerfox poweropti device, a LED based energy meter:

The WallBe plugin was reworked to now also support wallboxes from different brandings (but same internal chip) from Scapo and Compleo.

Besides those, obviously more smaller fixes and updates were included too.


Full changelog:

  • nymea-app (1.3.1)

    • Reworked bottom panel and main view configuration
    • Improvements in the energy MainView
    • Fixed some back buttons in the setup wizard not return to previous page
    • Performance optimizations
    • Update image for push button auth to the nymea:energy gateway
  • nymea (1.3.0)

    • Migrate pluginid in thing settings when a thing class moves
    • Add ping retry feature and provide it to the monitor
    • Some fixes in Coap
    • Add support for CoIoT
    • Fix additional interface command line parameter
    • Add phaseCount state to electricvehicle interface
  • nymea-plugins (1.3.0)

    • Shelly: Rework plugin to use CoAP instead of MQTT
    • Meross: Also list devices with a Meross owned mac address
    • TpLink: Add a timeout timer for jobs
    • New plugin: powerfox
    • Bump pyjwt from 2.3.0 to 2.4.0 in /bimmerconnected
    • Shelly: Add support for the Shelly Plus 1[PM]
    • SystemMonitor: Add more process and system monitoring capabilites
    • Bump numpy from 1.21.0 to 1.22.0 in /sunposition
    • Tasmota: Add support for energy metering
    • Keba: Add a phase count setting to the Keba germany edition
  • nymea-plugins-zigbee (1.3.0)

    • Develco: Fix a crash in handleNode()
  • nymea-plugins-simulation (1.3.0)

    • Energy: Add a simulated generic car
    • Energy: Fix phases handling on wallbox
  • nymea-plugins-genericthings (1.3.0)

    • Generic car: Add capacity and phaseCount states and settings
  • nymea-plugins-modbus (1.3.0)

    • PhoenixConnect: Rename wallbe plugin and add support for Compleo and
    • modbus-tool: Fix issue #69 : make json without blocks work again
    • modbus-tool: Add register read finished signal
    • SunSpec: Introduce reconnect on to many timeout errors and update
  • nymea-zigbee (1.3.0)

    • Fix a crash if the controller takes too long to start
    • Add Time cluster implementation
    • Implement commands for metering cluster
  • nymea-mqtt (1.3.0)

    • Improve the warning message when a client is rejected
  • nymea-experience-plugin-energy (1.3.0)

    • Keep the minutes based samples for at least one week
  • nymea-plugin-streamunlimited (1.3.0)

    • Update code to deal with changes in the Ambeo image
  • nymea-cli (1.3.0)

    • Remove deprecated API and update devices to things
1 Like

I don’t know if this issue is new to r1.3, but since I am using this feature for the first time since this release I wanted to mention it.

Using Nymea with a secondary user account is severely broken for me.

I can neither execute “Scenes” I set-up with my primary account nor can I add any of my things to favorites with any other account than my primary one.

Scenes show up as the standard icon, not the ones I have set-up with my primary user. Clicking then does not execute any instructions.

When I try to edit any of my magic, it shows the right title on edit, but it treats it like it’s a new script rather than showing existing rules.

I can rule out misconfiguration of the device since I had to do a complete re-install on a different SD Card, since my previous one died while upgrading to r1.3.

So all I did so far is setting up my things and writing a few magic scripts.

I took that chance to use a more kiosk device friendly user for both my partners phone and the raspberry pi, that runs both the server and app through the latest kiosk image I installed via Rapberry Pi Imager.

Let me know what I can provide to get to the bottom of this, thank you!

I don’t think this has anything to do with the 1.3 release. Anyhow, what permissions did you grant to the user? It sounds like there are indeed some issues in that the app shows too many controls which should be hidden because of missing permissions.

At first I created a user with “Control Things” and “Execute Magic” permissions.

When that did not work I created another user with all but “Admin” permissions.

Neither of them worked.

Now because you asked I wanted to try if the last option, which is giving another user “Admin” permission would let me do it, just to see.

The problem is that I now have an account that looks like this

and that I can’t delete it either. When I try I get this error:

Edit: All right. I got the blank account to properly show up after a restart of the system. As such I can confirm I have to use an admin account to use magic created with an admin account. “Execute Magic” and “Control Things” is not enough.

Btw, I also noticed that I cannot edit permissions of already created users.