MSR UI on a mobile browser

[therealdb]

zwave_device.impl_sig="24233:1:24233:2"

[toggledbits]

Are you using position.set directly, or using the relative actions?

[therealdb]

position.set.

[therealdb]

That's wonderful. I have a FGR222 (previous fw) that's working. Here's node 3:

cover.state=false
energy_sensor.units="kWh"
energy_sensor.value=0
position.value=0
power_sensor.units="W"
power_sensor.value=0
power_switch.state=true
x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Roller Shutter","model":"FGRM222","default_name":"Roller Shutter","values":[{"match":{"commandClass":38,"property":"currentValue"},"capabilities":{"cover":{"attributes":{"state":{"expr":"value !== 0"}},"actions":{"open":{"valueId":"+targetValue:#","value":99},"close":{"valueId":"+targetValue:#","value":0},"stop":{"valueId":"+Up:","value":false}}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"+targetValue:#","value":{"expr":"entity.attributes.cover.state ? 0 : 99"}}}}}}],"manufacturerId":271,"productType":769,"productId":4097}
x_zwave_values.Binary_Switch_currentValue=true
x_zwave_values.Binary_Switch_targetValue=null
x_zwave_values.Configuration_Delay_Time_After_S2=10
x_zwave_values.Configuration_Energy_Reports=10
x_zwave_values.Configuration_Forced_Roller_Shutter_Calibration=0
x_zwave_values.Configuration_Lamellas_Positioning_Mode=1
x_zwave_values.Configuration_Managing_Lamellas_in_Response_to_Alarm=0
x_zwave_values.Configuration_Motor_Operation_Detection=1
x_zwave_values.Configuration_Motor_Operation_Time=240
x_zwave_values.Configuration_Periodic_Power_or_Energy_Reports=3600
x_zwave_values.Configuration_Power_Reports=10
x_zwave_values.Configuration_Reports_Type=0
x_zwave_values.Configuration_Response_to_General_Alarm=0
x_zwave_values.Configuration_Response_to_Smoke_CO_CO2_Alarm=0
x_zwave_values.Configuration_Response_to_Temperature_Alarm=0
x_zwave_values.Configuration_Response_to_Water_Flood_Alarm=0
x_zwave_values.Configuration_Roller_Shutter_Operating_Modes=0
x_zwave_values.Configuration_Scenes_Associations_Activation=1
x_zwave_values.Configuration_Self_Measurement=0
x_zwave_values.Configuration_Switch_Type=0
x_zwave_values.Configuration_Turning_Time_Delay_Time=150
x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=99
x_zwave_values.Manufacturer_Specific_manufacturerId=271
x_zwave_values.Manufacturer_Specific_productId=4097
x_zwave_values.Manufacturer_Specific_productType=769
x_zwave_values.Meter_reset=null
x_zwave_values.Meter_value_65537=0
x_zwave_values.Meter_value_66049=0
x_zwave_values.Multilevel_Sensor_Power=0
x_zwave_values.Multilevel_Switch_Close=null
x_zwave_values.Multilevel_Switch_Open=null
x_zwave_values.Multilevel_Switch_currentValue=0
x_zwave_values.Multilevel_Switch_duration=null
x_zwave_values.Multilevel_Switch_restorePrevious=null
x_zwave_values.Multilevel_Switch_targetValue=0
x_zwave_values.Protection_exclusiveControlNodeId=null
x_zwave_values.Protection_local=0
x_zwave_values.Protection_rf=0
x_zwave_values.Protection_timeout=null
x_zwave_values.Version_firmwareVersions=["24.24"]
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="3.52"
zwave_device.capabilities=[37,38,49,50,112,114,117,134,145]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Switch"
zwave_device.impl_sig="24233:1:24233:2"
zwave_device.is_beaming=false
zwave_device.is_listening=true
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[271,769,4097]
zwave_device.max_data_rate=null
zwave_device.node_id=3
zwave_device.specific_class="Motor Control Class B"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"24.24"]

[toggledbits]

OK. I think I see it. #4 has a different type and ID, and the alias has an error. Pull the new data ZIP and try again.

[therealdb]

That did the trick. Two things. position.value is now incosistent, whereas dimming.level was ok before. I tried to set node 4 to .9, and it's now reporting .31. A refresh is updating the position (to .91), but now power_switch.state=null.

power_sensor.value is still 0.

[toggledbits]

What are you comparing it to? For node 4, the last data you show have the Meter class value (meterType 1, property value, propertyKey 66049) at 0, and the Multilevel Sensor with sensorType=4 (Power) also 0. What are you expecting the value to be? Again, can you show more context, too? Post all the attributes? These things are moving targets, so more data is better than less.

[therealdb]

I'm getting the values from ZWaveJS UI and checking on the reported values from MSR:

Position

Watts reading seems to be more related to the device not refreshing itself (or refreshing randomly), as it was doing on Vera. I'll keep debugging the ZWaveJS part, since it seems that if I refresh the device, the values is passed onto Reactor.

Thanks for the help!

[toggledbits]

Sorry, but the image looks like you're showing position, not watts. I would like to understand which of the two power values provided by the device you are trying to reconcile.

That said, a position of 0.91 would be correct, as the scale of the position.value attribute in Reactor is 0.0 to 1.0, computed from the device range of 0 to 99 (90/99 = 0.91 rounded to two digits).

[therealdb]

@toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

Sorry, but the image looks like you're showing position, not watts. I would like to understand which of the two power values provided by the device you are trying to reconcile.

no screenshot. As I've said, I'm finding that the device is not reporting that well. I'm 100% sure it was OK under Vera, and maybe it was part of the custom code they wrote for the device, Idk.

@toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

That said, a position of 0.91 would be correct, as the scale of the position.value attribute in Reactor is 0.0 to 1.0, computed from the device range of 0 to 99 (90/99 = 0.91 rounded to two digits).

ok, but I've asked for 0.90 via Reactor and I got 0.91 inside Reactor and 0.90 inside ZWaveJS. Imagine something that tries to position the device until it is OK...

[toggledbits]

The rounding is a function of the scaling.

I believe I mentioned in another thread that comparing equality of floating point numbers is a well-known Bad Idea in pretty much all programming languages.

The raw value is always available in the x_ extended attributes.

[therealdb]

so, the correct way is to look for x_zwave_values.Multilevel_Switch_currentValue and divide by 100?

EDIT: anyway, I still think that this behavior is not OK, because value are not consistent, but the call is yours.

[toggledbits]

I can change it, but it may be a breaking change for all users at this point. Not something to be taken lightly. I have considered it.

I still don't have enough information from you to do anything about the power issue, assuming there still is one.

[therealdb]

@toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

I can change it, but it may be a breaking change for all users at this point. Not something to be taken lightly. I have considered it.

No problem, I found it strange and I was reporting. It's also strange 'cause after a refresh the value from the controller is overwritten.

I still don't have enough information from you to do anything about the power issue, assuming there still is one.

Yes, but it's zwavejs that's not updating. I suspect Vera was doing some magic behind the scene. I'll keep watching it, now that the new system is almost stable.

[toggledbits]

@therealdb said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

Yes, but it's zwavejs that's not updating.

I see. I guess I didn't understand that before. OK. Let me know if you figure anything out that helps. There may be something I can bolt on to help with that. There do seem to be delta-sensitivity configuration settings on the device. I wonder if those are related?

So for the moment, have we covered all the hot-button items? Anything I haven't addressed yet?

[therealdb]

@toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

There do seem to be delta-sensitivity configuration settings on the device. I wonder if those are related?

Maybe. I'm experimenting with parameter and I'll report back. I still have a couple of strange behaviors to fix before I could dedicate to fine tuning.

@toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

So for the moment, have we covered all the hot-button items? Anything I haven't addressed yet?

Yes, the only thing pending is tilt position. I managed to use it via raw ZWave commands, but I think it could useful to have a separate endpoint for that. RS 3 and 4 are already exposing multiple endpoints, where the first is controlling the blind and the second the lamellas (and root does nothing).

Unfortunately, those from Fibaro are the only ZWave devices in Europe that are supporting lamellas. I'm sure eventually Shelly will catchup with its new ZWave series from Qubino and I'll eventually replace my RS2s, since they're not ZWave+ and are 8+ years old (I bought them for the old house, where I started with just roller shutters, so they served their purpose well).

[toggledbits]

@therealdb said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

Yes, the only thing pending is tilt position.

OK. I've lost the thread there. What's the problem with tilt at this point? In my bench-top use, changes in the Z-Wave reports feed to the position attribute correctly, so I'm not clear where the issue remains.

[therealdb]

Sorry, I was referring to this thread: https://smarthome.community/topic/1576/zwavejs-venetian-blind-tilt-for-fibaro-roller-shutters-2-fgr222/4

[therealdb]

ok, meter fixed. I don't know how it worked all these years, but the associations of device 4 were completely wrong (assigned to a non-existence device), thus it was somewhat working on Vera. Go figure. I reset the values and now it's reporting ok.

The very last thing about the device is that, after configuring a parameter, they support scene activation v0 and it would be nice to have a separate scene device, as in the switch. Otherwise, I'll simply go with x_zwave_values. Thanks.

[toggledbits]

Try activating the central scene on the device. Since these values are events, they aren't created until the first event is received. You may also need to refresh the browser, or at least "stimulate" the redraw of the entity list (by modifying the filters, etc.).