Please, update driver one more time. There were a typo)
ok. I will "speed" to my appointment. LOL
I updated and hit configure, no new device was spawned. I deleted the device and set-it up again and now no component devices are spawned at all.
I do have to go now. I'll grab logs this evening if you haven't figured out what is happening by then.
Thanks.....
Hmm..
Yes. Logs wiil help..
I don't have such device, so cannot test myself.
The voltage didn't spawn but the rest of the children did this time. I had to restart the Shelly, it had gone off-line.
The logs are showing that there is a device called voltage sensor 101 and that it was installed but when clicking on that device in the logs it says that the device is missing.
Below are the component list and the logs. I wasn't sure what logs that you needed so I attached all 20 screenshot pages.
It looks like the driver is close to working. I can see the voltage reading being returned in the logs.
I updated the driver.
But it should work. According to your logs it behaves just like the typo mentioned before is still there (not the latest version).
With that typo device get spawned but then deleted right afterwards as it's not put in the 'white list' for child device cleaning (that removes unused child devices)
(null) int the logs means it is unable to find a child device for the specific component and id.
1 Like
I thought that's what that meant. I'll download and update again and let you know. Thanks.
All set. The Uni voltage is showing up. Thanks again. I really appreciate it.
1 Like
@dmitry.rozovik many thanks for your driver “suite”. While hunting for a driver for a Pro 3EM, I discovered your bundle hidden away in this topic. I really think it deserves its own thread!
Having down loaded the bundle, I attempted to configure the 3EM in mono phase mode, but with out success. I then discovered the note in the driver that monophase is not supported .
Are there plans to do so? Can I provide debug logs that might support the monophase mode?
Thanks again for all your efforts in developing and supporting these drivers!
Hello!
Yes, Sure. The main reason of missing support is that I simply don't have all the shelly devices at hand). And I need logs to monitor on how specific device behaves.
Specifically I need a screenshot of device data fields (attributes) at the bottom of the root device page in monophase mode after configuration (and page refresh) to see what components are reported in this mode.
The initial FW had no monophase mode at the time this device support were added.
P.S.:
In fact some "blind" support were added. But it may have issues.
Thanks for the speedy response!
I think this is what you asked for, but let me know if it's not, or if you need further info. I have the Pro 3EM set up on a "sandpit" Hubitat C7 so I can play without worrying about impacts on my production Hubitat!
Thanks for great and prompt support!
1 Like
Yes. That's exactly what I need)
Do you see any errors in the log after pressing 'configure'?
I actually can see one typo that may be blocking proper child creation. 'em1' compnents are supported in code. Yet there is a wrong function call. I have fix for it. And going to upload the update as soon as I'll get electricity back) [I have power outage atm]
In you case it should spawn 3 child devices one per phase, 1 child device for the temperature component instance and one child device for the 'reset' button,
em1:[1,2,3]
sysbtn:[1]
temperature:[1]
The bundle is updated with fix for 'em1' component
1 Like
Hi Dmitry!
Wow! That did it!
Spawned Meters 1,2 and 3, together with button and temperature!
All appear to be operating OK, but I have not had a chance to test individual meters - the Pro 3EM is set up on the bench and it's getting late here. Will get to test with live data tomorrow or Tuesday.
Again, many thanks for your contributions and your speedy response.
2 Likes
Bencj=h tested and works atreat!
Thaks again!
2 Likes
Great addition to the Shelly cohort, thank you, is there a way to be able to capture the current blind / shutter position - I have a few Shelly 2.5’s and have a rule setup in rule machine to open / close based off weather.
The devices show up under the restore command but don’t show up I’m my device list if capture is selected as an action - would this be driver related ?
Thank you
Sounds like it could be.
RM selection lists rely on driver "capabilities" (declared and implemented interfaces inside drivers).
Does the Uni Plus Analog-In voltage attribute have a multiplier in the device handler? I just ordered one and will be using resistor voltage divider to step down my 46 to 60v battery system to be below the 30v Max ADC input. So input of 60v will be divided into 30v at the ADC. So i need a multiplier input in the handler to get the attribute to display the real 60v. ADC multiplier default = 1.00 (2 decimals). In my case I would enter 2.00 or what ever it turns out to be. Voltage = ADC mapped voltage x Multiplier
It doesn't (at least I haven't seen it). You could easily do this in rule machine though.
My experience has been that the Uni has been quite accurate monitoring a 12 volt system.
The device it self according to documentation may have so called "evaluation" function.
(basically a mechanism to apply a simple formulae)
The "Shelly Plus/Pro xPM" driver can listen for such attributes if device reports them.
Specifically input child device driver has
* attribute("frequencyEvaluated", "NUMBER")
* attribute("levelEvaluated", "NUMBER")
* attribute("pulsesEvaluated", "NUMBER")
So depending on device two options may be available: RM and Shelly attribute evaluation.
1 Like
